1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
Summary of Gentoo council meeting 13 December 2011
Roll call
=========
betelgeuse
chainsaw
dberkholz
grobian
jmbsvicetto
ulm
missing
-------
ssuominen (proxy for hwoarang)
"Sighted pages" in the Gentoo wiki
==================================
Discuss/vote: Is this a council issue at the moment? [1]
The Council aggreed unanimously that this is not an issue for the
Council at the moment. The issue not yet clear, which makes it hard to
form an opinion on the subject, which is believed to be more of an issue
of the wiki team.
The Council advises to take up the issue with the wiki team. For this
case, it seems that the Council should only get involved through the
normal escalation procedures, as last resort.
In a side remark, the Council suggests using the term "reviewed pages",
which seems to express more clearly what the pages are about.
Quiet build default in Portage
==============================
Discuss/vote: Should the quiet default get reverted before affected
Portage versions get stabilised? [2]
The Council agreed that quiet-build behaviour of Portage should be made
an opt-in for existing installs (chainsaw, jmbsvicetto, grobian). The
suggested implementation for this is by reverting the default of
quiet-build.
Indifferent to the value of this default for existing installs:
dberkholz, ulm, betelgeuse.
The Council agreed that quiet-build behaviour of Portage can be made the
default for new installs (dberkholz, betelgeuse, jmbsvicetto, chainsaw,
grobian). A possible implementation for this suggested by jmbsvicetto
is via the stage building process (catalyst) to enable quiet-build in
the produced make.conf.
Indifferent to the value of this default for new installs: ulm.
The Council likes to note that the quiet-build option in itself seems
unknown to many, and hence leads to people searching for long how to
change it. Some pointers to documentation may be necessary. As
understood, a GLEP 42 news item is already planned. Another way of
getting it better documented would be to add it commented out to
make.conf.
Open bugs with Council involvement
==================================
There are currently no open Council bugs
Open actions from last meeting
==============================
- eclass API change devmanual patch from meeting 20111108 (betelgeuse)
A patch to the devmanual was committed during this meeting.
- eclass API changes discussion from meeting 20111108 (grobian)
No progress has been made (no discussion has been opened yet).
- moving council elections results to the elections project space (jmbsvicetto)
No progress has been made (open issue is the dates of some old council
elections).
Open floor
==========
No issues were brought up.
Next meeting date
=================
10 January 2012, 20:00 UTC.
[1] http://archives.gentoo.org/gentoo-project/msg_01e478ad89a5a27ff42471ba37fba287.xml
[2] http://archives.gentoo.org/gentoo-project/msg_4e282bb4e6ac2611de2a39171a803c48.xml
|
GitWeb