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