git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [GSoC] Git projects for Google Summer of Code 2008 final evaluation

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Sep 15, 2008, 12:40 UTC
Message-ID
<alpine.DEB.1.00.0809151434280.13830@pacific.mpi-cbg.de.mpi-cbg.de>
In-Reply-To
<200809151413.37628.jnareb@gmail.com>
Hi,
On Mon, 15 Sep 2008, Jakub Narebski wrote:
Show 19 quoted lines
> 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

Previous: Jakub NarebskiNext: Shawn O. Pearce
Message 11 of 12 in “[GSoC] Git projects for Google Summer of Code 2008 final evaluation”
  1. Jakub NarebskiSep 4, 2008
  2. Daniel BarkalowSep 4, 2008
  3. Joshua RoysSep 4, 2008
  4. Stephan BeyerSep 4, 2008
  5. Sverre RabbelierSep 4, 2008
  6. Miklos VajnaSep 4, 2008
  7. Shawn O. PearceSep 4, 2008
  8. Marek ZawirskiSep 8, 2008
  9. Johannes SchindelinSep 9, 2008
  10. Jakub NarebskiSep 15, 2008
  11. Johannes SchindelinSep 15, 2008
  12. Shawn O. PearceSep 15, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.