On 23 April 2016 at 22:47, Maรฑana <[email protected]> wrote: > Hi stain and michael , > > I am thilina manamgoda . My proposal ( TAVERNA-880 Browse+use CWL > tool descriptions h)has been selected ๐๐ for gsoc 2016 .So what ' next . > Please provide me a guide line ๐.
Hi! Congratulations to both you and Nadeesh on acceptance as GSOC students! Also congratulations to Rajan who got accepted for his Mifos Initiative Field App proposal (his preference over the Taverna Mobile proposal)! ## Issue tracker If you give me your account names on http://issues.apache.org/ I can grant you access there to manage issues in the Jira bug tracker for Taverna. ## Git branches Next I think we'll create some branches for you in git with some empty folders which you can start providing pull requests for as soon as you have something (even while it's in Taverna 2 land). It should work well to submit pull requests say every week or so so the code changes are not too massive for us to review. This also would help to show mentors your progress (or as can happen) where you are stuck. ## GitHub pull requests Do you already have a GitHub account, and are you familiar with pull requests? Perhaps now is a good time to read up on those. Generally your code would probably fit best within the incubator-taverna-workbench-common-activities repository - as that where is activity-browsing. We can also make a branch in taverna-common-activities for the cwl "dummy" activity. ## ICLA Legally you will need to fill in, sign and submit a ICLA to Apache Software Foundation so that we'll be allowed to redistribute your code. See https://www.apache.org/licenses/icla.txt (You would need to send it to [email protected], by fax ) If you do this earlier, it makes it easier for us to accept your code early rather than requiring an additional Intellectual Property clearance process at the end of your project. (BTW - this is the pattern we have used for Google Summer of Code students) If you have PGP/GPG, then you can do it fully electronically: 1) Make sure you have made a GPG key with your full name, and it has been published (gpg --send-key) 2) Fill in icla.txt in a text editor 3) Sign it with gpg --sign --armor --detach icla.txt 4) pre-flight check: gpg --verify icla.txt.asc 5) email both icla.txt and icla.txt.asc to [email protected] See http://www.apache.org/dev/openpgp.html for details on gpg. or go old skool (probably faster, but more boring): 1) Fill in icla.txt in a text editor 2) Print and sign by hand 3a) scan and email to [email protected] or 3b) send by fax +1-919-573-9199 (3c) you probably don't want to do send it by post as it could take a long time) Once the ICLA has been registered by the secretary we should be able to find it on https://home.apache.org/unlistedclas.html ## Dependencies and licenses Your plugin code need to use dependencies that are compatible with the Apache license - http://www.apache.org/legal/resolved.html - in short GPL and LGPL are not allowed, but pretty much anything open source is OK as a pom.xml dependency. Feel free to ask on the list about dependencies and we can help you review the licenses. Inclusion of third-party work in the source code (e.g. copy and paste) is much trickier area - avoid this if possible. This is particularly tricky if you find something on Stack Overflow. Feel free to ask on this list or the mentors if you are stuck on anything - e.g. your ArrayList comes out in the wrong order or some code won't compile. In your code, all files should have an Apache license file header, see for example: https://github.com/apache/incubator-taverna-language/blob/master/taverna-robundle/src/main/java/org/apache/taverna/robundle/Bundle.java#L3 (*.java) https://github.com/apache/incubator-taverna-language/blob/master/pom.xml#L2 (*.xml) ## Packages I would us a package name like org.apache.taverna.cwl.ui (for the activity-ui) and org.apache.taverna.cwl (for the activity) Likewise, in Maven, use groupId that matches the git repository's top-level pom.xml, e.g. org.apache.taverna.commonactivities or org.apache.taverna.workbench.commonactivities Likewise atifactId that matches the siblings, e.g. taverna-docker-activity, taverna-cwl-activity, taverna-cwl-activity-ui. ## Timeline Then just follow your plan and the GSOC timeline - officially coding starts 2016-05-23, but you are of course free to start coding earlier. :) The first month (2016-04-22 / 2016-05-22) is in a sense unpaid, a "Community Bonding period". You have done well already with getting to know both communities - but this is also the time to learn how both Taverna and CWL communities work and how you can interact and contribute. We hope you both give comments on other aspects of Taverna/CWL than just your particular project! Don't worry that you are new to the projects - we've all been there. Still even "old timers" have to ask each-other when we don't remember how things work. ## Learn the technologies I believe both of you have had a look at the Taverna Activity and Activity UI plugin tutorials. Playing with those and just getting to know Taverna is a good start. Please report any issues you find when doing so - e.g. if something is outdated in the documentation. This is also when you can get to know better the technologies Taverna and CWL/Docker - Thilina may also want to look at the CWL specs and raise any questions and improvements with CWL community - say if something is confusing or ambigious this could be fixed in newer version of the spec. http://www.commonwl.org/draft-3/ and in particular: http://www.commonwl.org/draft-3/CommandLineTool.html ## Participate, contribute! This is a good time for you to join in discussions on the mailing lists - for instance now we are planning a release of the Taverna Command Line which both of you may need later for testing - and part of release process at Apache is that he community (that includes you and everyone on this list) will be able to test the Release Candidates and provide feedback. I hope you would be willing to have a go - more details will follow. So good luck to you both - and stay in touch with the list! I think both myself and Alan are available also for private mentor-related questions - so for me using Skype text chat is a good way to catch my attention (roughly Mon-Fri 09-17 BST). I've not been to good following the CWL Gitter room - but I'll try a bit harder now. We have a #Taverna IRC room, but I know it's pretty quiet due to the synchronous nature of IRC - so I would not rely on that - rather just start a new email thread or Jira issue with a question. -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/0000-0001-9842-9718
