public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marius Mauch <genone@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] GLEP system worthwhile?
Date: Fri, 11 Mar 2005 17:28:03 +0100	[thread overview]
Message-ID: <20050311172803.18579d5f@sven.genone.homeip.net> (raw)
In-Reply-To: <20050311155822.3c0e1ddf@snowdrop>

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

On Fri, 11 Mar 2005 15:58:22 +0000
Ciaran McCreesh <ciaranm@gentoo.org> wrote:

> On Fri, 11 Mar 2005 15:50:01 +0000 Ian Leitch <port001@gentoo.org>
> wrote:
> | I propose that a dev is free to upload a GLEP in any state of
> | completeness/correctness as they wish, devs can then vote on said
> | GLEP. If the GLEP author makes changes, devs then vote again on that
> | revision. This system also gives power back to the devs (and users
> | if they're allowed to vote) and away from the GLEP editors.
> 
> 'Any' state is asking for trouble. You can post non-finished GLEP
> plans to the list in any state, but I'd expect things making it onto
> the site to be at least in reasonable draft state.

Agreed, but being able to have potential/unfinished gleps available (so
you can check them by url, but not by clicking a link on the index)
would be nice so people who are asked by glep authors to
proofread/comment/poop on a new glep don't have to remember all the
custom d.g.o URLs. Another thing is that I'd like to update it directly
and not to have to send diffs/new versions to some gatekeeper instance.
So maybe direct commit access for devs (as mentioned in GLEP1) with some
special magic for the index page?

Marius

-- 
Public Key at http://www.genone.de/info/gpg-key.pub

In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.

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

  parent reply	other threads:[~2005-03-11 16:26 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 [this message]
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=20050311172803.18579d5f@sven.genone.homeip.net \
    --to=genone@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