Hi,
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
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
From: "Michael Haggerty" <redacted>
Cc: "Dmitry Dolzhenko" <redacted>; "Sun He"
[off-list ref]; "Brian Gesiak" [off-list ref]; "Tanay
Abhra" [off-list ref]; "Kyriakos Georgiou"
[off-list ref]; "Siddharth Goel"
[off-list ref]; "Guanglin Xu" [off-list ref];
"Karthik Nayak" [off-list ref]; "Alberto Corona"
[off-list ref]; "Jacopo Notarstefano"
[off-list ref]
Hi,
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
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
--
In particular I liked : " If the documentation is unclear, it is OK to
ask for a clarification, but then _fix the documentation_ so that your
mentor never has to answer the same question again."
So the rhetorical question(s) for students would be :-
- was the Git documentation useful - did you see the README?, did it
lead, easily, to the useful places [1]? How could the wording/layout be
improved for the first time reader?
- which points of clarification were most useful and are they in the
documentation? Where should they be included?
- which points needed repeating often, and why? Where was the
disconnect?
- what would a patch look like...
Philip Oakley
[1] README; INSTALL; Documentation/SubmittingPatches;
Documentation/CodingGuidelines;
On Mon, Mar 3, 2014 at 5:45 AM, Michael Haggerty [off-list ref] wrote:
My secret tip for GSoC success
http://softwareswirl.blogspot.com/2014/03/my-secret-tip-for-gsoc-success.html
I enjoyed reading that BLOG post. I daresay some of the points you
raise are pertinent for any new contributor to any open-source code
base.