From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2166 invoked from network); 6 Jan 2004 12:57:46 +0000 Received: from smtp.gentoo.org (128.193.0.39) by eagle.gentoo.oregonstate.edu with DES-CBC3-SHA encrypted SMTP; 6 Jan 2004 12:57:46 +0000 Received: from lists.gentoo.org ([128.193.0.34] helo=eagle.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.24) id 1AdqmI-0004WQ-7l for arch-gentoo-dev@lists.gentoo.org; Tue, 06 Jan 2004 12:57:46 +0000 Received: (qmail 13026 invoked by uid 50004); 6 Jan 2004 12:57:45 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 2375 invoked from network); 6 Jan 2004 12:57:45 +0000 From: Paul de Vrieze To: gentoo-dev@lists.gentoo.org Date: Tue, 6 Jan 2004 13:57:40 +0100 User-Agent: KMail/1.5.4 References: <200401060017.08387.robert.cole@support4linux.com> In-Reply-To: <200401060017.08387.robert.cole@support4linux.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: clearsigned data Content-Disposition: inline Message-Id: <200401061357.40450.pauldv@gentoo.org> Subject: Re: [gentoo-dev] creating ebuilds X-Archives-Salt: 3bb03cbe-e808-417a-a1d8-50939c8de1c6 X-Archives-Hash: 7393a6bb01e0520d45cf92a181599db0 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 06 January 2004 09:17, Robert Cole wrote: > But I want to know if the brick wall that others have hit is still > there or not. There's been a bit o conflict in teh past where gentoo > will call for maintainers for certain projects yet previously slapped > down up and coming devs that want to maintain a different project. Why > would they volunteer for the requested project after being hammered > previously even if they have the skill to do the requested one? Would > you? Who would? From my understanding the devs are overwhelmed right > now with maintaining the current tree and need more people to take on > maintaining packages. The egos need to go by by and just do a quick > check to see if the ebuild and the dev have followed policy and mark > the thing ~x86 or whatever arch it is and toss it out. If it floats > then great they've proven themselves. If it sinks then a bit more > education is in order, pull the package and politely ask the new dev > to find and fix the problem and describe clearly what the problem was > and what they did to fix it and if it apears they understand the > problem and had a good solution toss it back in the tree to go again. > It would likely float the second time. There is unfortunately a limit on the amount of devs that we can handle.=20 We are still busy putting more structure in the gentoo organization, but=20 we would certainly have a problem if the amount of developers increased=20 drastically. > I'm not suggesting giving someone new with no established background > any sort of access. What I'm suggesting is basically what Allen spoke > of in just encouraging more contributions but accepting ebuilds faster > and the person with the proper access toss it in the tree. Like said before, the issue is not the initial ebuild. It is the=20 maintenance, including fixing bug reports and new versions. At the=20 moment there are allready too many packages in the tree that are not=20 actually maintained. This is partly due to the fact that those packages=20 are not easy to identify, and partly because it are just low-profile=20 packages. But that does not mean that we want more of those packages.=20 However when an ebuild gets committed without someone maintaining it=20 that is exactly what happens. If there are too many of those orphan=20 ebuilds it will reflect on the distribution (most orphan ebuilds have=20 issues because of not being maintained) Paul =2D --=20 Paul de Vrieze Gentoo Developer Mail: pauldv@gentoo.org Homepage: http://www.devrieze.net =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQE/+rDEbKx5DBjWFdsRAoeNAJ4x9wMNJoi7CCMRqBCPJPrGOHrDUwCdGLGp oA6tDMX7fglK22bUZ2zsy54=3D =3DsYex =2D----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list