Tripal PMC Meeting 2019/02/11

Meeting Date
Attendees

Bradford, Lacey, Stephen

  • Tripal microservices proof of concept discussion.

    • Stephen will contact EC

 

Tripal 3.1 release

  • https://github.com/tripal/tripal/projects/4

  • Test the tripal_install module.

  • Don’t wait for blast, interpro releases.

  • Don’t wait for tripal.info site d8 registration (put in 3.2 release instead)

  • Module rating system in RTD.

Tripal 3.2 goals

  • https://github.com/tripal/tripal/projects/5

  • Tripal registration form and Tripal.info D8 site needs to be in production.

  • We need to tag open issues that should be on the 3.2 release.

  • Open pull requests merge on this version.

Module rating system

  • https://github.com/tripal/tripal/issues/774

  • How “Drupal” should requirements for styling, branches, releases, pushing to Drupal, be?  Vs recommendations.

  • Action item: Lacey to clean this up and make a PR for review.

Bronze

  • Any Tripal version

    • Has a public release that follows Drupal release naming rules.

    • Should install on a Tripal site appropriate for the versions it supports.

    • Defines any custom tables or mviews in the install file (if applicable).

    • Provides Installation and admin instructions README.md (or RTD)

    • Has a license (distributed with module)

  • Tripal v3 specific

    • Adds any needed controlled vocabulary terms in the install file  (if applicable)

Silver

  • Any Tripal version

    • Follows Drupal code standards (how to measure this?)

    • Use tripal API functions (is this too generic)?

      • Uses the Chado API: Queries Chado using chado_generate_var, chado_expand_var, the ChadoRecord class or chado_xxx_record functions (except for complicated queries).

    • Provides an admin interface to allow for customization

    • Latest releases should follow drupal best practices.

      • e.g. first release for Drupal 7 should be: 7.x-1.x

  • Tripal v3 specific:

    • Uses the TripalField class to add data to pages (if applicable).

 

Gold:

  • Any Tripal version

    • Required:

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

      • Unit testing is implemented using PHPUnit with the TripalTestSuite or something similar.

      • Continuous integration is setup (e.g. such as with TravisCI).

    • Optional (but encouraged):  

      • code sniffing and testing coverage reports.

      • Drupal.org vetted release.

    •  

  • Tripal v3 specific:  

    • Imports data via Tripal's importer class

    • Tripal 3 fields are    

      • Fully compatible with web services

      • The elementInfo function is fully implemented.

      • query and queryOrder functions fully implemented.

      • Web Services uses Tripal's Web Service Classes.

 

Open items

 

Meeting Type
PMC