From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JXAZt-0000VB-3l for garchives@archives.gentoo.org; Thu, 06 Mar 2008 07:31:45 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4573DE07AB; Thu, 6 Mar 2008 07:31:43 +0000 (UTC) Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.184]) by pigeon.gentoo.org (Postfix) with ESMTP id 017E0E07AB for ; Thu, 6 Mar 2008 07:31:42 +0000 (UTC) Received: by gv-out-0910.google.com with SMTP id n40so2126363gve.39 for ; Wed, 05 Mar 2008 23:31:42 -0800 (PST) Received: by 10.78.141.12 with SMTP id o12mr8877015hud.22.1204788701277; Wed, 05 Mar 2008 23:31:41 -0800 (PST) Received: by 10.78.25.3 with HTTP; Wed, 5 Mar 2008 23:31:41 -0800 (PST) Message-ID: Date: Wed, 5 Mar 2008 23:31:41 -0800 From: "Alec Warner" Sender: antarus@scriptkitty.com To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Monthly Gentoo Council Reminder for March In-Reply-To: <6862BE72-6BDF-44D7-BBA3-88CA85A3C93B@gentoo.org> 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 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20080301103002.A2AE266A22@smtp.gentoo.org> <200803051504.53703.gentoofan23@gmail.com> <47CEFBBB.3010402@gentoo.org> <200803051531.54153.gentoofan23@gmail.com> <47CF0B05.6040308@gentoo.org> <6862BE72-6BDF-44D7-BBA3-88CA85A3C93B@gentoo.org> X-Google-Sender-Auth: a7fe84ebb3b8b06a X-Archives-Salt: 06514bcc-8f26-4624-8ec1-da3662dc97b9 X-Archives-Hash: 826c5db68758d5b3b2457c8512670f3b On 3/5/08, Anant Narayanan wrote: > On 06-Mar-08, at 2:35 AM, Petteri R=E4ty wrote: > > Thomas Anderson kirjoitti: > >> Arch Testers don't have tree access. This proposal gives the > >> package maintainer the ability to commit their changes. > > > > How would you ensure ebuild quality for these package maintainers? > > > Maintainers will also go through a recruitment process, although a > much shorter one which focusses only on ebuild maintenance - > maintainers will not have the karma to introduce new ebuilds into the > tree. The idea is to make the recruitment process as easy and quick as > possible, while ensuring that the person involved has the requisite > skills. Maybe break this down for me again please: What are the technical differences between a 'Package Maintainer' and a 'Developer'? I guess technical is the wrong word. Lets back up. What problem are you trying to solve? In your original mail; you stated that: a) The requirements to become a package maintainer for Gentoo may be lesser than that of the full-fledged developer. This serves a couple of purposes: - Users might become more motivated to becoming a maintainer for Gentoo, since it would require less time and effort from their end - Might reduce the number of orphaned packages we have in the tree So your goals are: Have more maintained packages in the tree. Get more people (users) involved in making Gentoo better. And you want to accomplish this by: Creating a position that has less stringent requirements to encourage interested folks to contribute. Your point B) also mentions removing pressure from existing developers by having some move to this new position to be less 'reponsible'. Can you explain how this 'Package Maintainer' is 'less responsible' than a full fledged developer? Can you also explain in more detail how the position of 'Package Maintainer' is also easier to obtain than the position of 'Developer'? You also stated: "Meanwhile, developers can do innovative things that they really like without having to maintain packages just because of a formality." I'm a bit new here; but since when was it required for a developer to maintain any packages? I care a lot less about how to implement this idea technically (cvs acls or lack of Gentoo.org e-mail address) and more so on what this will actually gain us; and how we should go about designing this position to accomplish the goals I think you want it to accomplish. > > Also, packages may not be marked stable until a full-fledged-developer/ > QA-member has approved of it. Packages being broken in the testing > tree are not uncommon, and we are usually notified quickly enough to > fix it. > > -- > > Anant-- > > gentoo-dev@lists.gentoo.org mailing list > > -- gentoo-dev@lists.gentoo.org mailing list