You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by Suresh Marru <sm...@apache.org> on 2016/06/25 14:33:03 UTC

[GSoC] Midterm Evaluations

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>



Re: [GSoC] Midterm Evaluations

Posted by Suresh Marru <sm...@apache.org>.
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 <Je...@nd.edu> 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 <smarru@apache.org <ma...@apache.org>> 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>
> 
> 
> 


Re: [GSoC] Midterm Evaluations

Posted by Jeffery Kinnison <Je...@nd.edu>.
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

On Sat, Jun 25, 2016 at 10:33 AM, Suresh Marru <sm...@apache.org> 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
>
>
>

Re: [GSoC] Midterm Evaluations

Posted by Bikramjeet Singh <si...@gmail.com>.
Hi,
Here is the Google docs link for the updates required for mid-term
evaluation -

https://docs.google.com/document/d/1J43l01svL00PJ_podd7Y5K1EzRHTmBDEsvrjZNBIhpY/edit?usp=sharing

kindly inform if anything is required to be added or edited.

Thanks



On Sun, Jun 26, 2016 at 7:44 PM, Pierce, Marlon <ma...@iu.edu> wrote:

> Google doc is ok for now if you don’t have access to the wiki.  Don’t let
> this be a blocker. We can migrate.
>
>
>
> *From: *Bikramjeet Singh <si...@gmail.com>
> *Reply-To: *"dev@airavata.apache.org" <de...@airavata.apache.org>
> *Date: *Sunday, June 26, 2016 at 1:10 AM
> *To: *Airavata Dev <de...@airavata.apache.org>
> *Subject: *Re: [GSoC] Midterm Evaluations
>
>
>
> Hi,
>
> Do we need to make it on cwiki only? As, I am not getting any option to
> create any page there.
>
>
>
> Thanks
>
>
>
> On Sat, Jun 25, 2016 at 8:03 PM, Suresh Marru <sm...@apache.org> 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
>
>
>
>
>
>
>

Re: [GSoC] Midterm Evaluations

Posted by Chathuri Wimalasena <ka...@gmail.com>.
Hi Bikramjeet,

While you are writing the documents, you can send the links to your source
code.

Thanks,
Chathuri.
On Jun 26, 2016 11:51 AM, "Bikramjeet Singh" <si...@gmail.com>
wrote:

> Oh alright. My username at cwiki is linfestus, in case you can grant
> access before deadline.
>
> Thanks
>
> On Sunday 26 June 2016, Pierce, Marlon <ma...@iu.edu> wrote:
>
>> Google doc is ok for now if you don’t have access to the wiki.  Don’t let
>> this be a blocker. We can migrate.
>>
>>
>>
>> *From: *Bikramjeet Singh <si...@gmail.com>
>> *Reply-To: *"dev@airavata.apache.org" <de...@airavata.apache.org>
>> *Date: *Sunday, June 26, 2016 at 1:10 AM
>> *To: *Airavata Dev <de...@airavata.apache.org>
>> *Subject: *Re: [GSoC] Midterm Evaluations
>>
>>
>>
>> Hi,
>>
>> Do we need to make it on cwiki only? As, I am not getting any option to
>> create any page there.
>>
>>
>>
>> Thanks
>>
>>
>>
>> On Sat, Jun 25, 2016 at 8:03 PM, Suresh Marru <sm...@apache.org> 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
>>
>>
>>
>>
>>
>>
>>
>

Re: [GSoC] Midterm Evaluations

Posted by Bikramjeet Singh <si...@gmail.com>.
Oh alright. My username at cwiki is linfestus, in case you can grant access
before deadline.

Thanks

On Sunday 26 June 2016, Pierce, Marlon <ma...@iu.edu> wrote:

> Google doc is ok for now if you don’t have access to the wiki.  Don’t let
> this be a blocker. We can migrate.
>
>
>
> *From: *Bikramjeet Singh <singh.bikramjeet3@gmail.com
> <javascript:_e(%7B%7D,'cvml','singh.bikramjeet3@gmail.com');>>
> *Reply-To: *"dev@airavata.apache.org
> <javascript:_e(%7B%7D,'cvml','dev@airavata.apache.org');>" <
> dev@airavata.apache.org
> <javascript:_e(%7B%7D,'cvml','dev@airavata.apache.org');>>
> *Date: *Sunday, June 26, 2016 at 1:10 AM
> *To: *Airavata Dev <dev@airavata.apache.org
> <javascript:_e(%7B%7D,'cvml','dev@airavata.apache.org');>>
> *Subject: *Re: [GSoC] Midterm Evaluations
>
>
>
> Hi,
>
> Do we need to make it on cwiki only? As, I am not getting any option to
> create any page there.
>
>
>
> Thanks
>
>
>
> On Sat, Jun 25, 2016 at 8:03 PM, Suresh Marru <smarru@apache.org
> <javascript:_e(%7B%7D,'cvml','smarru@apache.org');>> 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
>
>
>
>
>
>
>

Re: [GSoC] Midterm Evaluations

Posted by "Pierce, Marlon" <ma...@iu.edu>.
Google doc is ok for now if you don’t have access to the wiki.  Don’t let this be a blocker. We can migrate.

From: Bikramjeet Singh <si...@gmail.com>
Reply-To: "dev@airavata.apache.org" <de...@airavata.apache.org>
Date: Sunday, June 26, 2016 at 1:10 AM
To: Airavata Dev <de...@airavata.apache.org>
Subject: Re: [GSoC] Midterm Evaluations

Hi,
Do we need to make it on cwiki only? As, I am not getting any option to create any page there.

Thanks

On Sat, Jun 25, 2016 at 8:03 PM, Suresh Marru <sm...@apache.org>> 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




Re: [GSoC] Midterm Evaluations

Posted by Bikramjeet Singh <si...@gmail.com>.
Hi,
Do we need to make it on cwiki only? As, I am not getting any option to
create any page there.

Thanks

On Sat, Jun 25, 2016 at 8:03 PM, Suresh Marru <sm...@apache.org> 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
>
>
>