public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Goodyear <g2boojum@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP XX: Fix the GLEP process
Date: Tue, 13 Dec 2005 15:16:36 -0600	[thread overview]
Message-ID: <20051213211636.GL8629@bmb24.uth.tmc.edu> (raw)
In-Reply-To: <200512131106.54567.jstubbs@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1757 bytes --]

Jason Stubbs wrote: [Mon Dec 12 2005, 08:06:54PM CST]
> 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.

You know, there's no reason that GLEPs need to be written by a single
person.  It's often true, though, that it is a single person's idea,
initially at least.

> 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.

Throwing out the initial GLEP amounts to the same thing, in my opinion,
since any interested parties are urged to provide feedback, and ideally
the next revision will include that feedback, either to accept it or
reject it.

> 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.

Yes, of course, GLEP authors should talk to the folks who are likely to
be affected beforehand, but if they fail to do so then the GLEP process
is likely to be rather protracted for that GLEP.  I have to admit that I
have no problem with people doing hard work for little gain, if that's
what people want to do.  *Shrug*  

-g2boojum-
-- 
Grant Goodyear	
Gentoo Developer
g2boojum@gentoo.org
http://www.gentoo.org/~g2boojum
GPG Fingerprint: D706 9802 1663 DEF5 81B0  9573 A6DC 7152 E0F6 5B76

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-12-13 21:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-13  2:06 [gentoo-dev] GLEP XX: Fix the GLEP process Jason Stubbs
2005-12-13  2:15 ` 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 [this message]
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=20051213211636.GL8629@bmb24.uth.tmc.edu \
    --to=g2boojum@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