public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Goodyear <g2boojum@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Gentoo Linux Enhancement Proposals
Date: 06 Jun 2003 15:55:45 -0400	[thread overview]
Message-ID: <1054929345.8411.26.camel@orange-pc.ces.clemson.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 2356 bytes --]

Recently we've had a fair number of "big" projects proposed, both on the
-core list and on the -dev list, including herds, udder, refinement of
-stable and -stats (now subsumed by herds?), uid/gid handling, new types
of init scripts, hardened gentoo, using "delta"s when upgrading gentoo
packages, and probably a number of other things that have dropped off
the scope.  Unfortunately, we have no single repository of these
proposals, which means that it's very easy for both good and bad ideas
to be proposed and then quickly forgotten.

My proposal is that we adopt Python's concept of Python Enhancement
Proposals (http://www.python.org/peps/), which serves as Python's system
for handling large-scale proposals. (Incidentally, Gnome has also
adopted this idea, calling them Gnome Enhancement Proposals:
http://developer.gnome.org/gep/list.html.)

I've made a start.  Take a look at http://www.gentoo.org/proj/en/glep,
and you'll see two informational GLEPs already present.  (If you want to
make your own GLEP proposal, see the README.txt file in
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.)

Here's the comments that have been made so far about this GLEP proposal
from other developers: 

* Numerous votes in favor.

* It's been suggested out that GLEPs will solve the problem of a
moderator on the mailing lists to summarize where current proposals are,
as that's now the job of the GLEP authors, help increase signal-to-noise
on -dev, and help consolidate pros and cons.

* Existing Gentoo devs are willing to help with infrastructure and
creating any needed new tools.

* One comment that perhaps it would make more sense for people to
develop GLEPs (until ratified) on the new gentoo development wiki.  I'm
biased, but I prefer a more formal proposal submission method because I
think people are more likely to spend time polishing it before
submitting it.

Now it's time to open up this idea to the general Gentoo Linux
community.  Thoughts?  Comments?  Suggestions?
-- 
Grant Goodyear <g2boojum@gentoo.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-06-06 19:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-06 19:55 Grant Goodyear [this message]
2003-06-07 10:52 ` [gentoo-dev] Gentoo Linux Enhancement Proposals Michael Kohl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1054929345.8411.26.camel@orange-pc.ces.clemson.edu \
    --to=g2boojum@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox