1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Grant Goodyear wrote: |
5 |
~ > Really? It's usually just a matter of e-mailing me. I read through |
6 |
| it, and if I see that the GLEP fails to answer some questions that I |
7 |
| predict will arise, I will generally mention it to the GLEP author and |
8 |
| suggest that such issues be addressed, even it is just to add a |
9 |
| section labeled "open questions". Very occasionally I will mention to |
10 |
| an author that I don't think a GLEP is actually needed, and suggest |
11 |
| that the author just talk to the appropriate person and implement it. |
12 |
| I don't believe that I have ever outright refused a GLEP, or even added |
13 |
| more than a day to the time for it to be posted. |
14 |
|
15 |
For example, I first proposed the Planet idea long before GLEP 30 came |
16 |
along. Basically the idea got shot down on IRC because infra were |
17 |
worried about storing unmoderated material on Gentoo hardware. At that |
18 |
point it was pretty much a "no", so I didn't bother following it up with |
19 |
a GLEP. |
20 |
|
21 |
Moving forward 1 year, we have Planet Gentoo. How the hell did that |
22 |
happen then? Daniel persevered and produced a GLEP but which looked to |
23 |
be doing nothing (like most other GLEPS) until gentooexperimental.org |
24 |
came along setup a non official Planet. This made it obvious the idea |
25 |
was popular and the implementation of the GLEP soon followed, as did |
26 |
infra's concerns seem to disappear. |
27 |
|
28 |
If we'd had a voting system, the popularity of the GLEP would have been |
29 |
obvious from the start, and no doubt we would have had the Planet |
30 |
implemented _much_ sooner. |
31 |
|
32 |
In a nutshell, we need a system where ideas can be put forward so that |
33 |
they have maximum exposure AND accessibility to vote. Posting them to |
34 |
- -dev sure gets them a lot of exposure (though mostly only to devs), but |
35 |
the majority of people likely to respond are those not in favor. Having |
36 |
a simple voting system will allow people to put their voice forward with |
37 |
maximum ease. |
38 |
|
39 |
The thing I dislike about the current system is that most devs/users |
40 |
will never hear about an idea until it makes onto glep.g.o. GLEPs need |
41 |
to be put our there for everyone to see at an early stage so people can |
42 |
vote on the IDEA, not the specifics or the quality of the GLEP itself. |
43 |
|
44 |
| Most of these issues are moot, however, because in many cases GLEP |
45 |
| authors prefer to post an informal GLEP on -dev first, gather comments, |
46 |
| and then submit a formal GLEP after an initial revision. |
47 |
|
48 |
Having all those in a central place would be far better, I'm sure there |
49 |
are many GLEPs sitting in devspace that I or you have never seen. |
50 |
|
51 |
| It's worth noting that a GLEP author need not be a dev, so those |
52 |
| people, of course, would always require a surrogate to submit/revise |
53 |
| GLEPs. As for devs being able to upload/revise GLEPs, I'm not opposed. |
54 |
| The reason that devs cannot update their own GLEPs right now is purely |
55 |
| technical: the GLEP page is part of the www tree, and that tree has |
56 |
| fairly strict permissions. If opening up the GLEP directory isn't too |
57 |
| much of a pita for infra, I certainly won't oppose it. I would still |
58 |
| prefer that GLEPs be run by one of the editors before being posted, |
59 |
| since we may be able to help, but I wouldn't insist on it. I would be |
60 |
| very sad, though, if people took advantage of a more liberal policy to |
61 |
| post poorly-thought-out junk. |
62 |
|
63 |
If someone posts a poorly thought out GLEP then people will vote against |
64 |
it. If the author wishes, he/she can post a revised version and the |
65 |
voting process beings again. It's up to the author to make sure their |
66 |
idea is of decent quality first time round, unless they want to spend |
67 |
hours revising it. |
68 |
|
69 |
Regards, |
70 |
Ian Leitch |
71 |
|
72 |
-----BEGIN PGP SIGNATURE----- |
73 |
Version: GnuPG v1.4.0 (GNU/Linux) |
74 |
|
75 |
iD8DBQFCMgaWefZ4eWAXRGIRAlq5AJ0abRJqZJBHsujCHgTGAqT56OZ+awCgjAAg |
76 |
1sYVgg8bfD9xsKoI81VMPm4= |
77 |
=Wlfb |
78 |
-----END PGP SIGNATURE----- |
79 |
-- |
80 |
gentoo-dev@g.o mailing list |