Big +1. This(last paragarph) is exactly what you need to do to graduate from the incubator.
Marlon On 4/29/15, 10:52 AM, "Ian Dunlop" <ian.dun...@manchester.ac.uk> wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA512 > >Hello, > >Here are some good practice around the community bonding period from >http://en.flossmanuals.net/GSoCMentoring/mind-the-gap/. > >* Prepare students to immediately start writing code at the official >start of coding. >* Get students engaged socially in the project. >* Provide time for students to learn about the development practices >of the organization. >* Ensure that students have a development environment set up. This >includes getting set up with the project version control system and >reading up on necessary documentation. >* Further refine the strategic plan for project completion. >* Get required forms filled out, such as the tax forms required by >Google, any contributor license agreements, and any paperwork that >your project requires. > >We've started looking at some of these already which is great but we >need to keep the momentum going and ensure that the dev environment >and tools (git, jira etc) are ready to go by the end of the community >bonding period. Students need to look into the forms part as well as >mentors so that any CLAs, tax requirements are taken care of. >There is not much about development practices on >http://taverna.incubator.apache.org/download/code/. I think that >commit often, unit test lots and write documentation are key points. >No matter how much you think your code is self documenting, it >probably isn't! > >Cheers, > >Ian > >On 29/04/2015 15:39, Pierce, Marlon wrote: >> Recorded google hangouts are ok. >> >> Marlon >> >> On 4/29/15, 10:34 AM, "Ian Dunlop" <ian.dun...@manchester.ac.uk> >> wrote: >> >> Hello, >> >> Just reading >> http://en.flossmanuals.net/GSoCMentoring/notes-for-first-year-organiza >ti >> >> >ons/ >> >> and saw this >> >> "Make all communication public. If it didn¹t happen in public, it >> didn¹t happen." >> >> Maybe we should keep as much as possible to the lists (and maybe >> IRC since I think it is all logged). >> >> Cheers, >> >> Ian >> >> >> >> On 29/04/2015 15:29, Ian Dunlop wrote: >>>>> Hello, >>>>> >>>>> Hi there Larry and other GSoC students. Congratulations on >>>>> getting selected. I'm the main mentor for the Android app. I >>>>> guess we are all just getting up to speed with the issues >>>>> tracker and code repo. From my understanding we will use the >>>>> apache taverna jira for issues >>>>> >>>>> https://issues.apache.org/jira/browse/TAVERNA/ >>>>> >>>>> Which means we need to set up a project for the Android app >>>>> and the other GSoc projects. Are all your jira accounts >>>>> working OK? We also need to decide where to host the code. >>>>> @Stian etc Are we ok to use the apache taverna git repo? Do >>>>> the students need to sign CLAs? >>>>> >>>>> For day to day comms I am happy to use skype, hangouts or IRC >>>>> (when I remember to start the client!) - which do you prefer. >>>>> Its also nice to keep updates coming to the list so that we >>>>> all have a record of what is going on. I guess we will need >>>>> to find a balance between what we keep between mentors and >>>>> students and what we send to the list. >>>>> >>>>> I hope we all have a successful summer of code. >>>>> >>>>> Cheers, >>>>> >>>>> Ian >>>>> >>>>> On 28/04/2015 17:37, Larry Akah wrote: >>>>>> yeah , i've successfully logged-in . Who's in charge of >>>>>> the mobile app component part? I don't see any of the GSOC >>>>>> components anywhere. Thanks >>>>> >>>>>> 2015-04-28 17:21 GMT+01:00 Stian Soiland-Reyes >>>>>> <st...@apache.org>: >>>>> >>>>>>> Agree, let's just do three GSOC components in Jira for >>>>>>> now. (Done) >>>>>>> >>>>>>> The Taverna Language Command Line Tool should in theory >>>>>>> just be a branch/module of taverna-language - but we can >>>>>>> easily merge that post-GSOC. >>>>>>> >>>>>>> >>>>>>> Menaka, I've added you as lead on the Taverna Language >>>>>>> Command line tool and added you as a Contributor as >>>>>>> well. >>>>>>> >>>>>>> >>>>>>> That leaves Denis for the Databundle viewer - do you have >>>>>>> a Jira account? >>>>>>> >>>>>>> >>>>>>> So I would suggest to create the overall milestones from >>>>>>> your proposal as separate Tasks in Jira and connect them >>>>>>> to your Component. A Task can have Sub-tasks which >>>>>>> should be tiny stuff (e.g. 1d effort). >>>>>>> >>>>>>> >>>>>>> We should start a separate thread to sort out source >>>>>>> code repositories and CLAs. >>>>>>> >>>>>>> >>>>>>> On 28 April 2015 at 17:07, alaninmcr >>>>>>> <alanin...@googlemail.com> wrote: >>>>>>>> On 28/04/2015 16:56, Larry Akah wrote: >>>>>>>>> >>>>>>>>> y Jira name should be Larry Akah. >>>>>>>> >>>>>>>> >>>>>>>> Are you able to log in? >>>>>>>> >>>>>>>> I think there should be a separate Jira component for >>>>>>>> each of the GSOC projects, so: >>>>>>>> >>>>>>>> "Taverna Mobile App", "Taverna language command line >>>>>>>> tool" and >>>>>>> "Databundle >>>>>>>> viewer. >>>>>>>> >>>>>>>> Issues for the new command line interface could go >>>>>>>> inside the existing "Taverna Commandline" but I think >>>>>>>> that would be confusing. >>>>>>>> >>>>>>>> What do other people think? >>>>>>>> >>>>>>>>> Cheers >>>>>>>> >>>>>>>> >>>>>>>> Alan >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- Stian Soiland-Reyes Apache Taverna (incubating), >>>>>>> Apache Commons RDF (incubating) >>>>>>> http://orcid.org/0000-0001-9842-9718 >>>>>>> >>>>> >>>>> >>>>> >>>>> >> >-----BEGIN PGP SIGNATURE----- >Comment: GPGTools - https://gpgtools.org > >iQEcBAEBCgAGBQJVQPAtAAoJEPK45GBX+Cy576oH/RbI6rLl2WVwlFw5K7vRrDgP >D09euV8H+nAG89b+e3Ceyd5LqdCPKGLeRNbPhmVDEBzwrNDNe6AcD/A+nHFQL81p >0MzXrfw4Y+keazKHdGhpbYkLUo7VINKbeBTNaUVVrkbTfPd/eBJmi4aNE2nJnmw9 >Ne6vSeT8ckXApztyze657DpI9GjSR/Z4bMlDNuACGe7NXeTcX8ILIy3hbevDXwka >446N0r3Y/h1FFh440RRONT8Dr0mXQ5F4ERnWbIz0fZi8wzIvgqI5GzItqpNKTvpl >fo1DLJFy3pJe3fF8uak2/WG1nEiavvlOmqbaUUYnfgBrfdWT4rU1PvRdmXgLGsA= >=U4W9 >-----END PGP SIGNATURE-----
