Starting point for developers working with Taverna and Taverna's source code.
- IRC chat
- Taverna source code
- Development, release and testing procedures
- Taverna workflow architecture
- Taverna home directory
- Taverna startup (installation) directory
- Extension points
- Taverna installers
- Taverna 2 Architecture
- Technical Papers
Software releases hosting
- Version 3.0 (planned): Apache
- Version 2.5: BitBucket (backup: GitHub, myGrid internal)
- Version 2.4, 2.3, 2.2, 2.1 Launchpad (backup: GoogleCode, myGrid internal)
- Taverna 1.x and 2.0: SourceForge
Version control management
- Apache Taverna 3: http://taverna.incubator.apache.org/download/code/
- Taverna 2: github.com/taverna
- Structure of Taverna's Subversion repository (outdated)
- Checking out Taverna source code, compiling, running and debugging (outdated)
Build and release system
- Structure of Maven modules
- Automatic build system Jenkins
- workbench-distro project
- Release procedures
- Branching/tagging for release
- Making installers
We have an IRC chat channel #taverna on freenode.net for general discussion on Taverna and Taverna development.
The procedures we follow when developing code and making Taverna releases.
Tutorials for developers to get started with working with Taverna or developing plugins for Taverna.
Taverna home directory is used for runtime information specific to the current user or configuration settings specific to that user.
Taverna startup (installation) directory is the directory where you installed Taverna and where you run it from.
Extension points in Taverna are interfaces which can be implemented by different modules and plugins to extend and add functionality to the workflow engine and workbench.
SCUFL2 is the proposed new mechanism for specifying Taverna workflows. SCUFL2 defines a model, a workflow bundle file format (.wfbundle), and a Java API for working with workflow structures. SCUFL2 is the workflow language for Taverna 3, and replaces Taverna 2's t2flow format.