| 1 |
On Fri, 2005-03-11 at 17:40 +0000, Ian Leitch wrote: |
| 2 |
> Yes, but: |
| 3 |
> |
| 4 |
> 1) The revision has to go through one of 2 GLEP editors, what's wrong |
| 5 |
> with letting a dev do this themselves. I agree with genone on letting |
| 6 |
> devs have CVS access. Pkus it's not obvious on the GLEP main page which |
| 7 |
> GLEPs have been updated and require votes. |
| 8 |
|
| 9 |
I could agree with this only if there were something in place that keeps |
| 10 |
a new GLEP from being posted until it meets the proper layout. I don't |
| 11 |
want to see completely worthless entries that are still a work in |
| 12 |
progress. I would like it to at least be somewhat complete before I |
| 13 |
spend time looking through them. |
| 14 |
|
| 15 |
I'm thinking something like a barrier to entry, but not for editing. |
| 16 |
Give the GLEP authors and a group of people accepted by the author |
| 17 |
access to edit the GLEP. |
| 18 |
|
| 19 |
> 2) Voting is done on -dev, I can't think of a worse place to conduct a |
| 20 |
> vote. We need a web interface to count and clearly display votes for |
| 21 |
> each revision. |
| 22 |
|
| 23 |
I agree with you here. Voting over a mailing list just isn't very |
| 24 |
efficient. Perhaps a login-restricted web page? How about an app on |
| 25 |
toucan? "vote glep19 yes" or something equally as insane... |
| 26 |
|
| 27 |
-- |
| 28 |
Chris Gianelloni |
| 29 |
Release Engineering - Strategic Lead/QA Manager |
| 30 |
Games - Developer |
| 31 |
Gentoo Linux |
Archives