Hi, I think time has come for us to make the final push towards
graduation of Taverna from the incubator.


Some bureaucracy left, I'm afraid - maturity assessment needs filling in:

https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-03+Taverna+Graduation+Maturity+Assessment


I don't think we need to make the maturity assessment too detailed.
Here's one I just did for Commons RDF

https://github.com/apache/incubator-commonsrdf/blob/master/MATURITY.md

(admittedly that had a lower barrier as it does not graduate to a top
level proejct)


So unless someone screams I'll go ahead and fill in similarly in the
Taverna report in the wiki.



However what complicates things for us is that we have several git
repositories, but not all of them have gone through an Apache release
yet.

We could drop some of the repositories from ASF (I'm thinking
incubator-taverna-plugin-bioinformatics) and move those to
taverna-extras -- not sure if it would make sense to do that with the
workbench which you do kind of need to make Taverna workflows :)


So we do need to somewhat complete the license review:

https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-09+License+review

I think we should flag in Jira anything that requires attention in the
unreleased source code, like the XSD files in Taverna Server.


The way it was done for Taverna Mobile I think is great:

https://cwiki.apache.org/confluence/display/TAVERNADEV/Taverna+Mobile+Licence+Review

-- 
Stian Soiland-Reyes
http://orcid.org/0000-0001-9842-9718

Reply via email to