Gentoo Archives: gentoo-dev

From: Michael Hammer <mueli@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] EAPI-2
Date: Fri, 12 Sep 2008 06:28:56
Message-Id: 20080912062852.GI11796@mephisto
In Reply to: Re: [gentoo-dev] EAPI-2 by Ciaran McCreesh
1 Hi folks!
2
3 I am not involved in creating the EAPI 2 draft but I am interested in
4 the discussion and would like to track the technical evolution but
5 this seams nearly impossible as you're not able to agree on a public
6 draft document.
7
8 * Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> [080911 20:02]:
9 > On Mon, 08 Sep 2008 23:34:28 +0000
10 > "Jorge Manuel B. S. Vicetto" <jmbsvicetto@g.o> wrote:
11 > > Given the earlier discussion about EAPI-2 in
12 > > http://archives.gentoo.org/gentoo-dev/msg_3e9d42191c3537c4f699c12cadd0ad99.xml
13 > > and cardoe's earlier request to the council ml, can the council
14 > > members discuss this proposal and consider voting it?
15 > > Does anyone have any objections to this proposal?
16 >
17 > I've prepared patches for PMS for this lot. They can be found on the
18 > branch 'eapi-2' at git://git.overlays.gentoo.org/proj/pms.git . Can we
19 > use these as the definitive definition?
20
21 So my request to the council is not a technical decision on the
22 content itself but at least a decision about which document is the
23 official draft.
24
25 So here are my suggestions: (which are an enhancement over the GLEP
26 process)
27
28 - An official (by the council accepted) VCS repo (a la git) for the
29 document (EAPI draft or even the PMS spec?)
30
31 - An interface (mailing address) where everyone interested can submit
32 a patch for this document and a herd which is responsible for
33 maintaining and merging the patches if accepted. (<- we need a
34 procedure especially for the accept of patches. Voting, council
35 decision, herd decision)
36
37 - A project page where the patches are published (and evtl. can be
38 voted) and the HEAD is public readable
39
40 - The technical discussion can then be made in mailing list but then
41 every dev has a possibility to follow the technical issues in a
42 concentrated way and we have a place where we can cite and ref to.
43
44 - To make this work any other document or source for drafts has to be
45 declined and not discussed (this seams hard but is IMHO the only way
46 to make things work)
47
48 So long and thx for all the fish,
49
50 mueli
51
52 p.S.: If I missed something and something I mentioned already exists
53 then please correct me or forget my request but please be also so kind
54 and publish in a documentation (perhaps somewhere at [1]) where to
55 find informations on the EAPI process.
56
57 [1] ... http://www.gentoo.org/doc/en/list.xml
58
59 --
60 ------------------------------------------------------------
61 Michael Hammer | <mueli@g.o> | Graz, AT
62 Geno's Developer (Kerberos) | http://www.michael-hammer.at
63 LocalWords: Kerberos

Replies

Subject Author
Re: [gentoo-dev] EAPI-2 Ciaran McCreesh <ciaran.mccreesh@××××××××××.com>