[gsoc 19]proposal to project 1 Boost.GIL - Boost - lists.preview.boost.org

newer
Regarding Boost.Astronomy GSoC19

[gsoc 19]proposal to project 1 Boost.GIL

older
variant - off topic

raghuchandra kanakamedala

4 Apr 2019 4 Apr '19

8:42 a.m.

Hi my proposal link: https://docs.google.com/document/d/1-BZO0VuIcebe1ZcdyxHGjOEkQL3eeaXwGtKCWyQQ... .Please suggest me any changes if required. Thanking you K RaghuChandra

Reply

Sign in to reply online Use email software

Show replies by date

Mateusz Loskot

4 Apr 4 Apr

9:59 a.m.

On Thu, 4 Apr 2019 at 10:44, raghuchandra kanakamedala wrote:

my proposal link: https://docs.google.com/document/d/1-BZO0VuIcebe1ZcdyxHGjOEkQL3eeaXwGtKCWyQQ... .Please suggest me any changes if required.

I would suggest to not to give any promises of *effective* effort for 8 hours per day for 6 days. GSoC does not ask you to be that specific. https://developers.google.com/open-source/gsoc/faq """ How much time does GSoC participation take? You are expected to spend around 30+ hours a week working on your project during the 3 month coding period. """ You write "Interest in Project" as what motivates you to participate in GIL, then you write "Extensions of this project beyond summer of code". In between, you actually should describe - what project you'd like to work on - what functionality you would like to add to GIL - name algorithms and techniques you would like to implement. The section later "Implementation Details of Project" feels too much, and unnecessary. It seem to mix API description with algorithms description and implementation details, with attempt to squeeze all those into tiny paragraph. Your proposal does not need all those details (for this stage of GSoC). What is more important, the section "Implementation Details of Project" lists a lot of algorithms and processing techniques. Are you planning to implement all of them during this GSoC? I'd suggest to make the proposal more focused, to make it clear what you want to work on, what is the project about. ...sometimes "less is more" Take my comments as friendly but subjective piece of advice, opinionated though, and not as any authoritative one. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

Reply

Sign in to reply online Use email software

raghuchandra kanakamedala

4:23 p.m.

Hi I have made changes accordingly.Please give me your advises for any further improvement. Thanking you K RaghuChandra On Thu, Apr 4, 2019 at 3:30 PM Mateusz Loskot via Boost < boost@lists.boost.org> wrote:

On Thu, 4 Apr 2019 at 10:44, raghuchandra kanakamedala wrote:

...
my proposal link:

https://docs.google.com/document/d/1-BZO0VuIcebe1ZcdyxHGjOEkQL3eeaXwGtKCWyQQ...

...
.Please suggest me any changes if required.

I would suggest to not to give any promises of *effective* effort for 8 hours per day for 6 days. GSoC does not ask you to be that specific.

https://developers.google.com/open-source/gsoc/faq """ How much time does GSoC participation take? You are expected to spend around 30+ hours a week working on your project during the 3 month coding period. """

You write "Interest in Project" as what motivates you to participate in GIL, then you write "Extensions of this project beyond summer of code".

In between, you actually should describe - what project you'd like to work on - what functionality you would like to add to GIL - name algorithms and techniques you would like to implement.

The section later "Implementation Details of Project" feels too much, and unnecessary. It seem to mix API description with algorithms description and implementation details, with attempt to squeeze all those into tiny paragraph. Your proposal does not need all those details (for this stage of GSoC).

What is more important, the section "Implementation Details of Project" lists a lot of algorithms and processing techniques. Are you planning to implement all of them during this GSoC?

I'd suggest to make the proposal more focused, to make it clear what you want to work on, what is the project about. ...sometimes "less is more"

Take my comments as friendly but subjective piece of advice, opinionated though, and not as any authoritative one.

Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Reply

Sign in to reply online Use email software

2047

Age (days ago)

2047

Last active (days ago)

Download

2 comments

2 participants

tags

participants (2)

Mateusz Loskot
raghuchandra kanakamedala