From: "Michael Haggerty" <mhag...@alum.mit.edu>
Cc: "Dmitry Dolzhenko" <dmitrys.dolzhe...@yandex.ru>; "Sun He"
<sunheeh...@gmail.com>; "Brian Gesiak" <modoca...@gmail.com>; "Tanay
Abhra" <tanay...@gmail.com>; "Kyriakos Georgiou"
<kyriakos.a.georg...@gmail.com>; "Siddharth Goel"
<siddharth98...@gmail.com>; "Guanglin Xu" <mzguang...@gmail.com>;
"Karthik Nayak" <karthik....@gmail.com>; "Alberto Corona"
<albco...@gmail.com>; "Jacopo Notarstefano"
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
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 ? 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
- what would a patch look like...
 README; INSTALL; Documentation/SubmittingPatches;
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html