Welcome to Tripal Country!
Today I'm sharing my suggestions on how to set up your module.
If you create custom Tripal Modules, here are some best practices and suggestions.
We recommend making your code open source and hosting it on GitHub. It's free, it let's people easily find, use, and contribute to your source code.
Once your module is on GitHub, consider joining the Tripal organization. Your lab group can exist as a team and maintain control over your code, but your projects will be listed in the main Tripal group.
If you'd rather not, you can still tag your project as Tripal by clicking on the Manage Topics Link at the top of your repository.
When your module is release ready, why not create a Digital Object Identifier (DOI) for it with Zenodo? It's free! Sync your github account and create a new release (Zenodo won't find old releases). You can then display your DOI badge on your module's page.
Additionally, there is a Tripal Community group on Zenodo. You can edit your record to associate your DOI with the Tripal community.
A Tripal Test module is coming soon, which will automatically set up a PHPUnit and Travis testing environment for you.
Every repository can include a README file that will be displayed on the repository page. A README file should at a minimum include:
Consider documenting your Code itself. Tripal documents in the Doxygen style which allows documentation webpages to be automatically generated. Even if you don't build HTML documentation, the in-line code documentation will be very helpful to contributors.
Drupal has defined coding standards that Tripal modules should meet.