My understanding: Apache will have to do ranking of the student proposals across all projects, and then Google decides how many slots Apache gets overall.
So I think better have some proposals students can pick from, we will probably not get that many proposals on all of the ideas anyway. Your ideas sound great, specially the docker/cloud ones. We do already have docker image for Taverna server though - and its not something that takes 3 weeks to make. Perhaps a more interesting one would be to add docker support for the Tool Activity so we can have (and bundle) truly reproducible workflows. On 9 Mar 2015 14:10, "alaninmcr" <[email protected]> wrote: > On 08/03/2015 22:49, Stian Soiland-Reyes wrote: > > [snip] > > Feel free to propose other gsoc project ideas in the COMDEV jira (as our >> own Jira is not yet imported) - use the label gsoc2015 and prefix title >> with Taverna: >> > > I do have four ideas, but am wary of running out of (or overloading) > mentors. > > The ideas are: > > (a) Create docker images for Taverna, Taverna CLT and Taverna Server. Look > at creating workflow-specific docker images and CLTs so you can have a > workflow runner "in a box". > > (b) Extend the tool service so that it can execute commands on a host > spawned by Cloudstack. > > (c) Use DFDL annotation to describe the data that will be input/output on > a port. Using the annotation, be able to specify the extraction of specific > parts of the data - see XPath service. > > (d) Make the OpenRefine extension developed during the BioVeL project > easier to install and use. > > Alan > >
