You can subscribe to this list here.
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(1) |
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2010 |
Jan
(4) |
Feb
(25) |
Mar
(4) |
Apr
|
May
(9) |
Jun
(12) |
Jul
(8) |
Aug
(4) |
Sep
(15) |
Oct
|
Nov
(8) |
Dec
(5) |
2011 |
Jan
(16) |
Feb
(6) |
Mar
(1) |
Apr
(14) |
May
(29) |
Jun
(33) |
Jul
(36) |
Aug
(4) |
Sep
(24) |
Oct
(30) |
Nov
(13) |
Dec
(1) |
2012 |
Jan
(2) |
Feb
(5) |
Mar
(1) |
Apr
(14) |
May
(24) |
Jun
(18) |
Jul
(10) |
Aug
(6) |
Sep
(3) |
Oct
(10) |
Nov
(10) |
Dec
(31) |
2013 |
Jan
(20) |
Feb
(23) |
Mar
(24) |
Apr
(17) |
May
(1) |
Jun
(28) |
Jul
(28) |
Aug
(16) |
Sep
(9) |
Oct
(20) |
Nov
(14) |
Dec
(10) |
2014 |
Jan
(37) |
Feb
(32) |
Mar
(102) |
Apr
(126) |
May
(55) |
Jun
(46) |
Jul
(57) |
Aug
(35) |
Sep
(45) |
Oct
(58) |
Nov
(30) |
Dec
(23) |
2015 |
Jan
(23) |
Feb
(7) |
Mar
(30) |
Apr
(13) |
May
(9) |
Jun
(7) |
Jul
(14) |
Aug
(52) |
Sep
(14) |
Oct
(4) |
Nov
(30) |
Dec
(22) |
2016 |
Jan
(48) |
Feb
(44) |
Mar
(38) |
Apr
(23) |
May
(24) |
Jun
(51) |
Jul
(21) |
Aug
(27) |
Sep
(39) |
Oct
(10) |
Nov
(10) |
Dec
(4) |
2017 |
Jan
(20) |
Feb
(16) |
Mar
(13) |
Apr
(18) |
May
(4) |
Jun
(1) |
Jul
(1) |
Aug
(7) |
Sep
(7) |
Oct
(8) |
Nov
(2) |
Dec
(5) |
2018 |
Jan
(6) |
Feb
(8) |
Mar
(7) |
Apr
(7) |
May
(5) |
Jun
(8) |
Jul
(3) |
Aug
(5) |
Sep
(12) |
Oct
(9) |
Nov
(4) |
Dec
(9) |
2019 |
Jan
(8) |
Feb
(7) |
Mar
(7) |
Apr
(4) |
May
(6) |
Jun
(2) |
Jul
(1) |
Aug
(4) |
Sep
(3) |
Oct
(4) |
Nov
(5) |
Dec
|
2020 |
Jan
(3) |
Feb
(3) |
Mar
(6) |
Apr
(6) |
May
(4) |
Jun
(5) |
Jul
(10) |
Aug
(5) |
Sep
|
Oct
(7) |
Nov
(3) |
Dec
(3) |
2021 |
Jan
(10) |
Feb
(2) |
Mar
(1) |
Apr
(1) |
May
(2) |
Jun
|
Jul
(2) |
Aug
(2) |
Sep
(4) |
Oct
|
Nov
(2) |
Dec
(1) |
2022 |
Jan
(4) |
Feb
(3) |
Mar
(1) |
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
(3) |
Oct
(5) |
Nov
(1) |
Dec
(1) |
2023 |
Jan
(3) |
Feb
(2) |
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
2024 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Shawna Sp <sha...@gm...> - 2019-03-11 15:37:43
|
Dear Tripal Community, This is a reminder that the Tripal User's meeting is scheduled for tomorrow at 8 am PST / 11 am EST. The primary agenda item is to discuss the formalization of a Tripal Advisory Committee. The goal for this committee is to provide long-term direction for Tripal development and encourage a unified approach to funding of new Tripal core development. If you're able to join us the connection details are: Join Zoom Meeting https://zoom.us/j/695900512 One tap mobile +16468769923,,695900512# US (New York) +14086380968,,695900512# US (San Jose) Dial by your location +1 646 876 9923 US (New York) +1 408 638 0968 US (San Jose) +1 669 900 6833 US (San Jose) Meeting ID: 695 900 512 Find your local number: https://zoom.us/u/aemJ4PVvom Thanks, Shawna On Fri, Mar 1, 2019 at 12:13 PM Stephen Ficklin <ste...@ws...> wrote: > Dear Tripal Community, > > We will be moving our monthly Tripal User's Meeting from this coming > Tuesday (when it would normally fall) to March 12th. The time for the > meeting will be the same as usual (8am PST, 10am CST, 9am Regina, 11am > EST, 4pm European Central), and we will send out a link with connection > details as we near that date. > > **Note** that daylight savings time change occurs on March 10th in the > US so the usual meeting time may have changed for your time. (The list > I provide should be correct for the time zones listed for March 12th) > > The primary agenda item is to discuss the formalization of a Tripal > Advisory Committee. The goal for this committee is to provide long-term > direction for Tripal development, and encourage a unified approach to > funding of new Tripal core development. However, due to a scheduling > conflict not all of our interim TAC can attend this Friday. Because we > do not want to delay this discussion until April we've decided to > postpone the meeting one week. > > We encourage everyone to attend and participate. This is an opportunity > to have your voice heard in the formation of Tripal governance and > long-term direction. > > Best, > Stephen > > -- > Stephen Ficklin, PhD > Assistant Professor > Bioinformatics and Systems Genetics > Department of Horticulture > Washington State University > 153 Johnson Hall > Pullman, WA 99164-6414 > Office: (509) 335-4295 > > http://ficklinlab.cahnrs.wsu.edu/ > > > > _______________________________________________ > Gmod-tripal mailing list > Gmo...@li... > https://lists.sourceforge.net/lists/listinfo/gmod-tripal > |
From: Stephen F. <spf...@gm...> - 2019-03-04 21:32:47
|
Dear Tripal Community, Tripal v3.1 is now released! There are quite a few bug fixes (see the change log below). Also, there is a large increase in documentation. Please check out the online documentation for new tutorials and guides if you haven't looked recently. For sites using Tripal v3.0 or the Tripal 3.x development branch you can upgrade using the typical Drupal upgrade process. An example command-line with drush: drush pm-update For Tripal v2.x users, you can follow upgrade instructions here: https://tripal.readthedocs.io/en/latest/user_guide/install_tripal/upgrade_from_tripal2.html Remember to always make a back-up of your site before upgrading. As always please submit any issues, challenges, feature requests or items for discussion to our GitHub issue queue at https://github.com/tripal/tripal/issues. And Documentation is open for edits as well! Use the 'Edit on Github' link at the top of any Tripal v3 Users or Developer's Guide. Release 3.1 change log: 1. Updated User's and Developer's documentation to include module rating system, usage3 of pythlotree visualizations, fields and AJAX, creating your own RTD docs for a custom module, how to contribute to Tripal core development, improvements to the setup of a genomics web site, manging user file quotas, a new list of extension modules, 2. Added additional unit testing 3. Multiple bug fixes with chado querying 4. Fixes to bugs in icons of the panels display 5. Fixed access permissions in web services if the field permissions module is installed. 6. Fixed bugs with cvterm entity types. 7. Fixed bugs where some fields disappear even if they are not empty. 8. Fixed multiple problems with the relationship field. 9. Fixed bug with bulk setting of URL aliases for entities. 10. Fixes to the linker contact field. 11. Fixes to fields not being removed when emptied. 12. Support for creation of database cross references inside of entity edit forms. 13. Fixes to the FASTA importer related if a regex is not needed to specify a relationship. 14. New functionality to unpublish orphaned entities. |
From: Stephen F. <ste...@ws...> - 2019-03-01 17:13:36
|
Dear Tripal Community, We will be moving our monthly Tripal User's Meeting from this coming Tuesday (when it would normally fall) to March 12th. The time for the meeting will be the same as usual (8am PST, 10am CST, 9am Regina, 11am EST, 4pm European Central), and we will send out a link with connection details as we near that date. **Note** that daylight savings time change occurs on March 10th in the US so the usual meeting time may have changed for your time. (The list I provide should be correct for the time zones listed for March 12th) The primary agenda item is to discuss the formalization of a Tripal Advisory Committee. The goal for this committee is to provide long-term direction for Tripal development, and encourage a unified approach to funding of new Tripal core development. However, due to a scheduling conflict not all of our interim TAC can attend this Friday. Because we do not want to delay this discussion until April we've decided to postpone the meeting one week. We encourage everyone to attend and participate. This is an opportunity to have your voice heard in the formation of Tripal governance and long-term direction. Best, Stephen -- Stephen Ficklin, PhD Assistant Professor Bioinformatics and Systems Genetics Department of Horticulture Washington State University 153 Johnson Hall Pullman, WA 99164-6414 Office: (509) 335-4295 http://ficklinlab.cahnrs.wsu.edu/ |
From: Stephen F. <spf...@gm...> - 2019-02-26 18:31:51
|
Dear Extension Module Developers, The Tripal Project Management Committee (PMC) has introduced a new extension module rating system. The purpose is to help the community elevate the quality of our modules, maximize interoperability with Tripal and extensions and advertise the status of your modules to others. Learn more about the module rating system here: https://tripal.readthedocs.io/en/latest/extensions/module_rating.html Add badges to advertise your module's ratings to your GitHub repositories! Tripal Extenson Module Rating Badges To add a badge, your module must exist on the Extension Modules page of Tripal's online documentation: https://tripal.readthedocs.io/en/latest/extensions.html. If your module is not present, you may add it by following these instructions: https://tripal.readthedocs.io/en/latest/extensions/instructions.html Stephen Ficklin Member Tripal Project Management Committee |
From: Shawna Sp <sha...@gm...> - 2019-02-14 12:07:16
|
Hi all, If you have a specific topic you need help with please fill out this google form by tomorrow, Friday, February 15: https://goo.gl/forms/7ktsZFKy1n0cg0fH2 Tripal Help Desk sessions are scheduled for Tuesday, February 19, 2019. The aim of these sessions is to match up people who need help with people who can help. Once we have the times and topics worked out we will post them on the tripal.info site, and email a list of topics, times, and virtual room links to this mailing list. We are also looking for suggestions for the next Tripal Training session. If you've got a topic you'd like covered please let me know! Thanks! Shawna |
From: Cannon, E. K [C. S] <ekc...@ia...> - 2019-02-11 21:51:44
|
Dear Tripal Community, As the community grows and more people are contributing ideas and code to Tripal, it is prudent to decide on how we will govern ourselves. This is to keep coherence in the project and to ensure that Tripal continues to meet the needs of its growing community. A draft of the governance document is available here: https://docs.google.com/document/d/1iRGmZzKnAm8c5Q9yYLiTctSJaRqnT6Bm0eix1uzoTxw. This document describes the current roles within the community with the addition of a Scientific Advisory Committee (SAC). The vision is for this committee to act in an advisory role to the Project Management Committee (PMC) tackling long term planning and ensuring that Tripal stakeholder opinions are heard. We are asking the community for comments on the new SAC. You can make comments on the document or via the GitHub issue concerning governance, https://github.com/tripal/tripal/issues/344. We ask that comments be completed by next Monday so that we can begin planning for the first SAC meeting. An official chair will be selected will be selected at the first meeting. Ethy and Meg Acting co-chairs of the Scientific Advisory Committee |
From: Cannon, E. K [C. S] <ekc...@ia...> - 2019-02-11 21:29:26
|
Correction. Please add comments to this issue: https://github.com/tripal/tripal/issues/786 The issue listed below has now been closed. ________________________________ From: Cannon, Ethalinda K [COM S] Sent: Monday, February 11, 2019 2:18 PM To: gmo...@li... Subject: Request for comments on formation of Tripal Scientific Advisory Committee Dear Tripal Community, As the community grows and more people are contributing ideas and code to Tripal, it is prudent to decide on how we will govern ourselves. This is to keep coherence in the project and to ensure that Tripal continues to meet the needs of its growing community. A draft of the governance document is available here: https://docs.google.com/document/d/1iRGmZzKnAm8c5Q9yYLiTctSJaRqnT6Bm0eix1uzoTxw. This document describes the current roles within the community with the addition of a Scientific Advisory Committee (SAC). The vision is for this committee to act in an advisory role to the Project Management Committee (PMC) tackling long term planning and ensuring that Tripal stakeholder opinions are heard. We are asking the community for comments on the new SAC. You can make comments on the document or via the GitHub issue concerning governance, https://github.com/tripal/tripal/issues/344. We ask that comments be completed by next Monday so that we can begin planning for the first SAC meeting. An official chair will be selected will be selected at the first meeting. Ethy and Meg Acting co-chairs of the Scientific Advisory Committee |
From: Shawna Sp <sha...@gm...> - 2019-02-04 21:16:14
|
Hi all, Just a quick reminder that our Tripal users meeting is tomorrow at 8am PST/11am EST. Here are the connection details: Topic: February Tripal User's Meeting Time: Feb 5, 2019 8:00 AM Pacific Time (US and Canada) Join Zoom Meeting https://zoom.us/j/886432633 One tap mobile +16699006833,,886432633# US (San Jose) +14086380968,,886432633# US (San Jose) Dial by your location +1 669 900 6833 US (San Jose) +1 408 638 0968 US (San Jose) +1 646 876 9923 US (New York) Meeting ID: 886 432 633 Find your local number: https://zoom.us/u/blw0oihJ See you then! On Tue, Jan 29, 2019, 8:59 PM Shawna Sp <sha...@gm... wrote: > Hi all, > > Our next Tripal user's meeting is scheduled for Tuesday, February 5, 2019, > at 8 am PST / 11 am EST. > > This next Tripal user's meeting will be an open meeting. If you would like > to discuss anything, in particular, please feel free to add it to the > agenda: > https://docs.google.com/document/d/1JB976OcXS8QAyo7zLwFyyuLVdqNW3-IryEFe9_VNt2Q/edit?usp=sharing > > You can find the specific time in your area via this link: > https://www.timeanddate.com/worldclock/fixedtime.html?msg=Tripal+User%27s+Meeting+February+2019&iso=20190205T08&p1=2035&ah=1 > > > Connection Details to come. > > > Also, we are going to start offering Tripal Help Desk and Tripal Trainings > again. We will be running our next round of Tripal Help Desk virtual > collaboration meetings on Tuesday, February 19, 2019. > > As a reminder, the aim of these sessions is to match up people who need > help with people who can help. Once we have the times and topics worked out > we will post them on the tripal.info site, and email a list of topics, > times, and virtual room links to this mailing list. > > If you have a specific topic you need help with please fill out this > google form by Friday, February 15: https://goo.gl/forms/7ktsZFKy1n0cg0fH2 > > We are also looking for suggestions for the next Tripal Training session. > If you've got a topic you'd like covered please let me know! > > Thanks! > Shawna > |
From: Main, D. <do...@ws...> - 2019-02-04 20:39:52
|
I have the same concerns Bradford and think support effort is best placed helping groups port from T2 to T3. I think I mentioned that we (led by Stephen) should think of applying for a major grant ($10-15M through a non competitive process - I have an idea on how we might do this) for the entire Tripal community (so each group would get funds - including the non US groups) to get us up to where we need to be. I am very concerned about the workload proposed given the current lack of resources, plus the impression that we are now going of in many directions which is counter to the whole idea of Tripal (I would argue). Cheers Dorrie Dorrie Main, PhD Professor of Bioinformatics Department of Horticulture Washington State University 45 Johnson Hall Pullman, WA 99164-6414 Tel: 509-335-2774 (office) Email: do...@ws...<mailto:do...@ws...> URL: www.bioinfo.wsu.edu<http://www.bioinfo.wsu.edu/> ________________________________ From: bradford condon <bra...@gm...> Sent: Monday, February 4, 2019 9:59 AM To: Cannon, Ethalinda K [COM S]; GMOD Tripal Cc: lac...@us... Subject: Re: [Gmod-tripal] Tripal v4 plan: request for feedback Hi everyone: Speaking as myself, not for the entire PMC. I have two main concerns with the backdrop proposal. 1). The work of maintaining a backdrop compatible branch. As it is, we don’t have the developer time or interest in maintaining and back porting features to the tripal 2 branch. We created issues but no one was filling them. When someone does contribute code to the tripal 2 branch, it takes me more time to review it than a tripal 3 contribution, as I have to set up a different developer instance, recreate the problem, and understand the t2 code which I’m not familiar with. I imagine this would be even harder with backdrop. While chatting, Valentin brought up the possibility of the Tripal core team not maintaining the backdrop branch. Users could contribute patches which each site could apply at their own discretion, without approval from the Tripal team. I think this is more realistic. However it's also more problematic since now there is more admin work for sites using a backdrop branch (they have to test and apply the patches themselves). 2). The community We are not a big community. This would more or less be forking Tripal until a micro services approach could be taken, which we’ve agreed is a big undertaking. If I have the option, I’d prefer to spend development time helping out other sites upgrade to Tripal 3 (online training/help sessions, new guides, whatever we can do to help) than developing a fork. Bradford On Jan 24, 2019, at 8:20 AM, Cannon, Ethalinda K [COM S] <ekc...@ia...<mailto:ekc...@ia...>> wrote: I like this idea, Valentin. It's impossible to know what programming help I will have in the future, or how much time I will have, so it's good to prepare for the likelihood of not being able to upgrade to a current version of Tripal before D7 loses its security updates. Ethy ________________________________ From: Guignon, Valentin (Bioversity-France) <v.g...@cg...<mailto:v.g...@cg...>> Sent: Thursday, January 24, 2019 3:01 AM To: Stephen Ficklin; GMOD Tripal Cc: lac...@us...<mailto:lac...@us...> Subject: Re: [Gmod-tripal] Tripal v4 plan: request for feedback Dear Stephen, Sounds good to me. I just would like to raise a point. I know some people (Ethy for instance but there might be others) are not planning to upgrade to Tripal 3 because they don't have the resource (time/people/money) to do so. So they won't update to Drupal 8, 9 and Tripal 4 for the same reasons. I think we (as a community) should consider porting Tripal 2 (and/or 3?) to Backdrop (https://backdropcms.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__backdropcms.org_&d=DwMFaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-Je7sw&r=XhjY_3bv0u3surhUgGoaow&m=4z_r7i-rR90ZYkH2tzqgA5bqrvLlYQmYiiEWF9t0hiE&s=T4rx4Mv2KjkbzbrVpQQTVQbkp0LiVqUcR-l_oG7_eyw&e=>) which is a fork of Drupal 7 that will continue to have security support. I had a quick look at how hard would it be to do so (https://api.backdropcms.org/converting-modules-from-drupal<https://urldefense.proofpoint.com/v2/url?u=https-3A__api.backdropcms.org_converting-2Dmodules-2Dfrom-2Ddrupal&d=DwMFaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-Je7sw&r=XhjY_3bv0u3surhUgGoaow&m=4z_r7i-rR90ZYkH2tzqgA5bqrvLlYQmYiiEWF9t0hiE&s=KULMbAXsvFxLob0mLkG1ljmgPXmcYJ_tFwpGHZ6NFrU&e=>, https://www.youtube.com/watch?v=by8mMhIpARA<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.youtube.com_watch-3Fv-3Dby8mMhIpARA&d=DwMFaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-Je7sw&r=XhjY_3bv0u3surhUgGoaow&m=4z_r7i-rR90ZYkH2tzqgA5bqrvLlYQmYiiEWF9t0hiE&s=wt3DqNPjwQ4CllhMr2da3kl0NXalecp-7oY3QrPECtU&e=>) and I think it would take around a week (maybe less, 1 full time person) to do so. Moving from Drupal 7 to Backdrop 1 does not seem to be a big deal as long as you don't use contributed modules that have not been ported to backdrop. I think people who would be interested by this port should say so, to have an idea on how many people are interested and if this effort is really needed. What do you think? Best, Valentin -----Original Message----- From: Stephen Ficklin [mailto:spf...@gm...] Sent: mercredi 23 janvier 2019 21:02 To: GMOD Tripal <gmo...@li...<mailto:gmo...@li...>> Cc: lac...@us...<mailto:lac...@us...> Subject: [Gmod-tripal] Tripal v4 plan: request for feedback Dear Tripal Community, Thank you for your activity and usage of the past year! Special thanks to those who organized and participated in our recent CodeFest, Workshop at PAG, and everyone who has attended our monthly User's Meetings and training sessions. We hope to have another productive year. I wanted to write regarding the Tripal v4 upgrade. As a community, we have recently discussed a proof-of-concept effort to develop a micro-services software stack for Tripal that we think would afford more flexibility in development and hopefully reduce the learning curve for new developers to get involved. At the Codefest a group of us worked on that proof-of-concept to see how well it would work. We made progress but that work is still ongoing. Currently, Drupal 7 and Drupal 8 are expected to lose official support (i.e. end of life (EOL)) on Nov 2021. That's just under 3 years for Tripal to have a Drupal 8 version and a Drupal 9 version ready to go. To this end, Tripal's Project Management Committee (PMC) is proposing that we immediately start the port of Tripal v3 to Drupal 8 so that we have a complete upgrade path from Drupal 7 to eventually Drupal 9. The plan would be to release a Tripal v4 that is the same as Tripal v3 but is Drupal 8 compatible. This ensures we do not fall off of the Drupal security support timeline, which is the highest priority and should not be delayed. This will not conflict with the efforts of those working on the Proof of Concept. We will continue to develop that approach with the intent to create a Tripal v5 release supporting Drupal 9, pending recommendation of the (not yet formalized) Tripal Scientific Advisory Board. Please let us know if you have any concerns with this plan. Best, The Tripal Project Management Committee, Stephen Ficklin, Lacey Sanderson, Bradford Condon _______________________________________________ Gmod-tripal mailing list Gmo...@li...<mailto:Gmo...@li...> https://lists.sourceforge.net/lists/listinfo/gmod-tripal<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_gmod-2Dtripal&d=DwMFaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-Je7sw&r=XhjY_3bv0u3surhUgGoaow&m=4z_r7i-rR90ZYkH2tzqgA5bqrvLlYQmYiiEWF9t0hiE&s=bi59YXze_XidhLI6HQlUhtKjxTxJXwCcD8yROmdDBJg&e=> _______________________________________________ Gmod-tripal mailing list Gmo...@li... https://lists.sourceforge.net/lists/listinfo/gmod-tripal<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_gmod-2Dtripal&d=DwMFaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-Je7sw&r=XhjY_3bv0u3surhUgGoaow&m=4z_r7i-rR90ZYkH2tzqgA5bqrvLlYQmYiiEWF9t0hiE&s=bi59YXze_XidhLI6HQlUhtKjxTxJXwCcD8yROmdDBJg&e=> _______________________________________________ Gmod-tripal mailing list Gmo...@li...<mailto:Gmo...@li...> https://lists.sourceforge.net/lists/listinfo/gmod-tripal<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_gmod-2Dtripal&d=DwMFaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-Je7sw&r=XhjY_3bv0u3surhUgGoaow&m=4z_r7i-rR90ZYkH2tzqgA5bqrvLlYQmYiiEWF9t0hiE&s=bi59YXze_XidhLI6HQlUhtKjxTxJXwCcD8yROmdDBJg&e=> |
From: bradford c. <bra...@gm...> - 2019-02-04 18:00:05
|
Hi everyone: Speaking as myself, not for the entire PMC. I have two main concerns with the backdrop proposal. 1). The work of maintaining a backdrop compatible branch. As it is, we don’t have the developer time or interest in maintaining and back porting features to the tripal 2 branch. We created issues but no one was filling them. When someone does contribute code to the tripal 2 branch, it takes me more time to review it than a tripal 3 contribution, as I have to set up a different developer instance, recreate the problem, and understand the t2 code which I’m not familiar with. I imagine this would be even harder with backdrop. While chatting, Valentin brought up the possibility of the Tripal core team not maintaining the backdrop branch. Users could contribute patches which each site could apply at their own discretion, without approval from the Tripal team. I think this is more realistic. However it's also more problematic since now there is more admin work for sites using a backdrop branch (they have to test and apply the patches themselves). 2). The community We are not a big community. This would more or less be forking Tripal until a micro services approach could be taken, which we’ve agreed is a big undertaking. If I have the option, I’d prefer to spend development time helping out other sites upgrade to Tripal 3 (online training/help sessions, new guides, whatever we can do to help) than developing a fork. Bradford > On Jan 24, 2019, at 8:20 AM, Cannon, Ethalinda K [COM S] <ekc...@ia...> wrote: > > I like this idea, Valentin. It's impossible to know what programming help I will have in the future, or how much time I will have, so it's good to prepare for the likelihood of not being able to upgrade to a current version of Tripal before D7 loses its security updates. > > Ethy > From: Guignon, Valentin (Bioversity-France) <v.g...@cg...> > Sent: Thursday, January 24, 2019 3:01 AM > To: Stephen Ficklin; GMOD Tripal > Cc: lac...@us... > Subject: Re: [Gmod-tripal] Tripal v4 plan: request for feedback > > Dear Stephen, > > Sounds good to me. I just would like to raise a point. I know some people (Ethy for instance but there might be others) are not planning to upgrade to Tripal 3 because they don't have the resource (time/people/money) to do so. So they won't update to Drupal 8, 9 and Tripal 4 for the same reasons. > > I think we (as a community) should consider porting Tripal 2 (and/or 3?) to Backdrop (https://backdropcms.org/ <https://backdropcms.org/>) which is a fork of Drupal 7 that will continue to have security support. I had a quick look at how hard would it be to do so ( <applewebdata://579C24CA-6FF9-4964-9F5A-C4E8DC12358A>https://api.backdropcms.org/converting-modules-from-drupal, https://www.youtube.com/watch?v=by8mMhIpARA <https://www.youtube.com/watch?v=by8mMhIpARA>) and I think it would take around a week (maybe less, 1 full time person) to do so. Moving from Drupal 7 to Backdrop 1 does not seem to be a big deal as long as you don't use contributed modules that have not been ported to backdrop. > > I think people who would be interested by this port should say so, to have an idea on how many people are interested and if this effort is really needed. > What do you think? > > Best, > > Valentin > > > > -----Original Message----- > From: Stephen Ficklin [mailto:spf...@gm... <mailto:spf...@gm...>] > Sent: mercredi 23 janvier 2019 21:02 > To: GMOD Tripal <gmo...@li...> > Cc: lac...@us... > Subject: [Gmod-tripal] Tripal v4 plan: request for feedback > > Dear Tripal Community, > > Thank you for your activity and usage of the past year! Special thanks to those who organized and participated in our recent CodeFest, Workshop at PAG, and everyone who has attended our monthly User's Meetings and training sessions. We hope to have another productive year. > > I wanted to write regarding the Tripal v4 upgrade. As a community, we have recently discussed a proof-of-concept effort to develop a micro-services software stack for Tripal that we think would afford more flexibility in development and hopefully reduce the learning curve for new developers to get involved. At the Codefest a group of us worked on that proof-of-concept to see how well it would work. We made progress but that work is still ongoing. > > Currently, Drupal 7 and Drupal 8 are expected to lose official support (i.e. end of life (EOL)) on Nov 2021. That's just under 3 years for Tripal to have a Drupal 8 version and a Drupal 9 version ready to go. To this end, Tripal's Project Management Committee (PMC) is proposing that we immediately start the port of Tripal v3 to Drupal 8 so that we have a complete upgrade path from Drupal 7 to eventually Drupal 9. The plan would be to release a Tripal v4 that is the same as Tripal v3 but is Drupal 8 compatible. This ensures we do not fall off of the Drupal security support timeline, which is the highest priority and should not be delayed. > > This will not conflict with the efforts of those working on the Proof of Concept. We will continue to develop that approach with the intent to create a Tripal v5 release supporting Drupal 9, pending recommendation of the (not yet formalized) Tripal Scientific Advisory Board. Please let us know if you have any concerns with this plan. > > Best, > The Tripal Project Management Committee, Stephen Ficklin, Lacey Sanderson, Bradford Condon > > > > _______________________________________________ > Gmod-tripal mailing list > Gmo...@li... > https://lists.sourceforge.net/lists/listinfo/gmod-tripal <https://lists.sourceforge.net/lists/listinfo/gmod-tripal> > > _______________________________________________ > Gmod-tripal mailing list > Gmo...@li... > https://lists.sourceforge.net/lists/listinfo/gmod-tripal <https://lists.sourceforge.net/lists/listinfo/gmod-tripal> > _______________________________________________ > Gmod-tripal mailing list > Gmo...@li... <mailto:Gmo...@li...> > https://lists.sourceforge.net/lists/listinfo/gmod-tripal <https://lists.sourceforge.net/lists/listinfo/gmod-tripal> |
From: Shawna Sp <sha...@gm...> - 2019-01-29 19:59:55
|
Hi all, Our next Tripal user's meeting is scheduled for Tuesday, February 5, 2019, at 8 am PST / 11 am EST. This next Tripal user's meeting will be an open meeting. If you would like to discuss anything, in particular, please feel free to add it to the agenda: https://docs.google.com/document/d/1JB976OcXS8QAyo7zLwFyyuLVdqNW3-IryEFe9_VNt2Q/edit?usp=sharing You can find the specific time in your area via this link: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Tripal+User%27s+Meeting+February+2019&iso=20190205T08&p1=2035&ah=1 Connection Details to come. Also, we are going to start offering Tripal Help Desk and Tripal Trainings again. We will be running our next round of Tripal Help Desk virtual collaboration meetings on Tuesday, February 19, 2019. As a reminder, the aim of these sessions is to match up people who need help with people who can help. Once we have the times and topics worked out we will post them on the tripal.info site, and email a list of topics, times, and virtual room links to this mailing list. If you have a specific topic you need help with please fill out this google form by Friday, February 15: https://goo.gl/forms/7ktsZFKy1n0cg0fH2 We are also looking for suggestions for the next Tripal Training session. If you've got a topic you'd like covered please let me know! Thanks! Shawna |
From: Cannon, E. K [C. S] <ekc...@ia...> - 2019-01-24 14:54:05
|
I like this idea, Valentin. It's impossible to know what programming help I will have in the future, or how much time I will have, so it's good to prepare for the likelihood of not being able to upgrade to a current version of Tripal before D7 loses its security updates. Ethy ________________________________ From: Guignon, Valentin (Bioversity-France) <v.g...@cg...> Sent: Thursday, January 24, 2019 3:01 AM To: Stephen Ficklin; GMOD Tripal Cc: lac...@us... Subject: Re: [Gmod-tripal] Tripal v4 plan: request for feedback Dear Stephen, Sounds good to me. I just would like to raise a point. I know some people (Ethy for instance but there might be others) are not planning to upgrade to Tripal 3 because they don't have the resource (time/people/money) to do so. So they won't update to Drupal 8, 9 and Tripal 4 for the same reasons. I think we (as a community) should consider porting Tripal 2 (and/or 3?) to Backdrop (https://backdropcms.org/) which is a fork of Drupal 7 that will continue to have security support. I had a quick look at how hard would it be to do so (https://api.backdropcms.org/converting-modules-from-drupal, https://www.youtube.com/watch?v=by8mMhIpARA) and I think it would take around a week (maybe less, 1 full time person) to do so. Moving from Drupal 7 to Backdrop 1 does not seem to be a big deal as long as you don't use contributed modules that have not been ported to backdrop. I think people who would be interested by this port should say so, to have an idea on how many people are interested and if this effort is really needed. What do you think? Best, Valentin -----Original Message----- From: Stephen Ficklin [mailto:spf...@gm...] Sent: mercredi 23 janvier 2019 21:02 To: GMOD Tripal <gmo...@li...> Cc: lac...@us... Subject: [Gmod-tripal] Tripal v4 plan: request for feedback Dear Tripal Community, Thank you for your activity and usage of the past year! Special thanks to those who organized and participated in our recent CodeFest, Workshop at PAG, and everyone who has attended our monthly User's Meetings and training sessions. We hope to have another productive year. I wanted to write regarding the Tripal v4 upgrade. As a community, we have recently discussed a proof-of-concept effort to develop a micro-services software stack for Tripal that we think would afford more flexibility in development and hopefully reduce the learning curve for new developers to get involved. At the Codefest a group of us worked on that proof-of-concept to see how well it would work. We made progress but that work is still ongoing. Currently, Drupal 7 and Drupal 8 are expected to lose official support (i.e. end of life (EOL)) on Nov 2021. That's just under 3 years for Tripal to have a Drupal 8 version and a Drupal 9 version ready to go. To this end, Tripal's Project Management Committee (PMC) is proposing that we immediately start the port of Tripal v3 to Drupal 8 so that we have a complete upgrade path from Drupal 7 to eventually Drupal 9. The plan would be to release a Tripal v4 that is the same as Tripal v3 but is Drupal 8 compatible. This ensures we do not fall off of the Drupal security support timeline, which is the highest priority and should not be delayed. This will not conflict with the efforts of those working on the Proof of Concept. We will continue to develop that approach with the intent to create a Tripal v5 release supporting Drupal 9, pending recommendation of the (not yet formalized) Tripal Scientific Advisory Board. Please let us know if you have any concerns with this plan. Best, The Tripal Project Management Committee, Stephen Ficklin, Lacey Sanderson, Bradford Condon _______________________________________________ Gmod-tripal mailing list Gmo...@li... https://lists.sourceforge.net/lists/listinfo/gmod-tripal _______________________________________________ Gmod-tripal mailing list Gmo...@li... https://lists.sourceforge.net/lists/listinfo/gmod-tripal |
From: Guignon, V. (Bioversity-France) <v.g...@cg...> - 2019-01-24 09:16:35
|
Dear Stephen, Sounds good to me. I just would like to raise a point. I know some people (Ethy for instance but there might be others) are not planning to upgrade to Tripal 3 because they don't have the resource (time/people/money) to do so. So they won't update to Drupal 8, 9 and Tripal 4 for the same reasons. I think we (as a community) should consider porting Tripal 2 (and/or 3?) to Backdrop (https://backdropcms.org/) which is a fork of Drupal 7 that will continue to have security support. I had a quick look at how hard would it be to do so (https://api.backdropcms.org/converting-modules-from-drupal, https://www.youtube.com/watch?v=by8mMhIpARA) and I think it would take around a week (maybe less, 1 full time person) to do so. Moving from Drupal 7 to Backdrop 1 does not seem to be a big deal as long as you don't use contributed modules that have not been ported to backdrop. I think people who would be interested by this port should say so, to have an idea on how many people are interested and if this effort is really needed. What do you think? Best, Valentin -----Original Message----- From: Stephen Ficklin [mailto:spf...@gm...] Sent: mercredi 23 janvier 2019 21:02 To: GMOD Tripal <gmo...@li...> Cc: lac...@us... Subject: [Gmod-tripal] Tripal v4 plan: request for feedback Dear Tripal Community, Thank you for your activity and usage of the past year! Special thanks to those who organized and participated in our recent CodeFest, Workshop at PAG, and everyone who has attended our monthly User's Meetings and training sessions. We hope to have another productive year. I wanted to write regarding the Tripal v4 upgrade. As a community, we have recently discussed a proof-of-concept effort to develop a micro-services software stack for Tripal that we think would afford more flexibility in development and hopefully reduce the learning curve for new developers to get involved. At the Codefest a group of us worked on that proof-of-concept to see how well it would work. We made progress but that work is still ongoing. Currently, Drupal 7 and Drupal 8 are expected to lose official support (i.e. end of life (EOL)) on Nov 2021. That's just under 3 years for Tripal to have a Drupal 8 version and a Drupal 9 version ready to go. To this end, Tripal's Project Management Committee (PMC) is proposing that we immediately start the port of Tripal v3 to Drupal 8 so that we have a complete upgrade path from Drupal 7 to eventually Drupal 9. The plan would be to release a Tripal v4 that is the same as Tripal v3 but is Drupal 8 compatible. This ensures we do not fall off of the Drupal security support timeline, which is the highest priority and should not be delayed. This will not conflict with the efforts of those working on the Proof of Concept. We will continue to develop that approach with the intent to create a Tripal v5 release supporting Drupal 9, pending recommendation of the (not yet formalized) Tripal Scientific Advisory Board. Please let us know if you have any concerns with this plan. Best, The Tripal Project Management Committee, Stephen Ficklin, Lacey Sanderson, Bradford Condon _______________________________________________ Gmod-tripal mailing list Gmo...@li... https://lists.sourceforge.net/lists/listinfo/gmod-tripal |
From: Stephen F. <spf...@gm...> - 2019-01-23 20:01:39
|
Dear Tripal Community, Thank you for your activity and usage of the past year! Special thanks to those who organized and participated in our recent CodeFest, Workshop at PAG, and everyone who has attended our monthly User's Meetings and training sessions. We hope to have another productive year. I wanted to write regarding the Tripal v4 upgrade. As a community, we have recently discussed a proof-of-concept effort to develop a micro-services software stack for Tripal that we think would afford more flexibility in development and hopefully reduce the learning curve for new developers to get involved. At the Codefest a group of us worked on that proof-of-concept to see how well it would work. We made progress but that work is still ongoing. Currently, Drupal 7 and Drupal 8 are expected to lose official support (i.e. end of life (EOL)) on Nov 2021. That's just under 3 years for Tripal to have a Drupal 8 version and a Drupal 9 version ready to go. To this end, Tripal's Project Management Committee (PMC) is proposing that we immediately start the port of Tripal v3 to Drupal 8 so that we have a complete upgrade path from Drupal 7 to eventually Drupal 9. The plan would be to release a Tripal v4 that is the same as Tripal v3 but is Drupal 8 compatible. This ensures we do not fall off of the Drupal security support timeline, which is the highest priority and should not be delayed. This will not conflict with the efforts of those working on the Proof of Concept. We will continue to develop that approach with the intent to create a Tripal v5 release supporting Drupal 9, pending recommendation of the (not yet formalized) Tripal Scientific Advisory Board. Please let us know if you have any concerns with this plan. Best, The Tripal Project Management Committee, Stephen Ficklin, Lacey Sanderson, Bradford Condon |
From: Guignon, V. (Bioversity-France) <v.g...@cg...> - 2019-01-15 21:48:18
|
Hi! I believe most of you already know what iNaturalist is (https://www.inaturalist.org/). During PAG I heard about it in some presentations. As I'm working on a projects that aims to include people observations about banana plants on our MGIS website, we contracted a consultant to develop a module to import data from iNaturalist 3 month ago. The contract is over now. The system is already working but not officially displayed on our production site (beta version). It's composed of 2 modules, one to import data into Chado through Drupal migrate module (https://www.drupal.org/project/migrate_chado) and another one (private) dedicated to our needs (mgis_inaturalist). We still plan to add some features but I'll do them. Maybe other people in our community are interested in iNaturalist and may even have started to work on modules. I would be interested to know: -who might be interested by an iNaturalist Tripal (2-3) module (a public and more generic one)? -what would be your needs on such a module? what type of iNaturalist data are you interested in and what/how would you like to import? -if you have already people working on this, how far are they and if you see an opportunity here to join our efforts? Cheers, Valentin |
From: Stephen F. <spf...@gm...> - 2019-01-07 23:03:22
|
A clarification. The Tripal Governance/SAC discussion during the CodeFest will begin at 9am on Friday. There will be no Thursday activities for this topic. On 1/7/2019 9:32 AM, Stephen Ficklin wrote: > > For those of you attending the upcoming Tripal Codefest and or > Workshop at the Plant and Animal Genome Conference in San Diego at the > Town and Country here are a few important details: > > *Tripal CodeFest > * > > When: Thursday**and Friday Jan 10th from 8:00am-5:00pm and Jan 11th > from 8:00am - 2:45pm > Where: The Crescent Room (see map for directions: > https://www.towncountry.com/hotel-map). > > If you are planning to attend and have not yet signed up for a topic > please add your name to our signup page: > https://docs.google.com/spreadsheets/d/1agEK8S4yxphTOC7cojvsVjTxsPH5PenvtHDBDz5XotE/edit#gid=0 > > We have three major coding topics and one topic for discussion. These > include: > 1. Tripal 4 Proof of Concept implementing Python and microservices. > 2. Implementation of the Breeders API for Tripal. > 3. Updates to Chado. > 4. Discussion: Scientific Advisory Committee Discussion > > *Tripal Face-to-Face User's Meeting* > > When: Friday Jan 10th 3pm-5pm. > Where: Crescent Room. > > This meeting is open to all who want to attend. The major topic to be > discussed will be Tripal Governance, in particular creation of a > scientific advisory committee for Tripal. > > *Tripal Workshop* > > When: Sunday Jan 13th 4pm-6:00pm > Where: California Room > > See the list of speakers here: > https://plan.core-apps.com/pag_2019/event/9441a7255c56cf0ce04b90bfc40903c5 > |
From: Stephen F. <spf...@gm...> - 2019-01-07 17:32:31
|
For those of you attending the upcoming Tripal Codefest and or Workshop at the Plant and Animal Genome Conference in San Diego at the Town and Country here are a few important details: *Tripal CodeFest * When: Thursday**and Friday Jan 10th from 8:00am-5:00pm and Jan 11th from 8:00am - 2:45pm Where: The Crescent Room (see map for directions: https://www.towncountry.com/hotel-map). If you are planning to attend and have not yet signed up for a topic please add your name to our signup page: https://docs.google.com/spreadsheets/d/1agEK8S4yxphTOC7cojvsVjTxsPH5PenvtHDBDz5XotE/edit#gid=0 We have three major coding topics and one topic for discussion. These include: 1. Tripal 4 Proof of Concept implementing Python and microservices. 2. Implementation of the Breeders API for Tripal. 3. Updates to Chado. 4. Discussion: Scientific Advisory Committee Discussion *Tripal Face-to-Face User's Meeting* When: Friday Jan 10th 3pm-5pm. Where: Crescent Room. This meeting is open to all who want to attend. The major topic to be discussed will be Tripal Governance, in particular creation of a scientific advisory committee for Tripal. *Tripal Workshop* When: Sunday Jan 13th 4pm-6:00pm Where: California Room See the list of speakers here: https://plan.core-apps.com/pag_2019/event/9441a7255c56cf0ce04b90bfc40903c5 ** |
From: Stephen F. <ste...@ws...> - 2019-01-02 18:23:25
|
Dear Tripal Community, The Tripal Galaxy module v1.0 is now available for Tripal v3! It allows you to integrate Galaxy workflows with your Tripal site in two ways 1. Creating web-forms for existing workflows. Users can submit analytical jobs to a Galaxy server through your site using data on your site. The Tripal Galaxy module automatically generates a form for the workflow. 2. Using the Tripal Galaxy API you can create Tripal-compatible applications that are powered behind-the-scenes with Galaxy workflows. Full instructions (installation and usage) are provided at: https://tripal-galaxy.readthedocs.io/en/latest/index.html. Some additional testing is required to ensure full compatibility with Tripal v2. Watch for an updated release. Drupal project page: https://www.drupal.org/project/tripal_galaxy GitHub source code: https://github.com/tripal/tripal_galaxy -- Stephen Ficklin, PhD Assistant Professor Bioinformatics and Systems Genetics Department of Horticulture Washington State University 153 Johnson Hall Pullman, WA 99164-6414 Office: (509) 335-4295 http://ficklinlab.cahnrs.wsu.edu/ |
From: Stephen F. <spf...@gm...> - 2018-12-11 18:24:25
|
Dear Tripal Community, We are looking to setup a Tripal Advisory Committee. It's purpose will be to provide scientific and technological guidance to the Tripal Project Management Committee to help ensure that stakeholder's voices are heard, and that Tripal development proceeds in a manner that meets future needs. I have created an issue on our GitHub project for discussion of our current proposal. https://github.com/tripal/tripal/issues/786 We welcome anyone to contribute thoughts. I would like to see the first Tripal Advisory Committee organized early in 2019. Thanks, Stephen |
From: Stephen F. <spf...@gm...> - 2018-12-11 03:59:38
|
Hello, if you are participating in our Tripal v4 Proof of Concept efforts (or would like to be), below is the connection details for our meeting tomorrow. The Meeting is at 8am US PST, 11 am EST, 5pm European Central. Chat soon! Please download and import the following iCalendar (.ics) files to your calendar system. Monthly: https://zoom.us/meeting/455940438/ics?icsToken=41bf372d296005c816afb7d3ba49cc609553220f54d8a194f104582dcced2b9b Join Zoom Meeting https://zoom.us/j/455940438 One tap mobile +14086380968,,455940438# US (San Jose) +16699006833,,455940438# US (San Jose) Dial by your location +1 408 638 0968 US (San Jose) +1 669 900 6833 US (San Jose) +1 646 876 9923 US (New York) Meeting ID: 455 940 438 Find your local number: https://zoom.us/u/cXre9E3v8 |
From: Stephen F. <spf...@gm...> - 2018-12-08 08:46:51
|
Dear Tripal Users, A bit of information about extension modules.... *New Modules List* We have simplified the list of Tripal Extension modules to hopefully make it easier for us to maintain and for you to find what's out there. In the past anyone with an extension module could log on to the http://tripal.info site and submit a record describing their module. Unfortunately those records became stale or folks did not submit them. They were available under the "Extensions" link at the top of the Tripal website. Now, we have created a new "Extension Modules" section in the online Tripal documentation that categorizes each module and provides links to the documentation and code. This list should be easier to maintain and anyone can edit directly via GitHub. Please check it out and let us know if we've missed any of your modules. You can find it by clicking on that same "Extensions" link on the Tripal website. For your convenience here is the link: https://tripal.readthedocs.io/en/latest/extensions.html. (We did not list modules that are deprecated, do not install on other Tripal sites or are not Tripal v3 compatible). *Module Ratings System* On a related note, the Tripal Program Management Committee (PMC) has discussed a way to rate extension modules. It is easy to advertise a module as being Tripal compatible, but sometimes modules are not sufficiently generic to work on all Tripal sites. Sometimes they only work on the sites of the developers who made them, or they are not sufficiently generic to allow others to take advantage of all features. To help improve the quality of modules and to help us know what to expect from modules before we install them we'd like to introduce a rating system for modules: bronze, silver and gold levels. We have listed our initial idea for rating criteria on this issue page: https://github.com/tripal/tripal/issues/774. Please take a look and let us know if you think these criteria are fair, or if we can change them. Thanks! Stephen |
From: Guignon, V. (Bioversity-France) <v.g...@cg...> - 2018-12-07 15:54:08
|
The next "BrAPI-pre-PAG-codefest" meeting will be on next Wednesday December the 12th at 5pm Paris time. https://www.timeanddate.com/worldclock/fixedtime.html?iso=20181212T1600 Please consider having a look to this short presentation https://docs.google.com/presentation/d/18Iix10NxfNKq5wVCjmz_L28BlaeAcQIg5Fm1fzQjmdE/edit?usp=sharing before the meeting, thanks. Use the following GoTo meeting link for that meeting: https://global.gotomeeting.com/join/173361157 Val From: Guignon, Valentin (Bioversity-France) [mailto:v.g...@cg...] Sent: mercredi 5 décembre 2018 14:18 To: gmo...@li... Subject: [Gmod-tripal] Tripal + BrAPI pre-codefest meeting 2 Hi there! since a couple of people wanted to attempt to the BrAPI meeting but couldn't because of other meetings, we decided to open a second meeting to continue the first one discussions. If you would like to join, please fill the doodle to find a date *before this Friday* (dec. 7th, 4pm Paris time): https://doodle.com/poll/xm9bet6qma24u9ut Proposed dates are all at 5pm (to 6pm) Paris time (like other Tripal meeting hours): December 11, 12, 13, 14, 17 and 18. A mail will be sent between 4pm and 5pm Paris time on Friday to let you know which day has been selected. If you would like to see what has been said during last meeting, here are the notes: https://docs.google.com/document/d/1xm18hsKFoLThkXxZ8FxGZPUREyoW44DWhSQ_N29P-qc/edit?usp=sharing *Before the next meeting*, please have a look to this brief overview of what current BrAPI module can do and think about your specific needs to report them during the meeting: https://docs.google.com/presentation/d/18Iix10NxfNKq5wVCjmz_L28BlaeAcQIg5Fm1fzQjmdE/edit?usp=sharing Cheers, Val |
From: Guignon, V. (Bioversity-France) <v.g...@cg...> - 2018-12-05 13:34:27
|
Hi there! since a couple of people wanted to attempt to the BrAPI meeting but couldn't because of other meetings, we decided to open a second meeting to continue the first one discussions. If you would like to join, please fill the doodle to find a date *before this Friday* (dec. 7th, 4pm Paris time): https://doodle.com/poll/xm9bet6qma24u9ut Proposed dates are all at 5pm (to 6pm) Paris time (like other Tripal meeting hours): December 11, 12, 13, 14, 17 and 18. A mail will be sent between 4pm and 5pm Paris time on Friday to let you know which day has been selected. If you would like to see what has been said during last meeting, here are the notes: https://docs.google.com/document/d/1xm18hsKFoLThkXxZ8FxGZPUREyoW44DWhSQ_N29P-qc/edit?usp=sharing *Before the next meeting*, please have a look to this brief overview of what current BrAPI module can do and think about your specific needs to report them during the meeting: https://docs.google.com/presentation/d/18Iix10NxfNKq5wVCjmz_L28BlaeAcQIg5Fm1fzQjmdE/edit?usp=sharing Cheers, Val |
From: Guignon, V. (Bioversity-France) <v.g...@cg...> - 2018-12-04 17:21:58
|
Hi, For the "2. Tripal v3 Breeders API (BrAPI) Implementation", you already got the GoTo meeting link https://global.gotomeeting.com/join/173361157 and here is a shared Google doc for the notes: https://docs.google.com/document/d/1xm18hsKFoLThkXxZ8FxGZPUREyoW44DWhSQ_N29P-qc/edit?usp=sharing See you in a couple of minutes! Val -----Original Message----- From: Stephen Ficklin [mailto:ste...@ws...] Sent: lundi 3 décembre 2018 17:52 To: GMOD Tripal <gmo...@li...>; GMOD Schema/Chado List <gmo...@li...> Subject: [Gmod-tripal] Tripal & Chado Codefest Meetings Tomorrow Hi All, Tomorrow the normal Tripal User's Meeting is being moved to plan for the Tripal/Chado Codefest just before PAG in San Diego. To help ensure our Codefest in January is as productive as possible we will have three separate meetings for each of the 3 primary topics for the Codefest. If you will be attending the Codefest and if you can attend the online meeting tomorrow please join one of the of the following meetings below: 1. Tripal v3 Python Proof of Concept. Group Lead: Stephen Ficklin Connect via Zoom: https://zoom.us/j/455940438 2. Tripal v3 Breeders API (BrAPI) Implementation: Group Lead: Valentin Guignon Connect via GoToMeeting https://global.gotomeeting.com/join/173361157 3. Chado Updates (open to non-Tripal developers). Group Lead: Scott Cain Connect via Zoom: https://zoom.us/u/acrqoPpqZ6 The meetings all begin at 5pm European Central, 12pm US Eastern, 10am Regina, 8am US Pacific. You find the time in your area via this link: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20181204T1600 If you are considering attending but have not yet signed up please add your name to our registration document: https://docs.google.com/spreadsheets/d/1agEK8S4yxphTOC7cojvsVjTxsPH5PenvtHDBDz5XotE/edit#gid=0 Chat soon! Stephen -- Stephen Ficklin, PhD Assistant Professor Bioinformatics and Systems Genetics Department of Horticulture Washington State University 153 Johnson Hall Pullman, WA 99164-6414 Office: (509) 335-4295 http://ficklinlab.cahnrs.wsu.edu/ _______________________________________________ Gmod-tripal mailing list Gmo...@li... https://lists.sourceforge.net/lists/listinfo/gmod-tripal |
From: Scott C. <sc...@sc...> - 2018-12-04 16:28:10
|
Hi Stephen, The link for the Chado call doesn't appear to be a "connect" link. It should be a long string of digits I think. Scott On Mon, Dec 3, 2018 at 7:25 AM Stephen Ficklin <ste...@ws...> wrote: > Hi All, > > Tomorrow the normal Tripal User's Meeting is being moved to plan for the > Tripal/Chado Codefest just before PAG in San Diego. To help ensure our > Codefest in January is as productive as possible we will have three > separate meetings for each of the 3 primary topics for the Codefest. If > you will be attending the Codefest and if you can attend the online > meeting tomorrow please join one of the of the following meetings below: > > 1. Tripal v3 Python Proof of Concept. > Group Lead: Stephen Ficklin > Connect via Zoom: https://zoom.us/j/455940438 > > 2. Tripal v3 Breeders API (BrAPI) Implementation: > Group Lead: Valentin Guignon > Connect via GoToMeeting https://global.gotomeeting.com/join/173361157 > > 3. Chado Updates (open to non-Tripal developers). > Group Lead: Scott Cain > Connect via Zoom: https://zoom.us/u/acrqoPpqZ6 > > The meetings all begin at 5pm European Central, 12pm US Eastern, 10am > Regina, 8am US Pacific. You find the time in your area via this link: > > https://www.timeanddate.com/worldclock/fixedtime.html?iso=20181204T1600 > > If you are considering attending but have not yet signed up please add > your name to our registration document: > > https://docs.google.com/spreadsheets/d/1agEK8S4yxphTOC7cojvsVjTxsPH5PenvtHDBDz5XotE/edit#gid=0 > > Chat soon! > Stephen > > -- > Stephen Ficklin, PhD > Assistant Professor > Bioinformatics and Systems Genetics > Department of Horticulture > Washington State University > 153 Johnson Hall > Pullman, WA 99164-6414 > Office: (509) 335-4295 > > http://ficklinlab.cahnrs.wsu.edu/ > > > > _______________________________________________ > Gmod-tripal mailing list > Gmo...@li... > https://lists.sourceforge.net/lists/listinfo/gmod-tripal > -- ------------------------------------------------------------------------ Scott Cain, Ph. D. scott at scottcain dot net GMOD Coordinator (http://gmod.org/) 216-392-3087 Ontario Institute for Cancer Research |