| 1 |
Abstract |
| 2 |
|
| 3 |
The purpose of GLEPs is to coordinate several teams into providing an overall |
| 4 |
enhancement to Gentoo. However, the GLEP itself is written by a single person |
| 5 |
rather than a cooperative effort between the teams. |
| 6 |
|
| 7 |
|
| 8 |
Motivation |
| 9 |
|
| 10 |
Recent GLEPs have attempted to force things on other teams. This just doesn't |
| 11 |
work. |
| 12 |
|
| 13 |
|
| 14 |
Specification |
| 15 |
|
| 16 |
Rather than coming to the ML with a completed GLEP and then asking for |
| 17 |
feedback, a GLEP author should look at the teams involved and then select a |
| 18 |
solicit a member from each team to be responsible for that area of the GLEP. |
| 19 |
The GLEP author may represent any teams they belong to. |
| 20 |
|
| 21 |
|
| 22 |
Rationale |
| 23 |
|
| 24 |
Rather than doing lots of hard work and having it thrown away once it is found |
| 25 |
to be unacceptable by the teams involved, the teams involved share the hard |
| 26 |
work and come up with something acceptable to everybody right from the |
| 27 |
outset. |
| 28 |
|
| 29 |
|
| 30 |
Backwards Compatibility |
| 31 |
|
| 32 |
Nothing |
| 33 |
|
| 34 |
|
| 35 |
Reference Implementation |
| 36 |
|
| 37 |
Just do it. |
| 38 |
|
| 39 |
|
| 40 |
Copyright |
| 41 |
|
| 42 |
Public Domain |
| 43 |
-- |
| 44 |
gentoo-dev@g.o mailing list |
Archives