Contents of /xml/htdocs/proj/en/glep/glep-0054.txt

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.1 - (show annotations) (download)
Fri Oct 12 02:08:27 2007 UTC (10 years, 8 months ago) by antarus
Branch: MAIN
File MIME type: text/plain
Add glep 54, to replace (and require) glep 39, regarding project announcements and RFCs.  I'm marking this as F (final) as it was approved ages ago; feel free to take up wording and merits with me and it will be edited after the fact.  If you have a problem with this process, again take it up with me as I'm the bastard that did it.  Thanks

1 GLEP: 54
2 Title: An "old-school" metastructure proposal with "boot for being a slacker" Part II
3 Version: $Revision: 1.1 $
4 Last-Modified: $Date: 2007/07/22 10:03:18 $
5 Author: Alec Warner <antarus@gentoo.org>
6 Status: Final
7 Type: Standards Track
8 Content-Type: text/x-rst
9 Created: 11-Oct-2007
10 Replaces: 39
11 Requires: 39
12 Post-History: 11-Oct-2007
15 Abstract
16 ========
18 This GLEP amends GLEP 39[#GLEP39]_. A new project must be announced
19 to the community prior to it's conception. The announcement should state
20 the project goals, the plan to achieve those goals, and any other information
21 deemed useful to the community by the person proposing a new project.
24 Motivation
25 ==========
27 Projects were being started behind the scenes that people were not aware of;
28 this included developers and users alike. It was thought important to notify
29 the community of new projects. This also enables new projects to get valuable
30 feedback before getting to far into design and implementation.
33 Rationale
34 =========
36 We hope projects receiving feedback fare better in the long run with regards
37 to general reception as well as meeting the goals set forth in their
38 announcement. We hope projects announced early get more volunteers by virtue
39 of being announced and in the community's view.
42 Backwards Compatibility
43 =======================
45 Projects already announced before 19-Oct-2006 are not affected. Since this
46 GLEP was authored nearly a year later, conceivably projects announced since
47 then should retroactively send mail regarding their goals and means to achieve
48 them if they have not done so already; otherwise they would be in breach of
49 policy set in 2006.
52 Specification
53 =============
55 New projects should send an Request For Comments mail to gentoo-dev (and
56 optionally gentoo-project) in order to received feedback from the Gentoo
57 community. Once the feedback has been received and changes incorportated into
58 the goals and design (if any), the project team should send a mail to
59 gentoo-dev-announce (and optionally gentoo-announce) regarding it's launch.
61 The contents of the announcements is left intentionally vague as to not
62 restrict the scope of projects, goals, and means. If announcement, projects,
63 goals, or means end up being terrible; the authors of this GLEP fully expect
64 the community to chew you out over it.
66 This GLEP does not empower the community to kill a new project, even if everyone
67 decides it sucks.
70 Copyright
71 =========
73 This document has been placed in the public domain.

  ViewVC Help
Powered by ViewVC 1.1.20