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 1Nsckl-0001Xs-6e for garchives@archives.gentoo.org; Fri, 19 Mar 2010 14:00:43 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 65DFBE0CE5; Fri, 19 Mar 2010 14:00:40 +0000 (UTC) Received: from vms173001pub.verizon.net (vms173001pub.verizon.net [206.46.173.1]) by pigeon.gentoo.org (Postfix) with ESMTP id 03759E0CD4 for ; Fri, 19 Mar 2010 14:00:38 +0000 (UTC) Received: from gw.thefreemanclan.net ([unknown] [96.245.231.248]) by vms173001.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0KZJ00BVG88P8581@vms173001.mailsrvcs.net> for gentoo-dev@lists.gentoo.org; Fri, 19 Mar 2010 09:00:37 -0500 (CDT) Received: from [192.168.0.5] (rich.homedns.org [192.168.0.5]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by gw.thefreemanclan.net (Postfix) with ESMTPS id DC8641759F48 for ; Fri, 19 Mar 2010 10:00:24 -0400 (EDT) Message-id: <4BA38378.9080303@gentoo.org> Date: Fri, 19 Mar 2010 10:00:24 -0400 From: Richard Freeman User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100306 Thunderbird/3.0.3 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> <4BA27A77.2050803@gentoo.org> In-reply-to: Content-type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Archives-Salt: b15d2ee0-9b21-42ad-81d2-b060211ba32c X-Archives-Hash: bd0bc15353dd4be4802ccea71cbf2776 On 03/18/2010 04:34 PM, Ben de Groot wrote: > Recruitment being the bottleneck that it is (with candidates > waiting many months), it is good to have another option > for people who want to contribute. If we do have a list of people waiting to get in, could we maybe publish=20 this list somewhere, or instruct these people to look for=20 maintainer-wanted bugs and offer their services as proxy-maintainers?=20 Can we have some way of communicating that one of these almost-devs has=20 written some ebuilds so that devs can work with them to get them committe= d? This would get them a head-start and will give them VERY practical=20 instruction. For the devs that work with them they'll know that they're=20 working with somebody with a long-term interest. I'm not sure that we=20 want a policy that states that when the recruits become devs that they=20 will maintain these packages long-term, but it would be nice if they did = so. Perhaps the devs could also provide feedback to the recruiters on the=20 recruit's strong/weak points so that they could work on these. (NOTE -=20 I'm not suggesting marking people for exclusion here - if somebody is=20 fairly raw we want to work with them, but it doesn't hurt for the=20 recruiters to know about that up-front.) I realized that some of these ideas are still half-baked, but I'm=20 wondering if there isn't an opportunity here. Rich