From: Junio C Hamano <gitster@pobox.com>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: git discussion list <git@vger.kernel.org>,
Dmitry Dolzhenko <dmitrys.dolzhenko@yandex.ru>,
Sun He <sunheehnus@gmail.com>, Brian Gesiak <modocache@gmail.com>,
Tanay Abhra <tanayabh@gmail.com>,
Kyriakos Georgiou <kyriakos.a.georgiou@gmail.com>,
Siddharth Goel <siddharth98391@gmail.com>,
Guanglin Xu <mzguanglin@gmail.com>,
Karthik Nayak <karthik.188@gmail.com>,
Alberto Corona <albcoron@gmail.com>,
Jacopo Notarstefano <jacopo.notarstefano@gmail.com>
Subject: Re: My advice for GSoC applicants
Date: Mon, 03 Mar 2014 14:29:10 -0800 [thread overview]
Message-ID: <xmqqa9d6or0p.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <53145D48.3040603@alum.mit.edu> (Michael Haggerty's message of "Mon, 03 Mar 2014 11:45:28 +0100")
Michael Haggerty <mhagger@alum.mit.edu> writes:
> Based on my experience so far as a first-time Google Summer of Code
> mentor, I just wrote a blog article containing some hopefully useful
> advice for students applying to the program. Please note that this is
> my personal opinion only and doesn't necessarily reflect the views of
> the Git/libgit2 projects as a whole.
>
> My secret tip for GSoC success
>
> http://softwareswirl.blogspot.com/2014/03/my-secret-tip-for-gsoc-success.html
Thanks for writing this.
Also thanks for the MicroProject approach to introduce potential
students and the community.
Multiple students seem to be hitting the same microprojects (aka "we
are running out of micros"), which might be a bit unfortunate. I
think the original plan might have been that for a student candidate
to pass, his-or-her patch must hit my tree and queued somewhere, but
with these duplicates I do not think it is fair to disqualify those
who interacted with reviewers well but solved an already solved
micro.
Even with the duplicates I think we are learning how well each
student respond to reviews (better ones even seem to pick up lessons
from reviews on others' threads that tackle micros different from
their own) and what his-or-her general cognitive ability is.
next prev parent reply other threads:[~2014-03-03 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 10:45 My advice for GSoC applicants Michael Haggerty
2014-03-03 16:33 ` Philip Oakley
2014-03-03 17:12 ` Rick Umali
2014-03-03 22:29 ` Junio C Hamano [this message]
2014-03-04 7:58 ` Michael Haggerty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqa9d6or0p.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=albcoron@gmail.com \
--cc=dmitrys.dolzhenko@yandex.ru \
--cc=git@vger.kernel.org \
--cc=jacopo.notarstefano@gmail.com \
--cc=karthik.188@gmail.com \
--cc=kyriakos.a.georgiou@gmail.com \
--cc=mhagger@alum.mit.edu \
--cc=modocache@gmail.com \
--cc=mzguanglin@gmail.com \
--cc=siddharth98391@gmail.com \
--cc=sunheehnus@gmail.com \
--cc=tanayabh@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.