Gsoc

[Umesh Singla]

Hi Abhishek

On Mon, Mar 26, 2018, 01:52 Abhishek Kashyap <abhishek.kasyap09 at gmail.com>
wrote:

> I think it is not mandatory to submit a patch.First priority is Best
> proposals.
> A/c to your template there is no need to mention vision and Gsoc period is
> from
> Comunity bonding period to final submission.It is irrelevant to mention
> the goals after GSOC because its only about GSOC.
> As we can contribute anytime.
> Thank You
>

I do not agree. First it depends on the organization how and when they want
to evaluate the students. Some even go to the extent of video interviewing
the candidates. If you follow blogs about GSoC on internet, it's encouraged
(or recommended) to make contact with the organization as early as possible
and "prove" your ability.

"There is no need to mention vision." Really?

It's not about just GSoC at all. Google wouldn't name a period "community
bonding" unless it means it. It's supposed to introduce school (GCI) and
college students to the world of open source and be a part of larger
community rather than just being a worker in some company. Most of the
members of MacPorts came through GSoC only and stuck to it, whom you now
interact as mentors and admins.

If you don't even agree to maintain your code before even submitting the
application, I don't know how you expect us to help you through the summer.

Regards,
Umesh Singla.


> On 26 March 2018 at 01:11, Mojca Miklavec <mojca at macports.org> wrote:
>
>> On 25 March 2018 at 18:49, Abhishek Kashyap wrote:
>> > Till now i have niether get any feedback nor any sugestion,
>>
>> Organisations were announced on the 12th of February. I believe it is
>> somewhat unrealistic to expect from volunteer mentors from different
>> time zones to study your proposal and write substantial feedback in
>> less that two hours on a day that most would spend away from
>> computers.
>>
>> > What can i do?
>> > Any tips
>>
>> I haven't seen you submit any patches or trying to contribute some
>> code or trying to prove us your competence/ability to finish the
>> project. If you have free time waiting for feedback, it would probably
>> be useful to spend it working on that.
>>
>> Sadly we lack some "good first issue" tag and I'm not sure what would
>> be a suitable easy task that doesn't require a lot of preliminary
>> familiarisation with the base.
>> https://trac.macports.org/wiki/Meetings/MacPortsMeeting2018/Roadmap
>> A simple task where we need help in the ports would be for example this
>> one:
>>     https://trac.macports.org/ticket/54839
>>
>> I'm not too familiar with implementation details, but I have some
>> troubles with English in the proposal and there are no "stretch goals"
>> (for example how you could continue after the GSOC, what's the vision
>> for which there would be no time during the summer etc.).
>>
>> Mojca
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20180325/78e17ffa/attachment-0001.html>