[
https://issues.apache.org/jira/browse/TAVERNA-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193817#comment-15193817
]
Stian Soiland-Reyes commented on TAVERNA-879:
---------------------------------------------
Hi, potential Google Summer of Code (GSOC) students!
In a tiny hour the GSOC student application period opens:
> https://developers.google.com/open-source/gsoc/timeline
> 14 March 19:00 UTC Student application period opens.
> 25 March 19:00 UTC Student application deadline.
http://write.flossmanuals.net/gsocstudentguide/ has a good description
of the process.
I've tried to summarize who is interested in what here:
https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-03+GSOC+2016
My apologies for any mistakes or if I forgot someone.. it was a bit
hard to track across all the emails! Let me know what to fix.
If you are preparing a GSOC proposal for Apache Taverna, e.g. inspired
by our ideas at:
https://s.apache.org/taverna-gsoc-2016
or your own ideas (e.g further developing Taverna Mobile), then
now is a good time to start working on your project proposal.
I suggest writing a Google Docs page, and sharing it on dev@taverna (which
hopefully you have signed up to - see
http://taverna.incubator.apache.org/contact)
.. or leave a comment on this Jira Issue so we can discuss it and help you get
a good proposal!
See http://write.flossmanuals.net/gsocstudentguide/writing-a-proposal/
for suggestions for your proposal, and a template here:
http://community.staging.apache.org/gsoc#application-template
> Docker command line tool for Taverna Activity
> ---------------------------------------------
>
> Key: TAVERNA-879
> URL: https://issues.apache.org/jira/browse/TAVERNA-879
> Project: Apache Taverna
> Issue Type: New Feature
> Components: Taverna Common Activities
> Reporter: Stian Soiland-Reyes
> Priority: Minor
> Labels: cwl, docker, gsoc2016
>
> If Taverna workflows are to be represented in CWL, then the problem is that
> our activity descriptions are only usable within Taverna. (Except the Tool
> Activity which could be represented as a ShellCommandRequirement).
> A quick-and-dirty CWL representation of any Taverna workflow would need a
> TavernaActivityRequirement - but obviously only Taverna could read those back
> in.
> So a better approach could be to have a Docker image (in CWL using a
> DockerRequirement) that executes a Taverna Activity as an independent step -
> that would mean Taverna activities like WSDL and REST activities can be used
> in CWL.
> One way to do this today is for a Docker image that generate a simple SCUFL2
> workflow that executes just that single activity, and then just runs
> Taverna's executeworkflow.
> Taverna's CWL reader could then recognize these and re-instate the Taverna
> activity (as this Docker tool can keep the existing Taverna Activity JSON as
> its own configuration).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
