1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 06/23/2013 05:28 PM, hasufell wrote: |
5 |
> @dberkholz |
6 |
> |
7 |
> From your manifesto: |
8 |
> |
9 |
>> I continue to believe that technical advances are, and should be, |
10 |
>> driven by individuals. Given our volunteer culture, a council can't |
11 |
>> force people to do things they don't want to do, but it can help |
12 |
>> to break up disputes and roadblocks, and make global decisions when |
13 |
>> needed. |
14 |
> |
15 |
> Do you think that gentoo is consistent in it's behavior? |
16 |
> |
17 |
> Should the council step in without any1 asking them if there are |
18 |
> changes about to happen that are a) global and b) highly controversial |
19 |
> discussed? |
20 |
> |
21 |
> As an example: multilib. The council was not involved in that decision |
22 |
> between eclass vs multilib-portage. Since any1 is allowed to add |
23 |
> eclasses to the tree the decision was somehow implicit, without any |
24 |
> real consensus on what the course should be. |
25 |
> |
26 |
> |
27 |
|
28 |
- From http://devmanual.gentoo.org/eclass-writing/ : |
29 |
|
30 |
"Before committing a new eclass to the tree, it should be emailed to the |
31 |
gentoo-dev mailing list with a justification and a proposed |
32 |
implementation. Do not skip this step — sometimes a better |
33 |
implementation or an alternative which does not require a new eclass |
34 |
will be suggested." |
35 |
|
36 |
The dev manual doesn't believe this is implicit nor without any |
37 |
consensus. True, it doesn't ban you from adding a new eclass, but it |
38 |
doesn't say you can just go and randomly add new eclasses without |
39 |
discussion either. |
40 |
|
41 |
- -Zero |
42 |
-----BEGIN PGP SIGNATURE----- |
43 |
Version: GnuPG v2.0.19 (GNU/Linux) |
44 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
45 |
|
46 |
iQIcBAEBAgAGBQJRx33WAAoJEKXdFCfdEflKQscQALJBt8oaLsdVKO0U/KSo7ZFo |
47 |
RZ3/JJLkoFY1In6ny4aLN/50Fzimdi1+941gViMMixFOspHN3iDqL26PqZGR9dnV |
48 |
NLoNm2sGOEFp0kfTK2Ebx6BZN+9MhMxHTdJAwHd7QxCdV2Zat2UuoQLcRVNlL66H |
49 |
as1ogjjZAeYeDQbz5Jqu9mxVRpZUuvINAqwS0Pe44kP9hzgEqlKUTXshxhwfJnZM |
50 |
hMWHfFG7KRDvlrttM0oPK3kLh/djn5RWGbuMGoycmogBgmbwvdGf9V8WNreynivO |
51 |
rDcY9L4Mjp4o873CgW2ffPdTNb5NYkaQ0amJg3HWG33B2MNWx1ULSJ+yneuHewfz |
52 |
7YtaVy8MHElllpckFSNhrk1as9PY2hLaivm0XmZZQ7GUcAo2tkcHAmOuxvYYmfu6 |
53 |
Sz3JYflUfgrpsycuBDrFMxz4/CsuxhJ1HhPLShJufVXmNOAQJiwRYUvvZ0Qy+6zP |
54 |
IOQIPd12BZGoyovOUjEA2zuHRxpDX7Tv8Em7HSmscwzNR+QQ/4MvNpk3BolvDPX6 |
55 |
h8hLou6yBgEIab2IN8dbsoyFaqSHW/jjsYes50HISUYXdDuSivkoqyFjGmd23w5n |
56 |
bO0JRJDbDbrh1H/nmQkxeaHz4BunuinJoii7l7l3og3tj0LiZoyI9HkkDaNWGybE |
57 |
CXuBbHFK2jldX7mdBJzC |
58 |
=HkU2 |
59 |
-----END PGP SIGNATURE----- |