You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by Apoorv Palkar <ap...@aol.com> on 2017/03/29 21:23:48 UTC
[GSoC] Number of Deliverables
How many goals should we aim to put in our proposal? Is it better to put in small goals and over-deliver?
Thanks
Re: [GSoC] Number of Deliverables
Posted by "Pierce, Marlon" <ma...@iu.edu>.
Discussing those better ways on the dev list is also encouraged. No plans every stay the same. The value of plans is the process of planning, not the plan itself, as someone else has said.
Marlon
From: Supun Nakandala <su...@gmail.com>
Reply-To: "dev@airavata.apache.org" <de...@airavata.apache.org>
Date: Wednesday, March 29, 2017 at 6:12 PM
To: dev <de...@airavata.apache.org>
Subject: Re: [GSoC] Number of Deliverables
I think what is important here is what problem(s) you promise to solve.
In the proposal you will have to show some plan on how you intend to solve those problem(s) mainly to convince the mentors that you have an idea on what you are planning to do.
While executing the project, finding better ways to solve the initial problem(s) is always encouraged. :)
On Wed, Mar 29, 2017 at 6:05 PM, Apoorv Palkar <ap...@aol.com> wrote:
If you promise to do things a certain way, but you find a better solution when actually working the project, can you implement new ideas and scrap old ones?
-----Original Message-----
From: Supun Nakandala <su...@gmail.com>
To: dev <de...@airavata.apache.org>
Sent: Wed, Mar 29, 2017 4:43 pm
Subject: Re: [GSoC] Number of Deliverables
Hi Apoorv,
As a sample project proposal, I would recommend you to refer this.
From my experiences as a past GSoC student, I think having specific and challenging goals should make your proposal more attractive and increase the chances of getting accepted.
However trying to come up with a set of goals which you think is overly unrealistic will also hinder your success later because you will be judged based on what you promise(proposal). It is completely ok to not being able to achieve what you promise. But you will have to prove that you put significant effort in achieving your goals (which can get tricky).
-Supun
On Wed, Mar 29, 2017 at 5:23 PM, Apoorv Palkar <ap...@aol.com> wrote:
How many goals should we aim to put in our proposal? Is it better to put in small goals and over-deliver?
Thanks
--
Thank you
Supun Nakandala
Dept. Computer Science and Engineering
University of Moratuwa
--
Thank you
Supun Nakandala
Dept. Computer Science and Engineering
University of Moratuwa
Re: [GSoC] Number of Deliverables
Posted by Supun Nakandala <su...@gmail.com>.
I think what is important here is what problem(s) you promise to solve.
In the proposal you will have to show some plan on how you intend to solve
those problem(s) mainly to convince the mentors that you have an idea on
what you are planning to do.
While executing the project, finding better ways to solve the initial
problem(s) is always encouraged. :)
On Wed, Mar 29, 2017 at 6:05 PM, Apoorv Palkar <ap...@aol.com>
wrote:
> If you promise to do things a certain way, but you find a better solution
> when actually working the project, can you implement new ideas and scrap
> old ones?
>
>
>
> -----Original Message-----
> From: Supun Nakandala <su...@gmail.com>
> To: dev <de...@airavata.apache.org>
> Sent: Wed, Mar 29, 2017 4:43 pm
> Subject: Re: [GSoC] Number of Deliverables
>
> Hi Apoorv,
>
> As a sample project proposal, I would recommend you to refer this
> <https://cwiki.apache.org/confluence/display/AIRAVATA/%5BGSoC+Proposal%5D+Securing+Airavata+API>
> .
>
> From my experiences as a past GSoC student, I think having specific and
> challenging goals should make your proposal more attractive and increase
> the chances of getting accepted.
>
> However trying to come up with a set of goals which you think is overly
> unrealistic will also hinder your success later because you will be judged
> based on what you promise(proposal). It is completely ok to not being able
> to achieve what you promise. But you will have to prove that you put
> significant effort in achieving your goals (which can get tricky).
>
> -Supun
>
> On Wed, Mar 29, 2017 at 5:23 PM, Apoorv Palkar <ap...@aol.com>
> wrote:
>
> How many goals should we aim to put in our proposal? Is it better to put
> in small goals and over-deliver?
>
> Thanks
>
>
>
>
> --
> Thank you
> Supun Nakandala
> Dept. Computer Science and Engineering
> University of Moratuwa
>
--
Thank you
Supun Nakandala
Dept. Computer Science and Engineering
University of Moratuwa
Re: [GSoC] Number of Deliverables
Posted by Apoorv Palkar <ap...@aol.com>.
If you promise to do things a certain way, but you find a better solution when actually working the project, can you implement new ideas and scrap old ones?
-----Original Message-----
From: Supun Nakandala <su...@gmail.com>
To: dev <de...@airavata.apache.org>
Sent: Wed, Mar 29, 2017 4:43 pm
Subject: Re: [GSoC] Number of Deliverables
Hi Apoorv,
As a sample project proposal, I would recommend you to refer this.
From my experiences as a past GSoC student, I think having specific and challenging goals should make your proposal more attractive and increase the chances of getting accepted.
However trying to come up with a set of goals which you think is overly unrealistic will also hinder your success later because you will be judged based on what you promise(proposal). It is completely ok to not being able to achieve what you promise. But you will have to prove that you put significant effort in achieving your goals (which can get tricky).
-Supun
On Wed, Mar 29, 2017 at 5:23 PM, Apoorv Palkar <ap...@aol.com> wrote:
How many goals should we aim to put in our proposal? Is it better to put in small goals and over-deliver?
Thanks
--
Thank you
Supun Nakandala
Dept. Computer Science and Engineering
University of Moratuwa
Re: [GSoC] Number of Deliverables
Posted by Supun Nakandala <su...@gmail.com>.
Hi Apoorv,
As a sample project proposal, I would recommend you to refer this
<https://cwiki.apache.org/confluence/display/AIRAVATA/%5BGSoC+Proposal%5D+Securing+Airavata+API>
.
From my experiences as a past GSoC student, I think having specific and
challenging goals should make your proposal more attractive and increase
the chances of getting accepted.
However trying to come up with a set of goals which you think is overly
unrealistic will also hinder your success later because you will be judged
based on what you promise(proposal). It is completely ok to not being able
to achieve what you promise. But you will have to prove that you put
significant effort in achieving your goals (which can get tricky).
-Supun
On Wed, Mar 29, 2017 at 5:23 PM, Apoorv Palkar <ap...@aol.com>
wrote:
> How many goals should we aim to put in our proposal? Is it better to put
> in small goals and over-deliver?
>
> Thanks
>
--
Thank you
Supun Nakandala
Dept. Computer Science and Engineering
University of Moratuwa