From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
	by nuthatch.gentoo.org with esmtp (Exim 4.54)
	id 1ElzbF-0007uR-Cw
	for garchives@archives.gentoo.org; Tue, 13 Dec 2005 02:09:05 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
	by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jBD28JcT022282;
	Tue, 13 Dec 2005 02:08:19 GMT
Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30])
	by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jBD26W8s002859
	for <gentoo-dev@lists.gentoo.org>; Tue, 13 Dec 2005 02:06:32 GMT
Received: from jj039137.ppp.dion.ne.jp ([211.4.39.137] helo=opteron246.suzuki-stubbs.home)
	by smtp.gentoo.org with esmtpa (Exim 4.54)
	id 1ElzYl-00016J-G9
	for gentoo-dev@lists.gentoo.org; Tue, 13 Dec 2005 02:06:31 +0000
Received: by opteron246.suzuki-stubbs.home (Postfix, from userid 1000)
	id A5A89201A47; Tue, 13 Dec 2005 11:06:54 +0900 (JST)
From: Jason Stubbs <jstubbs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] GLEP XX: Fix the GLEP process
Date: Tue, 13 Dec 2005 11:06:54 +0900
User-Agent: KMail/1.9
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200512131106.54567.jstubbs@gentoo.org>
X-Archives-Salt: b10e4154-5adc-4a64-a636-308fdcb0b075
X-Archives-Hash: 420907d2776957f4e576652530441274

Abstract

The purpose of GLEPs is to coordinate several teams into providing an overall 
enhancement to Gentoo. However, the GLEP itself is written by a single person 
rather than a cooperative effort between the teams.


Motivation

Recent GLEPs have attempted to force things on other teams. This just doesn't 
work.


Specification

Rather than coming to the ML with a completed GLEP and then asking for 
feedback, a GLEP author should look at the teams involved and then select a 
solicit a member from each team to be responsible for that area of the GLEP. 
The GLEP author may represent any teams they belong to.


Rationale

Rather than doing lots of hard work and having it thrown away once it is found 
to be unacceptable by the teams involved, the teams involved share the hard 
work and come up with something acceptable to everybody right from the 
outset.


Backwards Compatibility

Nothing


Reference Implementation

Just do it.


Copyright

Public Domain
-- 
gentoo-dev@gentoo.org mailing list