Welcome to the Taverna developers’ community!
The Taverna team welcomes additional input into the development of Taverna. If you wish to develop a plugin for Taverna, write code that uses Taverna or integrate Taverna with your own applications, this is a place for you.
Developers of Taverna or of applications integrating with Taverna will find the following useful.
General
- JIRA system for tracking bugs, issues and development plans
Contributing code
If you wish to contribute to the development of the main Taverna code then you need to sign a Contributor License Agreement (CLA). You can find the CLA appropriate for you in the Contributors’ guide.
If you just wish to use Taverna with your own application then you do not need to sign anything.
Developers’ mailing list
It is also important for developers to join the taverna-hackers mailing list. This is where the developers’ community connects together, gets the latest news on the architecture and APIs and has a chance to express their opinions, provide technical input and discuss issues with other developers.
For Taverna 2.x developers
- Developers’ wiki containing the Developers’ guide among other things
- Taverna 2.x snapshot nightly builds
- Taverna 2.x source in SVN
- Hudson output from Taverna 2.x unit and integration tests
- Information on how to use the Taverna 2.x SVN codebase and build the source code
- Taverna 2.x architecture overview and technical papers
- Developing plugins
- Taverna 2.x API Javadocs
- SCUFL2, Taverna’s next workflow definition language and API
For Taverna 1.7.x developers
- Developers’ guide
- Taverna 1.7.x source in CVS
- Taverna 1.7.x architecture overview and technical papers
- Developing plugins
- Taverna 1.7.x API Javadocs
For Web service developers
- Advice for developers of Web services that are intended to be consumed from Taverna
