summaryrefslogtreecommitdiff
blob: 499682e5a4507f26fed837210523fee1a4ef701b (plain)
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
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
\summary{2008}{6}{12}


\agendaitem{Moderation}
\index{council!meeting!channel mode}

Modes +qnm, with voice for people involved in discussions?

If it becomes necessary, we'll do it. Leave channel open till then.


\agendaitem{Time limit}
\index{council!meeting!time limit}

2 hours?

Yes. We'll move any topics we didn't cover to the mailing lists.



\agendaitem{Document of being an active developer}
\index{developer certificate}

Last month: Numerous suggested improvements to info on the certificate.

Preparation: araujo needs to post progress, an updated certificate and 
any new requests to the gentoo-council or gentoo-project list 2+ hours 
before the meeting.

Goal: Suggest changes. This should happen on-list. No discussion 
expected.


\agendaitem{Slacker arches}
\index{arches!slacking}

Preparation: vapier needs to send the post 2+ hours before the meeting.

Goal: Suggest changes. This should happen on-list. No discussion 
expected.


\agendaitem{Can the council help fewer bugs get ignored by arm/sh/s390 teams?}
\index{arch!arm}\index{arch!sh}\index{arch!s390}

Preparation: Someone on an undermanned arch team needs to describe their 
workflow on-list 2+ hours before the meeting.

Goal: Suggest changes. This should happen on-list. No discussion 
expected.


\agendaitem{PMS: Are versions allowed to have more than 8 digits?}
\index{PMS}\index{eclass!versionator}

References:
\begin{itemize}
 \item 
 \agoref{gentoo-dev}{db2f5c09c2c0c8b042ca3d0dcec7cdaf}
 \item
 \bug{188449}
\end{itemize}

Preparation: Do the package maintainers with extremely long PVs need 
them? The involved packages:
\begin{verbatim}
	sys-process/fuser-bsd
	sys-apps/net-tools
	sys-apps/gradm
	net-im/ntame
	media-video/captury
	media-libs/libcaptury
	media-libs/capseo
	sys-block/btrace
	www-apache/mod_depends
	net-wireless/rt2500
	sys-fs/unionfs
\end{verbatim}

Preparation: What's the impact of extending versionator.eclass? 

Goal: With data in hand, make a decision.

Decision: We didn't have all of the testing requested. 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 appeals}
\index{council!appeal process}

Preparation: Post to the gentoo-council mailing list 2+ hours before the 
meeting with your opinion.

\agoref{gentoo-council}{d7c402fb577a3d5b1707e2bdf4b0a264}

Goal: Vote on an approach that was previously posted to the list.

Decision: We approved dberkholz's proposal.



\agendaitem{as-needed by default}
\index{as-needed}\index{--as-needed}\index{LDFLAGS}

antarus requested that we vote on whether to add it to the default 
LDFLAGS.

Preparation: Post your opinion to the -dev thread "RFC: --as-needed to 
default LDFLAGS" 2+ hours before the meeting.

\agoref{gentoo-dev}{fdfd519c5372394cc7f3aacaefa387b9}

Goal: Vote.

Result: Whether this should be in default LDFLAGS or suggested in 
make.conf.example wasn't clear. 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.

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}

Preparation: Post your opinion to the -dev thread "A few questions to 
our nominees" 2+ hours before the meeting.

\begin{itemize}
 \item 
 \agoref{gentoo-dev}{c6e4ba8293f50c1e0444e67d59cf85ea}
 \item
 \agoref{gentoo-dev}{05614741b3942bfdfb21fd8ebb7955e0}
\end{itemize}

Goal: Vote.

Result: lu_zero posted a second plan 12 hours ago. Since it hasn't been 
around long enough to get much feedback, we decided to let them develop 
and see if the ideas somehow merge.


\agendaitem{GLEP 55}
\index{GLEP!55}\index{EAPI suffix}

Preparation: Post your opinion to the -dev thread "GLEP 55" 2+ hours 
before the meeting. Let it attempt to come to a consensus before we 
vote.

\agoref{gentoo-dev}{c6e4ba8293f50c1e0444e67d59cf85ea}

Goal: Vote once the discussion's 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}

Preparation: Post your opinion to the -dev thread "[GLEP56] USE flag 
descriptions in metadata" 2+ hours before the meeting. Let it attempt to 
come to a consensus before we vote.

\agoref{gentoo-dev}{54ee20d2b1d8122370afdd4b3d7aafc9}

Goal: Vote once the discussion's no longer clearly ongoing. We can hold 
this vote on the -council mailing list instead of waiting for the next 
meeting.

There is still room for improvement in this GLEP, 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.


\agendaitem{Status of PMS}
\index{PMS}

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.

Preparation: Post your opinion to the -dev thread "One-Day Gentoo 
Council Reminder for June" 2+ hours before the meeting.

\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.