1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Ciaran McCreesh wrote: |
5 |
| | I propose that a dev is free to upload a GLEP in any state of |
6 |
| | completeness/correctness as they wish, devs can then vote on said |
7 |
| | GLEP. If the GLEP author makes changes, devs then vote again on that |
8 |
| | revision. This system also gives power back to the devs (and users if |
9 |
| | they're allowed to vote) and away from the GLEP editors. |
10 |
| |
11 |
| 'Any' state is asking for trouble. You can post non-finished GLEP plans |
12 |
| to the list in any state, but I'd expect things making it onto the site |
13 |
| to be at least in reasonable draft state. |
14 |
|
15 |
OK, that's fair enough, but just so long as the author can post a |
16 |
revised version and have devs vote on it again. The main reason for this |
17 |
is that it's hard to track changes made to a GLEP in a massive long -dev |
18 |
thread. |
19 |
|
20 |
Regards, |
21 |
Ian Leitch |
22 |
|
23 |
-----BEGIN PGP SIGNATURE----- |
24 |
Version: GnuPG v1.4.0 (GNU/Linux) |
25 |
|
26 |
iD8DBQFCMcLVefZ4eWAXRGIRAlXHAJ9nVGcarUlJoEUjb57N3T9ZzDqWdwCfexRK |
27 |
fY/QdqTl/GbAbwFOOhT9iY4= |
28 |
=sz/5 |
29 |
-----END PGP SIGNATURE----- |
30 |
-- |
31 |
gentoo-dev@g.o mailing list |