Welcome to the home of Tripal Development! If you are thinking to yourself "What is Tripal?", head over to our website, Tripal.info.

Current Status

Tripal 4.0-alpha1 has been released!
- Use this version to explore Tripal 4 and begin upgrading or creating extension modules!
- Upgrade path from Tripal 3 will be developed in future alpha releases.
- Note: Tripal 3 sites should be upgraded before November 2023 to keep security support by Drupal.
Development:
- : Focus is on bug fixes
- : Full upgrade to Drupal 9/10 (alpha1 released!).
Tripal and are no longer supported by the Project Management Committee, although we will accept community submitted fixes for Tripal 2.x.

Tripal 4 Testing Status

Drupal	9.3.x	9.4.x	9.5.x	10.0.x
PHP 8.0
PHP 8.1

Tripal 3
Tripal 4
- Requirements
- Use Tripal Docker to explore or develop extension modules.

Looking to contribute? That's Amazing -Welcome!!! Here's a quick run-down to get you started:

We welcome all contributions!
This github issue queue is open to: bug reports, usability concerns, performance issues, site administration or development questions, data storage discussions, etc.
We ask that questions/concerns/bugs with extension modules be addressed in their respective repositories (including those under the Tripal organization).
For feature request, please open an issue with detailed use cases and description. We would love to help you design a generic solution for the community whether it belongs in Tripal Core or an Extension module! Please wait to submit a PR until the Project Management Committee (PMC) indicates it is generally applicable and should be included in Core.
For potential bugs or concerns, please open an issue being as descriptive as possible. Screenshots and steps to reproduce will help us, help you! If you know how to fix the issue, feel free to submit a pull request (PR) linked to the issue!
For documentation contributions, click the "Edit on Github" link at the top of the page you want to improve! Instructions for our flavour of ReadtheDocs can be found on ReadtheDocs.
See our quickstart if you need help on how to submit a PR: ReadtheDocs, how to create a PR.
Click on issues > New Issue for helpful issue templates.

For more detailed guidelines see our full Contribution Documentation!

Don’t be afraid to mention people (@username) who are knowledgeable on the topic or invested. We are academics and overcommitted, it’s too easy for issues to go unanswered: don’t give up on us!
Likewise, don’t be shy about bumping an issue if no one responds after a few days. Balancing responsibilities is hard.
Want to get more involved? Issues marked with “Good beginner issue” are a good place to start if you want to try your hand at submitting a PR.
Everyone is encouraged/welcome to comment on the issue queue! Tell us if you
- are experiencing the same problem
- have tried a suggested fix
- know of a potential solution or work-around
- have an opinion, idea or feedback of any kind!
Be kind when interacting with others on Github! (see Code of Conduct below for further guidelines). We want to foster a welcoming, inclusive community!
- Constructive criticism is welcome and encouraged but should be worded such that it is helpful :-) Direct criticism towards the idea or solution rather than the person and focus on alternatives or improvements.

Be nice! If that’s insufficient, Tripal community defers to https://www.contributor-covenant.org/

Thanks goes to these wonderful people (emoji key):