public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] GLEP system worthwhile?
Date: Fri, 11 Mar 2005 12:03:19 -0500	[thread overview]
Message-ID: <1110560600.21812.112.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <4231BE29.2020408@gentoo.org>

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

On Fri, 2005-03-11 at 15:50 +0000, Ian Leitch wrote:
> This system also gives power back to the devs (and users if they're
> allowed to vote) and away from the GLEP editors.

Another abuse of power by the management trying to keep the little man
down!  Oh the injustice!

Sorry, man, but if you can't take the 30 minutes to write up a
well-written proposal in a readable and already established format, then
how can you possibly expect others to take the idea seriously?  (This
isn't meant to be pointing against you, Ian.)

The truth is that there are a lot of good ideas that die on the vine
simply because there isn't enough interest in them, or they aren't
thought out to a usable state.  I think we have also seen that sometimes
even a good idea just doesn't have enough momentum to keep it going.
Couple that with the fact that most of the work done on Gentoo doesn't
affect Gentoo on a global scope, and hence, doesn't require a GLEP, and
I would say the system has worked pretty well.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-03-11 16:59 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
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 [this message]
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=1110560600.21812.112.camel@cgianelloni.nuvox.net \
    --to=wolf31o2@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