[
https://issues.apache.org/jira/browse/TAVERNA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193816#comment-15193816
]
Stian Soiland-Reyes commented on TAVERNA-881:
---------------------------------------------
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
> Save Taverna workflows as CWL
> -----------------------------
>
> Key: TAVERNA-881
> URL: https://issues.apache.org/jira/browse/TAVERNA-881
> Project: Apache Taverna
> Issue Type: New Feature
> Components: Taverna Language
> Reporter: Stian Soiland-Reyes
> Priority: Minor
> Labels: cwl, gsoc2016
>
> Many Taverna workflows can probably be represented in CWL - so this issue
> proposes to add support for serializing to CWL in Taverna Language.
> I propose a staged approach:
> a) Represent workflow structure only (A->B, B->C, B->D)
> b) Save back CWL activities (from TAVERNA-877)
> c) Save/Load other Taverna activities as TavernaRequirement
> d) Save/Load other Taverna activities as DockerRequirement using TAVERNA-879
> The semantics of CWL does not always allow all the iteration strategies of
> Taverna etc., so presumably only a subset of Taverna workflows could be saved
> correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
