1 |
Recently we've had a fair number of "big" projects proposed, both on the |
2 |
-core list and on the -dev list, including herds, udder, refinement of |
3 |
-stable and -stats (now subsumed by herds?), uid/gid handling, new types |
4 |
of init scripts, hardened gentoo, using "delta"s when upgrading gentoo |
5 |
packages, and probably a number of other things that have dropped off |
6 |
the scope. Unfortunately, we have no single repository of these |
7 |
proposals, which means that it's very easy for both good and bad ideas |
8 |
to be proposed and then quickly forgotten. |
9 |
|
10 |
My proposal is that we adopt Python's concept of Python Enhancement |
11 |
Proposals (http://www.python.org/peps/), which serves as Python's system |
12 |
for handling large-scale proposals. (Incidentally, Gnome has also |
13 |
adopted this idea, calling them Gnome Enhancement Proposals: |
14 |
http://developer.gnome.org/gep/list.html.) |
15 |
|
16 |
I've made a start. Take a look at http://www.gentoo.org/proj/en/glep, |
17 |
and you'll see two informational GLEPs already present. (If you want to |
18 |
make your own GLEP proposal, see the README.txt file in |
19 |
http://cvs.gentoo.org/cgi-bin/viewcvs.cgi/gentoo/xml/htdocs/proj/en/glep/ as well as GLEP 2. Incidentally, the reason for choosing ReST, barely-marked-up text, as the base format is to make proposals simple to write without too much worry about the formatting. It should be relatively simple to convert ReST to our guide-xml, if desired.) |
20 |
|
21 |
Here's the comments that have been made so far about this GLEP proposal |
22 |
from other developers: |
23 |
|
24 |
* Numerous votes in favor. |
25 |
|
26 |
* It's been suggested out that GLEPs will solve the problem of a |
27 |
moderator on the mailing lists to summarize where current proposals are, |
28 |
as that's now the job of the GLEP authors, help increase signal-to-noise |
29 |
on -dev, and help consolidate pros and cons. |
30 |
|
31 |
* Existing Gentoo devs are willing to help with infrastructure and |
32 |
creating any needed new tools. |
33 |
|
34 |
* One comment that perhaps it would make more sense for people to |
35 |
develop GLEPs (until ratified) on the new gentoo development wiki. I'm |
36 |
biased, but I prefer a more formal proposal submission method because I |
37 |
think people are more likely to spend time polishing it before |
38 |
submitting it. |
39 |
|
40 |
Now it's time to open up this idea to the general Gentoo Linux |
41 |
community. Thoughts? Comments? Suggestions? |
42 |
-- |
43 |
Grant Goodyear <g2boojum@g.o> |