From: "Shawn O. Pearce" <spearce@spearce.org>
To: Andreas Ericsson <ae@op5.se>
Cc: git@vger.kernel.org
Subject: Re: Google Summer of Code 2009
Date: Mon, 12 Jan 2009 07:37:35 -0800 [thread overview]
Message-ID: <20090112153735.GC10179@spearce.org> (raw)
In-Reply-To: <496B2690.2010902@op5.se>
Andreas Ericsson <ae@op5.se> wrote:
> Just chiming in that I can probably help mentoring whoever goes
> with libgit2. I do not have enough spare time for me to promise
> that I can be there as much as I think is necessary and proper,
> but I'll gladly help out.
Thanks. I'd love to see a libgit2 project this summer.
If we do have such a thing, and if I'm still wearing the maintainer
hat for libgit2, I think it would be improper for me to be the mentor
for the student. Just as Junio abstains from mentoring any students
in GSoC, to prevent potential bias during patch review, I probably
should abstain in the case of libgit2. Or at least move the project
to a dual-maintainer approach like we use with JGit, so the other
maintainer is the one doing the actual review and patch acceptance.
--
Shawn.
prev parent reply other threads:[~2009-01-12 15:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 18:30 Google Summer of Code 2009 Shawn O. Pearce
2009-01-07 23:11 ` Miklos Vajna
2009-01-07 23:12 ` Alex Riesen
2009-01-07 23:14 ` Shawn O. Pearce
2009-01-07 23:30 ` Johannes Schindelin
2009-01-07 23:40 ` Alex Riesen
2009-01-08 7:55 ` Sam Vilain
2009-01-10 19:33 ` Jakub Narebski
2009-01-10 19:58 ` Johannes Schindelin
2009-01-12 13:01 ` Christian Couder
2009-01-14 22:01 ` Stephan Beyer
2009-01-12 11:16 ` Andreas Ericsson
2009-01-12 13:20 ` Christian Couder
2009-01-12 15:35 ` Shawn O. Pearce
2009-01-12 13:25 ` Johannes Schindelin
2009-01-12 15:33 ` Shawn O. Pearce
2009-01-12 17:23 ` Johannes Schindelin
2009-01-12 17:48 ` Shawn O. Pearce
2009-01-12 15:37 ` 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=20090112153735.GC10179@spearce.org \
--to=spearce@spearce.org \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
/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).