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
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
|
\summary{2008}{6}{12}
Agenda call: \agoref{gentoo-dev}{8d3e2ff5235b214f77d234449cdd5897}
Agenda announcement: \agoref{gentoo-dev}{868e239918e9bf80524415d5d12e2493}
\agendaitem{Moderation}
\index{council!meeting!channel mode}
Shall we use channel modes +qnm, with voice for people involved in discussions?
This means
\begin{itemize}
\item
+m - Moderated - People who don't have voices (+v) can't send
messages to the channel.
\item
+n - No external messages - With this mode, no one can send messages
to the channel without even being joined.
\item
+z - Relaxed moderation - When +z is set each message that would be
blocked by +m is sent to all the users who are currently operator.
\end{itemize}
Concusion --- if it becomes necessary, we'll do it. We leave the channel open
until then.
\agendaitem{Time limit}
\index{council!meeting!time limit}
Shall we set a time limit of 2 hours for the council meeting? ---
Yes. We will move any topics we didn't cover to the mailing lists.
\agendaitem{PMS: Are versions allowed to have more than 8 digits?}
\index{PMS}\index{eclass!versionator}\index{version specifications}
References:
\begin{itemize}
\item
\agoref{gentoo-dev}{db2f5c09c2c0c8b042ca3d0dcec7cdaf}
\item
\bug{188449}
\end{itemize}
The required testing was not done in the meantime. We still voted to allow
versions $>8$ digits. Adding a maximum restriction is a separate question and
was not addressed -- if anyone wants this restriction, please discuss with
fellow implementors and present your consensus to the council.
\agendaitem{How to handle the current appeals}
\index{council!appeal process}\index{enforced retirement}
Refernce: \agoref{gentoo-council}{d7c402fb577a3d5b1707e2bdf4b0a264}
Decision: We approved \dev{dberkholz}'s proposal.
\agendaitem{as-needed by default}
\index{as-needed}\index{--as-needed}\index{LDFLAGS}
Reference: \agoref{gentoo-dev}{fdfd519c5372394cc7f3aacaefa387b9}
\dev{antarus} requested that we vote on whether to add --as-needed to the
default LDFLAGS.
Whether this should be in default LDFLAGS or suggested in make.conf.example
wasn't clear. \dev{betelgeuse} suggested that we should know the whole tree
will build with this LDFLAGS setting (with open bugs for packages that append
-Wl,--no-as-needed) before we would consider enabling it by default.
The current state of the tree is tracked in \bug{129413}.
\dev{antarus} will post a deployment plan to -dev for discussion. We can vote
on it on -council as soon as it solidifies.
\agendaitem{GLEP 54}
\index{GLEP!54}\index{scm version suffix}\index{PV}
References:
\begin{itemize}
\item
\glep{54}
\item
\agoref{gentoo-dev}{c6e4ba8293f50c1e0444e67d59cf85ea}
\item
\agoref{gentoo-dev}{05614741b3942bfdfb21fd8ebb7955e0}
\end{itemize}
\dev{lu_zero} posted an alternative approach 12 hours ago. Since it hasn't been
around long enough to get much feedback, we decided to let the proposals
develop and see if the ideas somehow merge.
\agendaitem{GLEP 55}
\index{GLEP!55}\index{EAPI suffix}
References:
\begin{itemize}
\item
\glep{55}
\item
\agoref{gentoo-dev}{c6e4ba8293f50c1e0444e67d59cf85ea}
\end{itemize}
Let's vote once the discussion is no longer clearly ongoing. We can hold this
vote on the -council mailing list instead of waiting for the next meeting.
\agendaitem{GLEP 56}
\index{GLEP!56}\index{use flags}\index{metadata.xml}
References:
\begin{itemize}
\item
\glep{56}
\item
\agoref{gentoo-dev}{784e2b1c30bbffcaca4c27d3961de9c9}
\item
\agoref{gentoo-dev}{54ee20d2b1d8122370afdd4b3d7aafc9}
\end{itemize}
There is still room for improvement in \glep{56}, not so much in its
technical aspects but in the way it promotes itself, the possible
generation of legacy files, and the tools to use it.\footnote{Note that in this
iteration the intention is that global useflag descriptions cannot be
overridden locally. This later changed.}
A final vote will be done on the -council mailing list.
\agendaitem{Status of PMS}
\index{PMS}
\dev{ferringb} said:
``I'd like the council to please discuss the current status of PMS, if
the running of it satisfys the councils requirements of a *neutral*
standard, if the proposed spec actually meets said standards, and if
said spec is actually going to be approved sometimes this side of '09.''
References:
\begin{itemize}
\item
\agoref{gentoo-dev}{9e9652212b3aefe09d93fc24c6ec4cb7}
\item
\agoref{gentoo-dev}{37b3ca89a1d253516437facd22a3d806}
\end{itemize}
Result: This is a discussion that belongs on the mailing list. Council
members should post anything they have to add by the end of the weekend.
\vspace*{1cm}
Several further agenda items are mentioned in the official summary, but were
not actually discussed during the meeting.
|
GitWeb