From: Grant Goodyear <g2boojum@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: [gentoo-dev] GLEP system worthwhile?
Date: Fri, 11 Mar 2005 08:39:51 -0600 [thread overview]
Message-ID: <20050311143951.GA27199@dst.grantgoodyear.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1655 bytes --]
It's been a bit over a year and a half since glep.gentoo.org came
online, and GLEPs became the standard method for proposing significant
changes to Gentoo. I think it's time to assess what works, and what
doesn't, about this system. To date 30 GLEPs have been approved by the
GLEP editors that involve something other than the GLEP process itself.
Six of those GLEPs have been marked "Final", meaning they have been
successfully implemented. Seven more have been "Accepted", meaning
that the idea in the GLEP has been approved, but the implementation has
not yet been completed. Five are currently in "Draft" status, not yet
having been submitted for approval. One has been rejected. Eleven
GLEPs failed to get enough traction to be either approved or rejected,
and are thus "deferred". Do these statistics mean that the program is
working well, working poorly, or failed utterly? My personal opinion
is that even with the substantial number of timed-out GLEPs, the
program is still a modest success because these GLEPs provide a record
of notable, generally well-written proposals, which is a vast
improvement on seeing the same half-thought-out ideas appear on the
mailing lists time and time again. On the other hand, one might well
argue that fairly few substantial accomplishments have come about from
GLEPs, so perhaps GLEPs just add another bureaucratic impediment.
Thoughts / comments? I promise not to bite anyone's head off this time!
-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 --]
next reply other threads:[~2005-03-11 14:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 14:39 Grant Goodyear [this message]
2005-03-11 15:02 ` [gentoo-dev] GLEP system worthwhile? Ciaran McCreesh
2005-03-11 15:47 ` Daniel Ostrow
2005-03-11 15:50 ` Ian Leitch
2005-03-11 15:58 ` Ciaran McCreesh
2005-03-11 16:09 ` Ian Leitch
2005-03-11 17:05 ` Chris Gianelloni
2005-03-11 17:40 ` Ian Leitch
2005-03-11 18:24 ` Ciaran McCreesh
2005-03-11 20:28 ` Ian Leitch
2005-03-11 20:30 ` Ciaran McCreesh
2005-03-11 21:01 ` Ian Leitch
2005-03-11 21:30 ` Martin Schlemmer
2005-03-11 22:07 ` Donnie Berkholz
2005-03-11 18:39 ` Chris Gianelloni
2005-03-11 18:42 ` Ciaran McCreesh
2005-03-11 16:28 ` Marius Mauch
2005-03-11 19:40 ` Grant Goodyear
2005-03-11 19:59 ` Donnie Berkholz
2005-03-11 20:13 ` Ciaran McCreesh
2005-03-11 20:16 ` Donnie Berkholz
2005-03-11 17:03 ` Chris Gianelloni
2005-03-11 19:25 ` Grant Goodyear
2005-03-11 20:59 ` Ian Leitch
2005-03-11 21:10 ` Mike Frysinger
2005-03-11 21:31 ` Martin Schlemmer
2005-03-11 21:33 ` Ciaran McCreesh
2005-03-11 21:54 ` Martin Schlemmer
2005-03-11 23:34 ` Luis F. Araujo
2005-03-11 16:10 ` Benjamin A. Collins
2005-03-11 16:34 ` Marius Mauch
2005-03-11 19:42 ` Grant Goodyear
2005-03-14 13:09 ` Thierry Carrez
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=20050311143951.GA27199@dst.grantgoodyear.org \
--to=g2boojum@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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