public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <200512131106.54567.jstubbs@gentoo.org> (raw)

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



             reply	other threads:[~2005-12-13  2:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-13  2:06 Jason Stubbs [this message]
2005-12-13  2:15 ` [gentoo-dev] GLEP XX: Fix the GLEP process Jason Stubbs
2005-12-13  2:24   ` Ciaran McCreesh
2005-12-13  2:35     ` [gentoo-dev] " Dan Meltzer
2005-12-13  2:42       ` Ciaran McCreesh
2005-12-13  9:31         ` George Shapovalov
2005-12-13  2:39     ` [gentoo-dev] " Jason Stubbs
2005-12-13  2:58       ` Ciaran McCreesh
2005-12-13 14:11         ` Jason Stubbs
2005-12-13 21:16 ` Grant Goodyear
2005-12-14 16:16   ` Jason Stubbs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200512131106.54567.jstubbs@gentoo.org \
    --to=jstubbs@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox