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 13:39:44 -0500	[thread overview]
Message-ID: <1110566384.21812.119.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <4231D807.6030805@gentoo.org>

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

On Fri, 2005-03-11 at 17:40 +0000, Ian Leitch wrote:
> Yes, but:
> 
> 1) The revision has to go through one of 2 GLEP editors, what's wrong
> with letting a dev do this themselves. I agree with genone on letting
> devs have CVS access. Pkus it's not obvious on the GLEP main page which
> GLEPs have been updated and require votes.

I could agree with this only if there were something in place that keeps
a new GLEP from being posted until it meets the proper layout.  I don't
want to see completely worthless entries that are still a work in
progress.  I would like it to at least be somewhat complete before I
spend time looking through them.

I'm thinking something like a barrier to entry, but not for editing.
Give the GLEP authors and a group of people accepted by the author
access to edit the GLEP.

> 2) Voting is done on -dev, I can't think of a worse place to conduct a
> vote. We need a web interface to count and clearly display votes for
> each revision.

I agree with you here.  Voting over a mailing list just isn't very
efficient.  Perhaps a login-restricted web page?  How about an app on
toucan?  "vote glep19 yes" or something equally as insane...

-- 
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 18:35 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 [this message]
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=1110566384.21812.119.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