From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Shawn O. Pearce" Subject: Re: Google Summer of Code 2009 Date: Mon, 12 Jan 2009 07:37:35 -0800 Message-ID: <20090112153735.GC10179@spearce.org> References: <20090107183033.GB10790@spearce.org> <496B2690.2010902@op5.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: git@vger.kernel.org To: Andreas Ericsson X-From: git-owner@vger.kernel.org Mon Jan 12 16:39:15 2009 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1LMOsW-00089T-Rv for gcvg-git-2@gmane.org; Mon, 12 Jan 2009 16:39:01 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752506AbZALPhi (ORCPT ); Mon, 12 Jan 2009 10:37:38 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752295AbZALPhh (ORCPT ); Mon, 12 Jan 2009 10:37:37 -0500 Received: from george.spearce.org ([209.20.77.23]:52547 "EHLO george.spearce.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752179AbZALPhh (ORCPT ); Mon, 12 Jan 2009 10:37:37 -0500 Received: by george.spearce.org (Postfix, from userid 1001) id AD1F438210; Mon, 12 Jan 2009 15:37:35 +0000 (UTC) Content-Disposition: inline In-Reply-To: <496B2690.2010902@op5.se> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Andreas Ericsson 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.