After designing the tool, you should spend some time and reconsider what
you have written in the timeline, which currently says absolutely nothing
about the actual implementation, as you use generic sentences about writing
"the code" and compiling "the code".
Please, take a look at former years student proposals to get a hint of how
to structure a meaningful proposal, how to design your project and how to
split up the project in milestones for your timeline.

Thanks and regards,

On Sat, 10 Mar 2018 at 09:21, Margherita Di Leo <direg...@gmail.com> wrote:

> Hi,
>
> I see that you have indicated in the first week: to design the tool,
> actually you should be doing this now, as well as compiling the source
> code, which you put in the bonding period. Rationale: how do you/we know
> that you will be able to develop such tool if you haven't neither designed
> it, nor compiled the source code and studied basic documentation.
>
> Thanks
>
> On Sat, 10 Mar 2018 at 07:10, sharry gill <sharrygill5...@gmail.com>
> wrote:
>
>> Hi,
>>
>> Here is the draft proposal, I fixed it: Link To Proposal
>> <https://docs.google.com/document/d/1G3cAkTXh_DAGyG26Mi1Sw3Ot2IL1msReG-_KFTSp2Nc/edit?usp=sharing>
>>
>> If any improvements are required, please let me know.
>>
>> Thank You
>> Supreet Singh
>> https://singhsupreet.github.io/
>>
>> On Wed, Mar 7, 2018 at 9:49 PM, Luca Delucchi <lucadel...@gmail.com>
>> wrote:
>>
>>> On 7 March 2018 at 09:08, sharry gill <sharrygill5...@gmail.com> wrote:
>>> >
>>> > Hello,
>>>
>>> hi,
>>>
>>> >
>>> > May be this is poasible that, if we allow user only to select modules,
>>> and
>>> > flags will be automatic.
>>>
>>> yes, so please improve your proposal..
>>>
>>> --
>>> ciao
>>> Luca
>>>
>>> www.lucadelu.org
>>>
>>
>> _______________________________________________
>> grass-dev mailing list
>> grass-dev@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
>
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to