Gentoo Archives: gentoo-dev

From: Duncan <1i5t5.duncan@×××.net>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Re: Gentoo Council Reminder for April 23
Date: Fri, 24 Apr 2009 08:34:42
Message-Id: pan.2009.04.24.08.34.07@cox.net
In Reply to: Re: [gentoo-dev] Gentoo Council Reminder for April 23 by Mart Raudsepp
1 Mart Raudsepp <leio@g.o> posted 1240508221.2635.18.camel@localhost,
2 excerpted below, on Thu, 23 Apr 2009 20:37:01 +0300:
3
4 > I think the whole council should understand why something received a
5 > "no" from someone, as they might be important technical (or subjective)
6 > arguments against having that in EAPI-3
7
8 > It is quite likely that almost all features will get a majority "yes"
9 > vote when taken individually because not all council members have seen
10 > the problems a few of the council members have. [T]he whole of the
11 > council should consider the objections of an individual council member,
12 > so that potentially bad things don't end up accepted based on some kind
13 > of an uninformed majority vote or concensus.
14
15 [Noting that this is now after the meeting...]
16
17 While you bring up a worthwhile point, keep in mind that based on
18 previous council discussion the current vote is preliminary -- the idea
19 being to select a set of features that the council would like in EAPI-3
20 for the PM folks to work on, then set a goal date for implementation.
21
22 At that date, the intent is that the council will take a look at what has
23 actually been implemented and how, checking any implementation problems
24 that occurred in the process, and /then/ vote a final yea or nay on
25 individual EAPI-3 features. Since they will have already been
26 implemented in test-EAPI form (with ebuilds using the non-final features
27 not allowed into the tree until EAPI-3 is finalized with those features
28 in it), once the vote is in, it should be a simple matter of flipping a
29 switch turning on an approved EAPI-3.
30
31 Thus, while knowing the individual reasons now, for the preliminary vote,
32 may prevent work on features ultimately voted down and thus is a good
33 thing, it's not the end of the world if the current vote fails to take
34 into account a valid objection. In fact if my read is correct, that's
35 one reason the council decided to do it this way. It prevents voting in
36 a standard that's difficult to implement, thus avoiding imposing
37 potentially difficult or impossible mandates on an after all volunteer
38 work force, with all the practical ugliness that entails.
39
40 --
41 Duncan - List replies preferred. No HTML msgs.
42 "Every nonfree program has a lord, a master --
43 and if you use the program, he is your master." Richard Stallman