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 1NsL6g-0003w6-2u for garchives@archives.gentoo.org; Thu, 18 Mar 2010 19:10:11 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A6F4FE0B21; Thu, 18 Mar 2010 19:10:04 +0000 (UTC) Received: from tommyserver.de (unknown [85.14.198.50]) by pigeon.gentoo.org (Postfix) with ESMTP id D5523E0B06 for ; Thu, 18 Mar 2010 19:09:49 +0000 (UTC) Received: from [192.168.178.22] (p4FDF25A2.dip0.t-ipconnect.de [79.223.37.162]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tommyserver.de (Postfix) with ESMTPSA id 24EC798CF79 for ; Thu, 18 Mar 2010 20:09:49 +0100 (CET) Message-ID: <4BA27A77.2050803@gentoo.org> Date: Thu, 18 Mar 2010 20:09:43 +0100 From: Thomas Sachau 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]: Proxy-maintainer project References: <201003181830.01103.hwoarang@gentoo.org> In-Reply-To: <201003181830.01103.hwoarang@gentoo.org> X-Enigmail-Version: 1.0.1 OpenPGP: id=211CA2D4 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig9AAAB23BBAF28DF4B09D2503" X-Archives-Salt: 8b1845b1-8704-4331-8ee0-4205d83f2492 X-Archives-Hash: f8a22f0c77cb820218de94e35c3ffae7 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig9AAAB23BBAF28DF4B09D2503 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 03/18/2010 05:29 PM, Markos Chandras wrote: > Dear fellow developers, >=20 > A new project is about to start so I am requesting your feedback >=20 > The primary goal of the Proxy Maintainers[1] project is to create and m= aintain=20 > relationships between developers and users in order to ensure packages = in the=20 > Gentoo tree stay up to date. This involves a few main tasks: Also it is a nice idea, i dont think, it will help Gentoo in the longer t= erm. As i can see with the Sunrise project, most users only want to get their ebuild initially into = portage/sunrise. They also listen to suggestions, improve their code and read a document to get acce= ss. But in most cases, they only do the initial commit or initial commit+some version bumps before th= ey leave again and the ebuild is unmaintained. I dont think, we want to proxy for those users, since this would result i= n either the proxy maintaining the ebuilds or many more maintainer-needed ebuild in main tre= e. The next group of users are those, who actively maintain their ebuild, al= so help other users and do this for a longer time. Usually those users get a mentor offer sooner or = later and then become a Gentoo Developer. So for those users, who are willing to help and can do = this for longer time (requirements for Gentoo devs), sunrise is already a good starting point = and base to get in. The only case, where there might be a (minimal) profit are those rare use= rs, who initially commit their ebuild and maintain exactly and only this ebuild for a longer time.= There might be 2 or 3 users doing it this way, so creating just another project for this idea i= s imho a bit too much work for minimal profit. I think, it might be better to send the interested users so Sunrise, wher= e they can learn the basics and afterwards you could still offer them to proxy the ebuild (sunrise ha= s an extra branch for proxy maintainers). A much better idea is imho to make the idea and way of Sunrise more publi= c and easier to see without searching (Homepage, FAQ, Forums), so interested users can find it easier= =2E In addition, every dev, who is interested in proxy maintaining something can do this via Sunrise.= --=20 Thomas Sachau Gentoo Linux Developer --------------enig9AAAB23BBAF28DF4B09D2503 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iJwEAQEKAAYFAkuienwACgkQG7kqcTWJkGcoygP+Iwwwa4eSMu54LBcNqPRGoEqg F5CdyWI0CFBhnztIF9MNbYukgsngmJgondRCbY0EOlHd4LRo5VhWI8079SpNAxJg pIKOwYjmnqM8iGydMF60J0M4+HOAQnfgyIaX1zabFjXfmA5I4pSWmPmbTAzX7jRU 6MyXhBkXQOFDH2iKzhs= =xOe6 -----END PGP SIGNATURE----- --------------enig9AAAB23BBAF28DF4B09D2503--