From: "Shawn O. Pearce" <spearce@spearce.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org, Sam Vilain <sam@vilain.net>,
Joshua Roys <roysjosh@gmail.com>,
Sverre Rabbelier <alturin@gmail.com>,
Sverre Rabbelier <sverre@rabbelier.nl>,
David Symonds <dsymonds@gmail.com>,
Lea Wiemann <LeWiemann@gmail.com>,
John Hawley <warthog19@eaglescrag.net>,
Marek Zawirski <marek.zawirski@gmail.com>,
Miklos Vajna <vmiklos@frugalware.org>,
Stephan Beyer <s-beyer@gmx.net>,
Christian Couder <chriscool@tuxfamily.org>,
Daniel Barkalow <barkalow@iabervon.org>,
Junio Hamano <gitster@pobox.com>
Subject: Re: [GSoC] Git projects for Google Summer of Code 2008 final evaluation
Date: Mon, 15 Sep 2008 07:08:11 -0700 [thread overview]
Message-ID: <20080915140811.GA6320@spearce.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0809151434280.13830@pacific.mpi-cbg.de.mpi-cbg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> 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:
...
> > 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.
I agree with Dscho completely. We are an email based community.
Students should be involved by email, not by blogs. If we were
the Ruby community (which near as I can tell is blog based) then
blogging might make more sense. We're not. We're an offshoot of
the Linux community, which is very much email-centric.
> 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.
Exactly. Email also costs time, but typically we don't see
traffic on the list that is just broadcasting something pointless.
In general people only start a topic if there is going to be
worthwhile discussion attached to it, and often that results in a
useful patch being applied at some point in the future. IOW that
time for email is just necessary in the course of development,
so it isn't wasted.
If the community of semi-interested people really wants blogs to
read, RSS scrape a news feed like Gmane. Ohloh already has an
RSS feed defined around the emails sent to git ML with the subject
"[ANNOUNCE]".
I however prefer email, and dislike blogging, so I'll continue
to use the git ML in the future, and so will any student I mentor
in any potential future GSoC program. FWIW I blogged here at new
day-job on company internal blog for about a half day before I gave
up and said "damn, that really is stupid".
--
Shawn.
prev parent reply other threads:[~2008-09-15 14:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 21:15 [GSoC] Git projects for Google Summer of Code 2008 final evaluation Jakub Narebski
2008-09-04 22:10 ` Daniel Barkalow
2008-09-04 22:22 ` Joshua Roys
2008-09-04 22:36 ` Stephan Beyer
2008-09-04 22:44 ` Sverre Rabbelier
2008-09-04 22:55 ` Miklos Vajna
2008-09-04 23:04 ` Shawn O. Pearce
2008-09-08 17:46 ` Marek Zawirski
2008-09-09 14:52 ` Johannes Schindelin
2008-09-15 12:13 ` Jakub Narebski
2008-09-15 12:40 ` Johannes Schindelin
2008-09-15 14:08 ` Shawn O. Pearce [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080915140811.GA6320@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=LeWiemann@gmail.com \
--cc=alturin@gmail.com \
--cc=barkalow@iabervon.org \
--cc=chriscool@tuxfamily.org \
--cc=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=marek.zawirski@gmail.com \
--cc=roysjosh@gmail.com \
--cc=s-beyer@gmx.net \
--cc=sam@vilain.net \
--cc=sverre@rabbelier.nl \
--cc=vmiklos@frugalware.org \
--cc=warthog19@eaglescrag.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).