Taverna Open Development workshop, Manchester, 2014-10-30
This work is licensed under a Creative Commons Attribution 4.0 International License.
... or at least according to a quick look at
sourceforge/cvs/svn/git history
and occassional dips into Stian's memory
myGrid: 6 academic institutions and 8 industry partners
Challenge: Create a graphical workbench for bioinformaticians to combine data and web services
Source+binary releases on SourceForge.net
Local CVS servers → SourceForge.net CVS
Apache Maven-based build
executeworkflow command line
Raven plugin system
Taverna Remote Execution Service
Preview of t2core workflow engine
SourceForge CVS → GoogleCode SVN
t2core workflow engine
Reimplemented workbench
Improved support for 3rd-party plugins
Taverna Server + ruby gem
Domain-specific editions
(astronomy, bioinformatics, biodiversity, digital preservation)
GoogleCode SVN → GitHub
Plugin system too strict on versioning of dependencies
Every new release of Taverna Workbench made existing plugins incompatible
Maintaining our own classloader implementation - hard!
Building a release difficult -
several weeks including testing
OSGi-based plugin system
Engine separated from workbench/commandline/server
Independent APIs for workflow and data format
Taverna Platform - execution API
Apache Taverna (incubating)
Non-profit organization, forming a community of open-source software projects.
Strong emphasis on openness, collaboration and a consensus-based development process.
Examples: Apache HTTP server, Tomcat, Maven,
Jena, CXF and OpenOffice.
Graduation path for becoming an Apache project
Champion: Andy Seaborne (Apache Jena)
Proposal submitted 2014-09-23
Volunteering mentors:
Fully investigate/resolve incompatibly licensed dependencies
Stage git repositories for move at https://github.com/taverna-incubator :
# Git repository groupId / Java package name
apache/taverna-maven-parent org.apache.taverna parent
apache/taverna-utils org.apache.taverna # Still neded?
apache/taverna-engine-api org.apache.taverna.engine
taverna-core-api org.apache.taverna.core
taverna-platform-api org.apache.taverna.platform
apache/taverna-engine-impl org.apache.taverna.engine.impl
taverna-core-impl org.apache.taverna.core.impl
taverna-platform-impl org.apache.taverna.platform.impl
taverna-rest-activity org.apache.taverna.rest.activity
taverna-script-activity org.apache.taverna.script.activity
taverna-interaction-activity org.apache.taverna.interaction.activity
apache/taverna-scufl2 org.apache.taverna.scufl2
apache/taverna-databundle org.apache.taverna.databundle
apache/taverna-workbench-api org.apache.taverna.workbench.api
org.apache.taverna.workbench.api.activitypalette
org.apache.taverna.workbench.api.menu
apache/taverna-workbench-impl org.apache.taverna.workbench.impl
org.apache.taverna.workbench.impl.activitypalette
org.apache.taverna.workbench.impl.menu
org.apache.taverna.workbench.impl.diagram
org.apache.taverna.rest.workbench
org.apache.taverna.script.workbench
apache/taverna-commandline-product
apache/taverna-workbench-product
apache/taverna-server org.apache.taverna.server
apache/taverna-plugin-biomart org.apache.taverna.biomart
org.apache.taverna.biomart.activity
org.apache.taverna.biomart.workbench
apache/taverna-plugin-soaplab org.apache.taverna.soaplab
# Optional non-Apache plugins (e.g. due to LGPL/GPL dependencies)
taverna/taverna-plugin-rshell com.github.taverna.rshell
taverna/taverna-plugin-beanshell com.github.taverna.beanshell
astrotaverna/taverna-plugin-astrotaverna com.github.astrotaverna.plugin
astrotaverna/astrotaverna-workbench-product com.github.astrotaverna.workbench
johndoe/taverna-plugin-helloworld com.example.helloworld.taverna
Not going into Apache Incubator
"The final release": Taverna 2.5.1 (really soon now)
Security fixes only until Apache Taverna 3.0.0 is released
Fully open development
All discussion and decisions to be made on dev@taverna.incubator.apache.org mailing list
Mailing list open to all - not just committers
Voting on releases
Developer infrastructure managed by Apache
Plugin developers (e.g. Kevin, Dmitry)
Integrators (e.g. Vadim, Susheel, Yassene)
Core developers (e.g. Manchester, Dmitry)
Scientific Workflow researchers (e.g. Gabor, Pinar)
Submitting patches/pull requests
Contributing to mailing lists
Contributing to testing and documentation
Contributing a plugin
Be active on mailing lists
Find and invite plugin developers and integrators
Code documentation/examples/tutorials
Community webinars?
"I found a bug, but I am not sure how to fix it"
→ Online mentoring?
... your suggestion?