From: "Shawn O. Pearce" <spearce@spearce.org>
To: sverre@rabbelier.nl
Cc: Joshua Roys <roysjosh@gmail.com>,
Lea Wiemann <LeWiemann@gmail.com>,
Marek Zawirski <Marek.Zawirski@gmail.com>,
Miklos Vajna <vmiklos@frugalware.org>,
Stephan Beyer <s-beyer@gmx.net>,
git@vger.kernel.org, Sam Vilain <sam.vilain@catalyst.net.nz>,
David Symonds <dsymonds@gmail.com>,
"J.H." <warthog19@eaglescrag.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Christian Couder <chriscool@tuxfamily.org>,
Daniel Barkalow <barkalow@iabervon.org>
Subject: Re: Welcome to Git's GSoC 2008!
Date: Tue, 22 Apr 2008 02:03:13 -0400 [thread overview]
Message-ID: <20080422060313.GD29771@spearce.org> (raw)
In-Reply-To: <bd6139dc0804212235p250b7335ide5359b43937869b@mail.gmail.com>
Sverre Rabbelier <alturin@gmail.com> wrote:
> I'm wondering if you other students and mentors are interested in
> setting up something like a mailing list/forum/IM/whatever to keep
> each other posted of progress during the summer without spamming the
> other resources too much. Maybe we can all help each other out with
> any problems we encounter and just keep in touch in general?
I have been considering it. But haven't proposed the idea myself
quite yet.
We are all working on very different projects. But I see roughly
three classes of discussions that are likely to occur:
* seemingly stupid questions (aka read the manual or faq)
There's no such thing as a stupid question, only stupid answers.
But one reason we have these wonderful mentors is they can be a
safe place for you to bounce ideas off without inciting a flame
war on the mailing list.
* fine grained project specific details
These are maybe too specific to your project to really spam close
to 900 people on the main git mailing list, but are still worth
discussion. Often these sorts of discussions happen off-list
among a few interested contributors anyway, even in non-GSoC git
related projects.
These probably should happen between you, your mentor(s) and a
handful of others who your mentor has introduced you to as being
interested in your work, and as a resource for you to go to for
assistance (see the first class of discussion).
* more project wide discussions
These really should happen on the git mailing list. You really
want feedback from potential users, and you really want to get a
wider audience for your work. As your project evolves and takes
shape your mentor should be encouring you to start posting bits
of it for more general discussion.
That said, if the students want to set up a mailing list to help
each other out, go ahead. And feel free to invite your mentors,
or not. ;-)
For the record, the best way to reach me is this email address, or
as "spearce" on irc.freenode.net in #git and/or #gsoc. I'm never
on an IM network, and I really don't like to visit web forums.
If it doesn't email to this address where I can read and reply,
its not something I am interested in.
--
Shawn.
next prev parent reply other threads:[~2008-04-22 6:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 1:32 Welcome to Git's GSoC 2008! Shawn O. Pearce
2008-04-22 1:59 ` GSoC 2008 application summary Shawn O. Pearce
2008-04-23 4:21 ` Shawn O. Pearce
[not found] ` <bd6139dc0804212235p250b7335ide5359b43937869b@mail.gmail.com>
2008-04-22 6:03 ` Shawn O. Pearce [this message]
2008-04-25 16:46 ` Welcome to Git's GSoC 2008! Jakub Narebski
2008-04-26 17:29 ` Shawn O. Pearce
2008-04-26 18:28 ` Jakub Narebski
2008-04-26 18:59 ` Shawn O. Pearce
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=20080422060313.GD29771@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=LeWiemann@gmail.com \
--cc=Marek.Zawirski@gmail.com \
--cc=barkalow@iabervon.org \
--cc=chriscool@tuxfamily.org \
--cc=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=roysjosh@gmail.com \
--cc=s-beyer@gmx.net \
--cc=sam.vilain@catalyst.net.nz \
--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).