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 <gentoo-dev+bounces-29739-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1JXGmH-0005CN-Ow
	for garchives@archives.gentoo.org; Thu, 06 Mar 2008 14:08:57 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 89FDCE06AC;
	Thu,  6 Mar 2008 14:08:49 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
	by pigeon.gentoo.org (Postfix) with ESMTP id 3C8AEE06AC
	for <gentoo-dev@lists.gentoo.org>; Thu,  6 Mar 2008 14:08:49 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
	by smtp.gentoo.org (Postfix) with ESMTP id 5F6A966998
	for <gentoo-dev@lists.gentoo.org>; Thu,  6 Mar 2008 14:08:48 +0000 (UTC)
X-Virus-Scanned: amavisd-new at gentoo.org
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 required=5.5 tests=[AWL=1.300,
	BAYES_00=-2.599]
Received: from smtp.gentoo.org ([127.0.0.1])
	by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VCnpBqdR4g-z for <gentoo-dev@lists.gentoo.org>;
	Thu,  6 Mar 2008 14:08:39 +0000 (UTC)
Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.189])
	by smtp.gentoo.org (Postfix) with ESMTP id D2D4664A48
	for <gentoo-dev@gentoo.org>; Thu,  6 Mar 2008 14:08:38 +0000 (UTC)
Received: by gv-out-0910.google.com with SMTP id s4so2248985gve.21
        for <gentoo-dev@gentoo.org>; Thu, 06 Mar 2008 06:08:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        bh=GUL5zD1hAe17yTSfjfLswLreuRnYsgQ/NTNXnjYG7fg=;
        b=hBY+Z7VFcvdXb7wsKLjBFIK69vCp/Q7tGrOUaRX8CQnJgX6qWq13azSUrkee3+qEKcLBMG//hlZxW2fZKaZYOuwlwcAsKdjbgxoVUUKzpwDRBB6Bf3N5S+qw6nz37ZtB3+oel+P/quAkzF9RQIUBndQNz7BCm5rFlw+3YKUJ4R8=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=xllK7GN5XgHxKZmcbVtgAV20VfZkHvDAc871doMIYdQBsgFLjoKRNEwf/ozZhMQXCnpr5s/dk/xoWXGlj4ad326xGgHlzIUOCgu+30li1VUGa3nRb86hpypFdMPGAsPKnaBtmHiutzyIpENQbc98aFDNMHHbxCft09mIHm5G7yE=
Received: by 10.142.141.21 with SMTP id o21mr1165771wfd.199.1204812515850;
        Thu, 06 Mar 2008 06:08:35 -0800 (PST)
Received: by 10.143.52.6 with HTTP; Thu, 6 Mar 2008 06:08:34 -0800 (PST)
Message-ID: <7c612fc60803060608y64171fdu321cacb1b57849c1@mail.gmail.com>
Date: Thu, 6 Mar 2008 15:08:34 +0100
From: "Denis Dupeyron" <calchan@gentoo.org>
Sender: denis.dupeyron@gmail.com
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Monthly Gentoo Council Reminder for March
In-Reply-To: <C4B684E9-EE99-4568-AFE1-D7ABFC452466@gentoo.org>
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20080301103002.A2AE266A22@smtp.gentoo.org>
	 <FE6D272E-113E-449C-8AC6-7A1D57E9F543@gentoo.org>
	 <20080305184531.952d9550.genone@gentoo.org>
	 <C4B684E9-EE99-4568-AFE1-D7ABFC452466@gentoo.org>
X-Google-Sender-Auth: 232bff95daed4fbb
X-Archives-Salt: 090c159f-989d-43a7-8ad3-ff89f2e52114
X-Archives-Hash: d912d1f8e7519c3d9f9990faa844b6e3

On Wed, Mar 5, 2008 at 7:10 PM, Anant Narayanan <anant@gentoo.org> wrote:
>  maintainers don't need to complete the staff quiz.

The staff quiz is focused on our general procedures and how to behave
and interact with other devs. It is a great opportunity for the
recruiter to get to know who he (no "she"s in recruiters, applications
welcome) is talking to. It's at this time that I have the most
interesting discussions with the recruit and learn the most on the
individual (s)he is. We had enough issues in the past with technically
good people who just couldn't behave that I think skipping this phase
is really not a good idea. Because, believe it or not, the recruitment
process in general and the review in particular are not only about
checking yes/no boxes about the recruit's answers to obscure quizzes.
Plus, practically the staff quiz takes very little time. With the old
argument being that if you can't spend that little time on the staff
quiz then chances are you won't be a dev for long, and thus not worth
investing time in.

> On the technical side, about the only thing
>  they really require is a sound knowledge of bash, the do's and don'ts
>  of ebuilds, and knowledge of how to use eclasses.

This is currently what the ebuild quiz is trying to be. I don't
understand what difference you want to make between a full dev and a
package maintainer when both will have to write the same kind of
ebuilds, face the same kind of issues and have to come up with the
same kind of solutions. And in in the end create the same risk of
instability to the tree, only in a more fragmented, thus less
controllable way (due to more clueless people for the same job).

>  As for the privileges, maintainers wouldn't need an email account,
>  commit access to portions not concerning their package(s),

Meaning that they'll be allowed to break only a certain portion of the
tree. That's OK with me, as long as it's not the portion I use. I
believe some people depend on gentoo. I don't see any reason to risk
making their life miserable.

I hope you're not going to take any of the above personally. My
opinion is we have proxy maintenance and overlays like sunrise in
place already. If they're not working properly I suggest we fix them.
There's no point breaking something in the hope you'll fix something
else that doesn't work. Go to the root of the problem instead.

Denis.
-- 
gentoo-dev@lists.gentoo.org mailing list