Hi, On Mon, 15 Sep 2008, Jakub Narebski wrote: > On Thu, 4 Sep 2008, Jakub Narebski wrote: > > > Mentors, could you tell us your side about how it was working as a > > mentor for Google Summer of Code? Perhaps some tricks of trade? > > By the way, I have found via LWN that Perl has written nice summary of > theirs Google Summer of Code projects[1]. Among other they very much > praise that students did blogging about their progress: > > "use Perl | Summer of Code recap" > http://use.perl.org/articles/08/08/29/1224242.shtml > > Most of the students did a great job of blogging their progress, which > I think is an important part of Summer of Code for the rest of the > community. > > What do you think about it (for example about doing it in a future > if our informal Git Development Community would participate in next > Google Summer of Code programs)? I think that it is better to require frequent interaction on the mailing list, or at least on IRC. Blogging is nice for those who want to follow the progress of a project, but do not want to get involved. In this case, it is even better than having the people discuss the issues of the project openly, as reading a blog does not require constant monitoring like the list does. However, blogging costs time. I think that in the case of Git, those who are interested are those that will work on (as opposed to "with") those projects, too. So I think the time is better spent on the mailing list. Especially given the fact that the interested parties can guide the course of the project early, i.e. before a blog entry would be written (just think about the Git.pm thing; both Lea's and Joshua's project could have benefitted from enhancing the existing Git.pm according to their needs). My cent, Dscho -- 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
