First, I'd like to thank Jeff King for creating and hosting GSoC wiki pages for Git. Without his initiative, and even more his volunteering to be GSoC Git organizator we (as the Git Development Community) wouldn't be in Google Summer of Code 2012. 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. * "SoC 2012 Ideas", to gather ideas for GSoC project from Git developers and others, as _example_ ideas for students applications. We really should have more ideas, as it looks like students would be battling for a few projects (I think there are two would-be students for any proposed project). Well, too late now. I'd really like to see blue-sky proposals not mentioned on ideas list, or at least greatly expanded on proposed ideas. When students proposals would get accepted at April 23, there would be created "SoC 2012 Projects", listing accepted projects and hopefully tracking their status. I guess we would try to list git-related GSoC projects from other organizations, like in previous years. 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. One can find some information buried in GSoC FAQ: http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2012/faqs It would be nice however to have it extracted and make easier to find. This page could also serve to gather organization-specific requirements, for example: * That the discussion of GSoC project application ideas with mentoring organization (i.e. with us) should take place in the open, here on git mailing list, git@xxxxxxxxxxxxxxx. * That each student should examine relevant parts of existing git code, read SubmittingPatches and Coding Guidelines, and at least lurk (read) on git mailing list during the Community Bonding Period (e.g. via GMane; I don't think we should require subscribing to git mailing list). * That for each project there should be created a public git repository on one of git hosting sites like repo.or.cz, Gitorious or GitHub. * How often students (and/or mentors) should send updates about status of a project (once per week perhaps?), and what should those announcements include. 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. [I was neither GSoC student, or GSoC mentor.] -- Jakub Narebski Poland -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html