From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Shawn O. Pearce" Subject: Increased maintainer work during Summer of Code Date: Tue, 15 Jul 2008 06:04:27 +0000 Message-ID: <20080715060427.GB3337@spearce.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: Christian Couder , Daniel Barkalow , Johannes Schindelin , "J.H." , Sam Vilain , git@vger.kernel.org To: Junio C Hamano X-From: git-owner@vger.kernel.org Tue Jul 15 08:05:55 2008 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 1KIdfd-0002lh-Jf for gcvg-git-2@gmane.org; Tue, 15 Jul 2008 08:05:54 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757494AbYGOGE3 (ORCPT ); Tue, 15 Jul 2008 02:04:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757132AbYGOGE3 (ORCPT ); Tue, 15 Jul 2008 02:04:29 -0400 Received: from george.spearce.org ([209.20.77.23]:52783 "EHLO george.spearce.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755725AbYGOGE2 (ORCPT ); Tue, 15 Jul 2008 02:04:28 -0400 Received: by george.spearce.org (Postfix, from userid 1001) id EC58D3836B; Tue, 15 Jul 2008 06:04:27 +0000 (UTC) Content-Disposition: inline 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: In reading through the submitted mid-term surveys from students I found this excellent answer from Stephan Beyer: Q: What advice would you give to future would-be Summer of Code mentoring organizations? > I am wondering about one thing in git which is perhaps true for > a lot of other mentoring organizations: There is one person, the > maintainer, that is the final authority of deciding what patches > go into the repositories and what not. (This is ok and good and if > somebody disagrees a lot with such decisions he or she can make up > a fork repo without problems.) But the point is that the maintainer > has to review and add a lot of patches each day and _during GSoC > this is even a lot more_. I sometimes wonder how the maintainer is > able to handle that much work ;-) So my "advice" could be to think > about the "problem" of more contributions during GSoC, and if it > is useful to have co-maintainers or something. :) Junio, I know you have been working extra hard lately with the merge of builtin merge, and now gitweb and the sequencer are also being looked at in much greater detail. What can we do to smooth out this workload better? Its awesome that we were so fortunate to get these great students this year, and have so much contributed in so little time, but we also do not want to see maintainer burn-out. We also want to avoid a huge backlog of patches. I don't think we really ever talked about how to help Junio work through these large contributions that are coming his way. -- Shawn.