Hi All, Hope you are progressing in working on updated proposals (due this Friday). Please read this workflow to follow test driven development and a suggested workflow - https://google.github.io/gsocguides/mentor/workflow <https://google.github.io/gsocguides/mentor/workflow> especially pay attention to the anti-pattern at the end of the document.
Suresh > On May 4, 2020, at 2:25 PM, Suresh Marru <[email protected]> wrote: > > Hi Vivek, Nick, Akhil, Nayeem, > > Congratulations on your GSoC acceptance!! And welcome to Apache Airavata. > > I am sure you have pointers to GSoC guides in your acceptance emails, in > addition to student guide (https://google.github.io/gsocguides/student/ > <https://google.github.io/gsocguides/student/>), review the mentor guide as > well (https://google.github.io/gsocguides/mentor/community-basics > <https://google.github.io/gsocguides/mentor/community-basics>). Do follow the > readings on “How to ask good questions”. > > A key GSoC aspect to remember: community engagement. Above and beyond summer > coding which you are anyway expected to contribute significantly, more > importantly you should be very active in mailing lists and ask and answer > questions. All of you have scored below par on mailing list communications > and hoping you will fix this during the community bonding period and beyond. > > Your first mid-term evaluation is June 29th, so few logistic things will be > required from all of you (try to get these by May 15th): > > * Post your updated/modified proposal to Airavata Wiki - > https://cwiki.apache.org/confluence/display/AIRAVATA/GSoC+2020 > <https://cwiki.apache.org/confluence/display/AIRAVATA/GSoC+2020> include the > following as a minimum: > * Create a detailed and clear description of the problem you will tackle > between now and June 29th. Yes, lets break this into three phase. Second one > due July 27th and final one due August 24th. It is totally fine if your > problem changes from your original proposal. Lets document the updated goal. > * Crete a good description on how your solution to the above problem will > look like. > * Also discuss of any alternative solutions and featured you considered. > * Describe how to evaluate/test your solution. > > It is expected that your understanding (as well as the communities > understanding) of the problem and feasible solutions will evolve over emmer. > Thats fine, but keep this document updated as you go. > > Lastly, write weekly sprint updates as child pages to the wiki and post them > to this list as well. Here is a good example project to follow: > > Proposal - > https://cwiki.apache.org/confluence/display/AIRAVATA/%5BGSoC+Proposal%5D+Securing+Airavata+API > > <https://cwiki.apache.org/confluence/display/AIRAVATA/[GSoC+Proposal]+Securing+Airavata+API> > Design document (submitted in community bonding period, notice the detailed > updates since proposal) - > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=58851790 > <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=58851790> > Weekly sprints - > https://cwiki.apache.org/confluence/display/AIRAVATA/Sprint+1 > <https://cwiki.apache.org/confluence/display/AIRAVATA/Sprint+1> and > https://cwiki.apache.org/confluence/display/AIRAVATA/Sprint+2 > <https://cwiki.apache.org/confluence/display/AIRAVATA/Sprint+2> > Mid-term evaluation (your June 29th evaluation will be based on such a > report) - > https://cwiki.apache.org/confluence/display/AIRAVATA/Update+for+the+mid+evaluation > > <https://cwiki.apache.org/confluence/display/AIRAVATA/Update+for+the+mid+evaluation> > > Welcome on board and happy coding, > > Cheers, > Suresh
