Hi Jeff, This is very nice. Can you also map these to the architecture diagram you had in your proposal, an illustration always help put it in a better context.
Suresh > On Jun 25, 2016, at 12:19 PM, Jeffery Kinnison <[email protected]> > wrote: > > Is this the sort of thing you're looking for? Does it need anything else? > > https://cwiki.apache.org/confluence/display/AIRAVATA/Update+for+Midterm+Evaluation > > <https://cwiki.apache.org/confluence/display/AIRAVATA/Update+for+Midterm+Evaluation> > > On Sat, Jun 25, 2016 at 10:33 AM, Suresh Marru <[email protected] > <mailto:[email protected]>> wrote: > GSoC Students, > > We (mentors from Airavata) need to turn in our evaluations into the GSOC > system by Sunday Night. Unlike previous years, the new GSOC system does not > allow edit of evaluations once submitted. Once we submit, GSoC admins within > apache will review the code commits and then randomly admins from google. > Airavata has been lucky to receive good number of gsoc slots over the years. > To maintain this, we will have to follow the rules and strictly measure code > contributions. > > To help us do the evaluation, before sunday night please submit the following: > * A detailed modified original gsoc plan. This typically changes during > community bonding period as you understand Airavata better since the proposal > time. > * A detailed progress report with pointers to pull request on where you stand > with the full summer plan. > * Detailed next steps on how you will plan to complete the program with test > cases and documentation. > > You can use [1] as reference. > > Suresh > > [1] - > https://cwiki.apache.org/confluence/display/AIRAVATA/Update+for+the+mid+evaluation > > <https://cwiki.apache.org/confluence/display/AIRAVATA/Update+for+the+mid+evaluation> > > >
