From: Daniel Ostrow <dostrow@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] GLEP system worthwhile?
Date: Fri, 11 Mar 2005 10:47:11 -0500 [thread overview]
Message-ID: <1110556031.8218.9.camel@Memoria.anyarch.net> (raw)
In-Reply-To: <20050311150215.16418202@snowdrop>
On Fri, 2005-03-11 at 15:02 +0000, Ciaran McCreesh wrote:
> On Fri, 11 Mar 2005 08:39:51 -0600 Grant Goodyear <g2boojum@gentoo.org>
> wrote:
> | Thoughts / comments? I promise not to bite anyone's head off this
> | time!
>
> I don't think there's anything wrong with the system, except that
> certain managers can in effect put a GLEP on hold indefinitely because
> their favourite editor sucks.
>
> I'd rather have GLEPs than half-baked kook schemes. We've all seen how
> long they take to un-screw-up... Well, actually, we haven't, since
> they're still not un-screwed, but we've at least seen how much mess they
> make.
>
Agreed, the GLEP system is good as it stands. If you look at the recent
GLEPs that came through like the GLEPs 30 & 31 which went by (with one
minor exception *cough* nano *cough*) very quickly due to developer
interest. And others, like GLEP 19 for example, are under active
development. The problem is not with the GLEP system it's with the
developers who are either too lazy/busy to write up a proper GLEP for
things that need it, and thus don't want whatever it is to be
implemented too badly, or loose interest in one way or another in one
they have already written and neither of these can be fixed by changing
policy.
--Dan
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-03-11 15:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 14:39 [gentoo-dev] GLEP system worthwhile? Grant Goodyear
2005-03-11 15:02 ` Ciaran McCreesh
2005-03-11 15:47 ` Daniel Ostrow [this message]
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=1110556031.8218.9.camel@Memoria.anyarch.net \
--to=dostrow@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