Re: [RFH] SoC 2012 Guidelines
- From
Jeff King <peff@peff.net>
- Date
- Mar 27, 2012, 05:57 UTC
- Message-ID
- <20120327055747.GB24170@sigill.intra.peff.net>
- In-Reply-To
- <201203241711.30270.jnareb@gmail.com>
On Sat, Mar 24, 2012 at 05:11:29PM +0100, Jakub Narebski wrote:
Show 9 quoted lines
> The https://github.com/peff/git/wiki/ includes the following pages: > > * "SoC 2012 Application", which should probably be renamed to > "SoC 2012 Organization Application"; it was here to help (crowd)craft > organization application. > > * "SoC 2012 Template", which perhaps should be better named > "SoC 2012 Student Application Template"; it is here for prospective > (would-be) student to help craft better project application.
Good renaming suggestions; I just pushed this.
The template page was not well-advertised, so I linked to it from the ideas page.
> What is lacking (for me) is something like "SoC 2012 Guidelines" wiki > page, which would gather guidelines and suggestions both for mentors > and for students.
Some of that (for the students) is at the ideas page, and on the application template page. To a large degree, the advice is: engage the community. Hopefully that results in interesting discussions and the students getting a sense of what is required for each project. But there is probably room to provide some more specific guidance.
For the mentor side, we have pretty much left the mentors alone to decide how to do their jobs, recognizing that every mentor and every student-mentor pair will be a little bit different.
> This page could also serve to gather organization-specific requirements, > for example: > [...]
All of what you said looks reasonable to me, and follows the practices we've had in years past. It's a wiki. Feel free to add a new page, or edit (or if you want to get feedback before changing the wiki, post patches).
Show 14 quoted lines
> And to gather help: > > * There should be some information about what parts of discussion and > work should take place in private communication between student and > mentor, and how much should it take place in public, on git mailing > list. > > * How can and how should mentors help students. > > * How to make use of comments on patches (or design ideas), while not > getting bogged down in "bikeshed"-ding :-) > > * Perhaps also some advice from successfull students to students, > and from mentors to mentors.
Some of these things are discussed in more general terms on the GSoC mentors list. We don't have particular policies in git, though in general I would encourage mentors to integrate the students into the usual list workflow. So lots of communication and status reports, and as much as possible in the open and on the list.
-Peff