From: Martin Schlemmer <azarah@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] GLEP system worthwhile?
Date: Fri, 11 Mar 2005 23:31:13 +0200 [thread overview]
Message-ID: <1110576673.8513.3.camel@nosferatu.lan> (raw)
In-Reply-To: <42320696.7030404@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1437 bytes --]
On Fri, 2005-03-11 at 20:59 +0000, Ian Leitch wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Grant Goodyear wrote:
> | It's worth noting that a GLEP author need not be a dev, so those
> | people, of course, would always require a surrogate to submit/revise
> | GLEPs. As for devs being able to upload/revise GLEPs, I'm not opposed.
> | The reason that devs cannot update their own GLEPs right now is purely
> | technical: the GLEP page is part of the www tree, and that tree has
> | fairly strict permissions. If opening up the GLEP directory isn't too
> | much of a pita for infra, I certainly won't oppose it. I would still
> | prefer that GLEPs be run by one of the editors before being posted,
> | since we may be able to help, but I wouldn't insist on it. I would be
> | very sad, though, if people took advantage of a more liberal policy to
> | post poorly-thought-out junk.
>
> If someone posts a poorly thought out GLEP then people will vote against
> it. If the author wishes, he/she can post a revised version and the
> voting process beings again. It's up to the author to make sure their
> idea is of decent quality first time round, unless they want to spend
> hours revising it.
>
Given, but there should be a cutoff point I think ... 3-5 tries is OK,
but 20 ....
--
Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-11 21:28 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
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 [this message]
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=1110576673.8513.3.camel@nosferatu.lan \
--to=azarah@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