Tripal PMC Meeting 2018/11/19

Meeting Date
Attendees

Bradford Condon, Lacey Sanderson, Stephen Ficklin

Major Issues  #1

Tripal Annotation Extensions

Ready:

  • Tripal Analysis Blast

  • Tripal Analysis InterproScan

    • Minor issues, minor fixes?  Stil ready for release (BC’s opinion)

    • Coordinate issue: clarify in instructions.

  • Need updated README.

Not Ready:

  • Tripal Analysis KEGG

    • Possible solution: Chado DBs can be linked.  See EDAM problem.

      • OBO loader would need to be updated for the db-linker.

    • No README.md

 

Should we deprecate?

  • Tripal Analysis GO

    • Just an importer.   Could easily be a bulk loader instead?

    • No display field, for example.

    • Do we bother releasing as 3.0?

  • Tripal Analysis Unigene

    • Obviously deprecated

 

Major #2  New Tripal v3 Release

Current bugs are preventing creation of content.

Extensions

  1. Add the Tripal Docker, Python Tripal

  2. Gold/Silver/Bronze

    1. Purpose: The Tripal Community recognizes these qualities as making good code.  They are ideals to strive for…..

    2. “Terms and conditions apply” we can change the list and you need to do something to qualify for silver again.

    3.  What is the list of extension criteria?

      1. Bronze:
        1. Has a public release that follows Drupal release naming rules.

        2. Should install on any Tripal site

          1. defines any custom tables or mviews

          2. adds any needed controlled vocabulary terms

        3. Installation and admin instructions README.md (or RTD)

        4. Need a license (distributed with module)

      2. Silver:
        1. Follows Drupal code standards (how to measure this?)

        2. USING TripalField class to add data to pages.

        3. Use tripal API functions

          1. Queries Chado using chado_generate_var, chado_expand_var, the ChadoRecord class or chado_xxx_record functions (except for complicated queries).

        4. Provides an admin interface to allow for customization

      3. Gold:
        1. Imports data via Tripal's importer class

        2. Tripal 3 fields are fully compatible with web services

          1. The elementInfo function is fully implemented.

          2. Field as query and queryOrder functions fully implemented.

        3. Web Services uses Tripal's Web Service Classes.

        4. PHPUnit testing

        5. CI testing

        6. Project should have a public development branch (following Drupal naming rules) to encourage collaboration and pull requests.

        7. Extensive documentation for the module (similar to Tripal User's Guide).

 

Cross-compatibility?

Requirements function in the install file so that it wont install without tripal 3 or 2.  

See: Tripal Galaxy install