git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: GSoC project mentors
Date: Fri, 9 Mar 2007 10:58:22 -0500	[thread overview]
Message-ID: <20070309155822.GB1131@spearce.org> (raw)
In-Reply-To: <81b0412b0703090150r674e754bn921d86eb40563e2a@mail.gmail.com>

Alex Riesen <raa.lkml@gmail.com> wrote:
> On 3/9/07, Shawn O. Pearce <spearce@spearce.org> wrote:
> >Committing oneself to being on IRC is a time commitment, isn't it?
> >:-)
> 
> yes, but it is a smaller one. And the suggestion was to commit to specific
> date and time.
> 
> >IRC time is difficult for me; I do hang out there more often than
> >I used to now that the community is doing the same, but I spend
> >a good part of my week working from a network where IRC access
> >isn't allowed.
> 
> Me too. But I would gladly spent some time on IRC when I'm home,
> which usually is after 20:00 CET. Especially if I promised to.

Looking at the way other successful projects have worked with GSoC,
it seems to really pay to have a couple of mentors per student.
The students don't always reach out to the mailing list right away
when they don't understand something or are seeking feedback on
an approach, as they might be shy or might be afraid of getting
flamed by one of the "old hands".  This is where having accessible
mentors comes in nicely, as the mentor can help the student frame
their message and get it into the public forum.  Likewise having
more than one mentor gives the student somewhere to turn when one
of the mentors takes a week of vacation.

Most of our projects do have more than one mentor listed now (thanks
guys!).  As our group's coordinator I intend on trying to make sure
every project has at least two mentors assigned to it and actively
participating with the student.  But given the way our community
works, I fully expect the whole community to be involved as patches
are posted and discussed on the mailing list.  Students need to be
interacting with all of us on git@vger, not just their mentors.

Having a fairly consistent presence on IRC would also be good.
I'm not quite sure yet how I'm personally going to do that this
summer scheduling wise, but I think it would be good if we can
have a few individuals on #git on a regularly scheduled basis.
I'd love to see you there, along with some of our other regulars.

-- 
Shawn.

  reply	other threads:[~2007-03-09 15:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08 10:12 [PATCH] shortlog: prompt when reading from terminal by mistake Junio C Hamano
2007-03-08 13:04 ` Johannes Schindelin
2007-03-08 15:07 ` GSoC project mentors Shawn O. Pearce
2007-03-08 16:04   ` Alex Riesen
2007-03-09  0:59     ` Shawn O. Pearce
2007-03-09  9:50       ` Alex Riesen
2007-03-09 15:58         ` Shawn O. Pearce [this message]
2007-03-08 17:27   ` Johannes Schindelin
2007-03-09  2:26     ` Shawn O. Pearce
2007-03-08 16:37 ` [PATCH] shortlog: prompt when reading from terminal by mistake Linus Torvalds
2007-03-08 17:10   ` Johannes Schindelin
2007-03-08 17:19     ` Matthieu Moy
2007-03-08 17:28       ` Johannes Schindelin
2007-03-08 17:31     ` Linus Torvalds
2007-03-08 17:37       ` Johannes Schindelin
2007-03-09 14:41     ` Jakub Narebski
2007-03-10  0:39   ` Junio C Hamano

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=20070309155822.GB1131@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=raa.lkml@gmail.com \
    /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).