From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1M4Q2x-0004Wb-Nf for garchives@archives.gentoo.org; Thu, 14 May 2009 01:47:43 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 01A46E06B3; Thu, 14 May 2009 01:47:42 +0000 (UTC) Received: from mta-a3.tc.umn.edu (mta-a3.tc.umn.edu [134.84.119.232]) by pigeon.gentoo.org (Postfix) with ESMTP id DF564E06B3 for ; Thu, 14 May 2009 01:47:41 +0000 (UTC) Received: from [192.168.1.110] (c-71-63-157-77.hsd1.mn.comcast.net [71.63.157.77]) by mta-a3.tc.umn.edu (UMN smtpd) with ESMTP for ; Wed, 13 May 2009 20:47:41 -0500 (CDT) X-Umn-Remote-Mta: [N] c-71-63-157-77.hsd1.mn.comcast.net [71.63.157.77] #+TS+AU+HN Message-ID: <4A0B783C.2000501@gentoo.org> Date: Wed, 13 May 2009 20:47:40 -0500 From: Jeremy Olexa User-Agent: Thunderbird 2.0.0.21 (X11/20090508) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] RFC: Project proposal -- maintainer-wanted References: <1242261133.23088.82.camel@localhost> In-Reply-To: <1242261133.23088.82.camel@localhost> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 2ffaae1e-d59d-4c3d-9999-8b75124bf3b5 X-Archives-Hash: 46f30a129d51ca30a4e6041ac370b443 Mart Raudsepp wrote: > Hello, > > I have had this project in my mind for a while, so it's about time to > get it out there, as to see if feedback finds it a good one - and if > that is so, if there are people who want to make it happen. Hmm, I wonder what the point is when there is 400 maintainer-needed bugs open.. I think a maintainer-wanted team won't accomplish much because it just uses more developer time from a pool of "not enough time" that exists already. If people are a) too lazy to contribute to sunrise, b) don't know about sunrise, or c) don't know enough about ebuilds to contribute to sunrise, then we need to fix[1] that. I don't see any reason to create a team that duplicates the sunrise work. Keep in mind, I am against pretty much any overlay, I think work should be kept in the main tree. But, for ebuild maintenance with limited developer time, sunrise just makes sense(tm). Some other possible directions include: 1) maintainer-needed team - Where a group maintains the set of 761 m-needed packages. 2) proxy maint project[2] - Where a group helps users commit to the main tree, very similar to the sunrise project. Very similar to this proposal but better conserves our developer time. -Jeremy [1]: http://dev.gentoo.org/~darkside/sunrise_proposal.txt http://dev.gentoo.org/~darkside/sunrise_status.txt [2]: http://dev.gentoo.org/~antarus/projects/proxy-maint/