Gentoo Archives: gentoo-commits

From: "Jorge Manuel B. S. Vicetto (jmbsvicetto)" <jmbsvicetto@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/council/meeting-logs: 20110510.txt
Date: Wed, 11 May 2011 10:56:46
Message-Id: 20110511105635.9D07C20057@flycatcher.gentoo.org
1 jmbsvicetto 11/05/11 10:56:35
2
3 Added: 20110510.txt
4 Log:
5 Added log for the council 20110510 meeting.
6
7 Revision Changes Path
8 1.1 xml/htdocs/proj/en/council/meeting-logs/20110510.txt
9
10 file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/council/meeting-logs/20110510.txt?rev=1.1&view=markup
11 plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/council/meeting-logs/20110510.txt?rev=1.1&content-type=text/plain
12
13 Index: 20110510.txt
14 ===================================================================
15 19:02 <@Chainsaw> So, we meeting?
16 19:02 <@jmbsvicetto> scarabeus: are you chairing the meeting?
17 19:04 <@scarabeus> yeah
18 19:04 <@scarabeus> sorry i spent last 14 minutes getting to net
19 19:04 <@scarabeus> lemme open eveyrthing i need
20 19:05 <@scarabeus> i just opened lappy
21 19:06 <@scarabeus> ok
22 19:06 <@scarabeus> so we can start if nobody complains :)
23 19:06 <@scarabeus> but there is one thing only on the topic :)
24 19:06 <@scarabeus> so lets start with mandatory thingie
25 19:06 <@scarabeus> roll call:
26 19:07 * scarabeus obviously here
27 19:07 <@Chainsaw> Yes, here.
28 19:07 <@Chainsaw> Mr. Vicetto was here earlier.
29 19:07 <@Chainsaw> Even the kitten.
30 19:07 <@Chainsaw> Oh, and wired.
31 19:08 <@scarabeus> so we lack only Betelgeuse and ferringb
32 19:08 <@bonsaikitten> is here.
33 19:09 <@scarabeus> wired, jmbsvicetto: show up again ;)
34 19:09 * wired here
35 19:09 <@Chainsaw> Just beetlejuice then.
36 19:09 <@wired> lol
37 19:09 <@jmbsvicetto> sorry, here
38 19:10 <@scarabeus> ok
39 19:10 <@scarabeus> 5 is enough for the meeting
40 19:10 <@scarabeus> so lets rool i guess
41 19:10 <@scarabeus> or does anyone has phone on those two?
42 19:11 <@Chainsaw> jmbsvicetto usually calls me. He's very good about that.
43 19:11 <@jmbsvicetto> I'll poke Betelgeuse and ferringb
44 19:11 <@scarabeus> Chainsaw: yeah he is great and responsible person
45 19:12 <@scarabeus> Chainsaw: i still dont understand how the kde people could trust me to be next in the row for the kde team lead :)
46 19:12 <@Betelgeuse> hello
47 19:12 <@scarabeus> so thats six :)
48 19:12 <@Betelgeuse> I always forget if there's no alarm.
49 19:12 <@Betelgeuse> At least jmbsvicetto is a good one :)
50 19:13 <@jmbsvicetto> I got voice mail for ferringb
51 19:13 <@scarabeus> ok so lets roll
52 19:13 <@scarabeus> this months agenda is just one item
53 19:13 <@jmbsvicetto> I'll leave him a message
54 19:13 <@scarabeus> http://archives.gentoo.org/gentoo-dev-announce/msg_4032405a712196c9f18f29aaf8f54d72.xml
55 19:13 <@scarabeus> unless i miss some reply
56 19:13 <@scarabeus> (there was one about openrc news item but that is obsolete now)
57 19:14 <@scarabeus> so the issue we are speaking about is nice discussion on gentoo-dev
58 19:14 <@scarabeus> http://archives.gentoo.org/gentoo-dev/msg_eaefa325b31360324d0fe53d0b9071e6.xml
59 19:15 <@jmbsvicetto> is there anything for us to decide?
60 19:15 <@scarabeus> so the issue is that changelog is not used by some developers in certain cases, like package removals
61 19:16 -!- NeddySeagoon [~NeddySeag@gentoo/developer/NeddySeagoon] has joined #gentoo-council
62 19:16 <@Chainsaw> I strongly believe that a removal is a change, and as such belongs in a changelog.
63 19:16 <@Betelgeuse> And they claim that it's not required.
64 19:16 <@scarabeus> well technically i would just say that we want devmanual to state that changelogs must be used for all relevant changes expect typo and whitespace changes
65 19:16 <@jmbsvicetto> imho, we already have a policy. The "discussion" arises because some developers don't want to follow it
66 19:16 <@bonsaikitten> I prefer complete changelogs just so that I can see from the changelog why a removal happened
67 19:16 <@scarabeus> so it is explicit
68 19:16 <@scarabeus> and even the typo is questional
69 19:16 <@scarabeus> i personaly does not changelog only whitespace
70 19:16 <@scarabeus> eg trailing spaces removal
71 19:17 <@Betelgeuse> In theory you can break the ebuild with every change.
72 19:17 <@Chainsaw> Yes, there is a story behind a removal. It should be captured.
73 19:17 <@Chainsaw> In fixing a repoman warning, you can break the build.
74 19:17 <@Chainsaw> It would be nice to know who changed it and what their motivation was.
75 19:18 <@scarabeus> reverse dependencies can get broken with removal
76 19:18 <@scarabeus> so removals tracking in changelog is nice
77 19:19 <@Betelgeuse> How about voting on the strictest text: "All commits must be accompanied by ChangeLog entries" and if that doesn't pass then think how to relax it?
78 19:19 <@scarabeus> good idea
79 19:19 -!- kallamej [~kallamej@gentoo/developer/kallamej] has quit [Quit: bl2 here we go]
80 19:19 <@wired> i like that
81 19:20 <@jmbsvicetto> I'm ok with it
82 19:20 <@scarabeus> i agree with that too (in future commits will be changelogs so everything will be shown anyway)
83 19:20 <@bonsaikitten> Betelgeuse: "all" is too strict, changelog changes and whitespace fixes might not need changelog entries
84 19:21 < Arfrever> Why would commits of changes in never used code (e.g. inside 'if [[ ${PV} == 9999 ]]' block in non-live ebuild) be mentioned in ChangeLog?
85 19:21 <@scarabeus> because you alter the ebuild
86 19:22 <@Betelgeuse> So let's vote.
87 19:22 <@jmbsvicetto> Arfrever: you can always add an entry for the above stating that you're "syncing ebuild with live ebuild version"
88 19:23 <@ferringb> Arfrever: "house keeping" isn't a bad message...
89 19:23 <@Betelgeuse> I vote yes for the reason scarabeus stated.
90 19:23 <@wired> I vote yes
91 19:23 <@scarabeus> i vote yes
92 19:23 <@jmbsvicetto> yes
93 19:23 <@ferringb> pardon folk, mildly in a sate of "walking dead" today
94 19:23 <@ferringb> *state
95 19:23 <@scarabeus> ferringb: well you shown up for the only relevant part :) so just use yar powaz
96 19:24 < Arfrever> It doesn't make sense to mention changes not affecting any users of given ebuild.
97 19:24 <@ferringb> "yes for strictest"
98 19:24 <@bonsaikitten> I vote no on Betelgeuse's strict form, but agree with the general idea
99 19:24 <@Betelgeuse> Arfrever: We think otherwise.
100 19:24 <@Betelgeuse> You can never be sure any way.
101 19:25 <@Betelgeuse> Chainsaw: your vote
102 19:29 <@scarabeus> hm
103 19:29 -!- alexxy[home] [~alexxy@gentoo/developer/alexxy] has joined #gentoo-council
104 19:29 -!- ssuominen [~ssuominen@gentoo/developer/ssuominen] has joined #gentoo-council
105 19:30 <@scarabeus> ok we have 6 votes so we can consider it official
106 19:30 <@Betelgeuse> http://paste.pocoo.org/show/386527/
107 19:30 <@Betelgeuse> Please comment on this and I can push it if ok
108 19:31 <@scarabeus> ++
109 19:31 < Arfrever> Please vote on excluding changes only in comments.
110 19:31 <@ferringb> ';' instead of '-, but sure.
111 19:31 <@ferringb> Arfrever: it's a vcs log
112 19:31 -!- kallamej [~kallamej@gentoo/developer/kallamej] has joined #gentoo-council
113 19:31 <@ferringb> if you seriously think commiting w/ a message '.' in your local vcs when you screw with comments is fine...
114 19:31 <@ferringb> well, it's your local vcs
115 19:31 <@ferringb> it's not the tree
116 19:32 <@Betelgeuse> ferringb: semicolon where?
117 19:32 <@ferringb> Betelgeuse: 3rd line addition
118 19:32 <@ferringb> or whatever the appropriate english char may be
119 19:32 <@Betelgeuse> ferringb: that's the old text
120 19:32 <@Betelgeuse> ferringb: But I had to rewrap lines
121 19:32 <@Betelgeuse> ferringb: Only first sentence changed in content
122 19:32 <@ferringb> sure doesn't look it
123 19:33 -!- bloodnoc [~roy@gentoo/developer/NeddySeagoon] has joined #gentoo-council
124 19:33 < Philantrop> Next time you're going to discuss the meaning of "should". :-) I'd make it "must".
125 19:34 <@Betelgeuse> Philantrop: hmm true
126 19:34 <@Betelgeuse> That was in my text voted also
127 19:36 <@Betelgeuse> http://paste.pocoo.org/show/386531/
128 19:36 <@Betelgeuse> changed to must
129 19:37 <@ferringb> Arfrever: the kicker is, in certain cases, you're partally right.
130 19:37 <@ferringb> Arfrever: the reality is, people will just adhere to the letter of the law rather than the intent
131 19:37 <@ferringb> we already had that occur with removal
132 19:38 -!- darkside_ [~darkside@gentoo/developer/darkside] has joined #gentoo-council
133 19:38 <@ferringb> stupid that we have to essentially legislate common sense, but that's what it is right now ;)
134 19:39 < NeddySeagoon> ferringb, common sense is much rarer that you might think :)
135 19:39 <@ferringb> NeddySeagoon: well aware
136 19:39 <@Betelgeuse> http://paste.pocoo.org/show/386532/
137 19:41 <@scarabeus> i like the last update
138 19:42 <@Betelgeuse> The meeting summary could point to wrapping repoman commit and the ssh tunnels
139 19:42 <@Betelgeuse> Those should address the speed concerns raised
140 19:42 <@Betelgeuse> at least I have never had issues
141 19:43 <@Betelgeuse> I don't do things like KDE bumps though
142 19:44 <@scarabeus> Betelgeuse: how?
143 19:44 <@scarabeus> i just echangelog everything
144 19:44 < Arfrever> `cvs commit` is faster than `repoman commit`. When ChangeLog is not updated during commit of deletions, then no CVS headers are changed and it's possible to commit changes in Manifest in the same commit as deletions of ebuilds.
145 19:44 <@scarabeus> and then category-commit it
146 19:45 <@jmbsvicetto> Arfrever: that argument isn't imho a valid argument for stop using repoman commit (cvs speed)
147 19:45 <@Betelgeuse> scarabeus: Like I said I don't do those category wide commits :)
148 19:46 <@jmbsvicetto> Arfrever: that is a good argument to get people working on replacements for cvs and or improving the QA scripts
149 19:46 <@Betelgeuse> scarabeus: I use http://paste.pocoo.org/show/386533/
150 19:46 <@jmbsvicetto> Betelgeuse: they can be very "stressing"
151 19:46 <@Betelgeuse> scarabeus: to dig what I just told echangelog
152 19:47 < Arfrever> jmbsvicetto: repoman wastes time on scanning other ebuilds not updated during committing.
153 19:47 <@ferringb> Arfrever: that's not true.
154 19:47 <@jmbsvicetto> last time I tried to do one for KDE I had to give up as my laptop just wasn't able to keep up with it
155 19:47 <@ferringb> Arfrever: note the headers in ebuilds.
156 19:47 <@ferringb> Arfrever: or headers in any other file frankly, that was modified.
157 19:47 < Arfrever> ferringb: I meant commits of only deletions of ebuilds + change in Manifest.
158 19:47 <@ferringb> Arfrever: those change, chksum changes, meaning double commit for manifest
159 19:47 <+dberkholz> repoman takes like 10 seconds, this isn't a big issue
160 19:47 <@ferringb> dberkholz: exactly.
161 19:47 <@jmbsvicetto> and that's one reason I'd really would like to have git by now. People have to work on that, though
162 19:48 <@ferringb> Arfrever: if you're going to complain about speed, complain about echangelog.
163 19:48 <@ferringb> repoman commit's speed really isn't a point you can complain about
164 19:48 <@Chainsaw> Sorry for the delay.
165 19:48 <@Betelgeuse> Seems there's no objections to my latest devmanual patch so I'll push that in a couple minutes.
166 19:48 <@Chainsaw> I am for the strict beetlejuice version. Yes.
167 19:49 <@ferringb> beetlejuice beetlejuice beetlejuice!
168 19:49 * ferringb wanders off to deal with the sand worms
169 19:49 <@Chainsaw> ferringb: Walk without rhythm.
170 19:50 <@ferringb> Chainsaw: or walk as if you were a desert mouse
171 19:50 <@ferringb> Chainsaw: was referencing the more comical version of sand worms also ;)
172 19:50 <@ferringb> Betelgeuse: honestly, no idea why I've not made that joke about your nick yet. ;)
173 19:51 <@scarabeus> ok so we have conclusion on this issue i suppose guys :)
174 19:52 < Arfrever> The patch for devmanual doesn't disallow `ln -fs /bin/true /usr/bin/echangelog` :) .
175 19:52 <@Betelgeuse> Arfrever: Sure but I bet QA/DevRel can come up with something
176 19:53 <@Betelgeuse> Arfrever: That doesn't end up updating ChangeLog
177 19:53 <@scarabeus> so next on list is bugs, where there is no change since last month i suppose
178 19:54 <@scarabeus> and the last thing on the list is the open floor and other topics brought by other members
179 19:54 <@scarabeus> so anyone anything?
180 19:54 <@Betelgeuse> jbartosik was supposed to be here for the council web app
181 19:54 <@scarabeus> Betelgeuse: btw would you mind open bug with attached changelog? or just commit it directly, if you have no access just tell infra to allow developers group to touch devmanual
182 19:54 <@Chainsaw> scarabeus: Nothing further your honour.
183 19:55 <@Betelgeuse> scarabeus: I have push access and it's already in
184 19:55 <@Betelgeuse> Any way we set a goal that we have something usable live for the meeting next month
185 19:55 <@scarabeus> Chainsaw: does that mean that i have to wear those silly white hair now?
186 19:55 < Arfrever> Also echangelog is known to break lines after very short limit. It should be changed to at least 144 :) .
187 19:55 <@Chainsaw> scarabeus: Look in a mirror. You already are!
188 19:55 <@Betelgeuse> Arfrever: You can open threads on mailing lists for that
189 19:55 <@ferringb> Arfrever: ml.
190 19:56 <@ferringb> this isn't going to be dissuaded by arguments about the tools potentially sucking
191 19:56 <@ferringb> fix the tools
192 19:56 <@Betelgeuse> If anyone wants access the Agilefant instance to track progress please query
193 19:56 <@scarabeus> i can wait for public preview :)
194 19:56 <@scarabeus> hope it is going well :)
195 19:57 <+dberkholz> Arfrever: stop breaking my terminals, they're only 80 wide.
196 19:57 <@Betelgeuse> scarabeus: GSoC hasn't officially started yet :)
197 19:58 <@Betelgeuse> scarabeus: the coding period any way but we started early
198 19:58 < Arfrever> dberkholz: You should switch to better terminals.
199 19:58 * ferringb should level the +m if arguing over decisions continues
200 19:58 <@ferringb> and yes, I'm an ass.
201 19:59 <@ferringb> think my point is made however.
202 19:59 <@Betelgeuse> Did you notice qiaomuf's blog post about libbash?
203 19:59 * bonsaikitten waits for ferringb to get stabby
204 20:00 <@ferringb> bonsaikitten: day's starting off that way. one hopes it becomes more xen like before the folks I have to interview later today ;)
205 20:00 * scarabeus throws his knife
206 20:00 <@bonsaikitten> zen I hope
207 20:00 <@ferringb> zen even.
208 20:00 <@scarabeus> here borrow this ;)
209 20:00 <@jmbsvicetto> ferringb: hopefully zen ;)
210 20:00 <@scarabeus> ok so i guess thats it
211 20:00 <@ferringb> xen from the stance of cutting a release in between interviewing. ;)
212 20:00 <@jmbsvicetto> scarabeus: ok, quick note
213 20:00 <@ferringb> either way
214 20:01 <@scarabeus> jmbsvicetto: hm?
215 20:01 <@jmbsvicetto> I've finally sent an email about the arch teams to the project ml right before the meeting started
216 20:01 <@scarabeus> :)
217 20:01 <@scarabeus> i see i see
218 20:01 <@jmbsvicetto> and I'm about to send an email about the automatic testing
219 20:01 <@scarabeus> so now for the next meeting :) 7.6. 19:00 UTC and who is willing to chair? :)
220 20:01 <@jmbsvicetto> so let's see if anything comes out from that
221 20:02 <@jmbsvicetto> are we back to Tuesdays or do we want to do it another day of the week?
222 20:02 <@Betelgeuse> scarabeus: time works for me
223 20:02 < Arfrever> scarabeus: Do you mean 2011-07-06?
224 20:02 <@jmbsvicetto> I can do Tuesdays
225 20:02 <@ferringb> 19:00 really is sucking ass for me
226 20:02 <@Betelgeuse> Arfrever: context tells it's June
227 20:02 <@jmbsvicetto> 2001-06-07
228 20:02 < Arfrever> jmbsvicetto: It was in the past :) .
229 20:02 <@ferringb> admittedly, 20:00 isn't always great either. 22:00 is the sweet spot for me, but I suspect horrible for the rest of y'all
230 20:03 <@Chainsaw> I can do Tuesdays, but not the first Tuesday of the month.
231 20:03 <@Chainsaw> That's the LUG meeting. Second Tuesday is totally fine though.
232 20:03 <@ferringb> can't do mondays, tuesdays is viable, but wednesday is better
233 20:03 <@ferringb> then thurs/fri start getting crazy. ;)
234 20:03 <@scarabeus> so lets do it on wed
235 20:03 <@Chainsaw> And if 22:00 is better for you, I can do that.
236 20:03 <@Betelgeuse> ferringb: 22UTC starts at 1am
237 20:03 <@scarabeus> it is option stuf
238 20:03 <@ferringb> Betelgeuse: I got up at 5-6am on a saturday for one of these.
239 20:03 <@ferringb> Betelgeuse: recall, I'm still trying to make y'all get up at a crazy hour in retaliation ;)
240 20:04 <@ferringb> wednesday at 19 is fine
241 20:04 <@Betelgeuse> ferringb: yes but maybe we can find a time that suits everyone :)
242 20:04 <@ferringb> it's basically the "ok, fires are out" before the new fires start
243 20:05 <@ferringb> Betelgeuse: early morn hours are what I've had for dealing w/ europe, but I've got meetings in the morning.
244 20:05 <@ferringb> my schedule sucks, is the short version.
245 20:05 <@Betelgeuse> Next meeting is the last one isn't it?
246 20:05 <@ferringb> will adapt to y'alls since currently, you outnumber the usians anyways. ;)
247 20:05 <@Chainsaw> Betelgeuse: Until the end of the world? That's 2012 isn't it?
248 20:06 <@Betelgeuse> ferringb: better luck for the next election round :)
249 20:06 <@Betelgeuse> Chainsaw: for our term
250 20:06 <@ferringb> heh
251 20:06 -!- darkside_ [~darkside@gentoo/developer/darkside] has left #gentoo-council []
252 20:06 <@Chainsaw> Betelgeuse: Oh right.
253 20:07 <@Betelgeuse> jmbsvicetto: Do you remember the election timetable?
254 20:07 < NeddySeagoon> the nomination peropd should have started then. Is that elections slacking again :)
255 20:08 <@Chainsaw> Can I buy my TV commercials & news articles yet?
256 20:08 <@Betelgeuse> NeddySeagoon: I think the elections take about a month so there's still time before July
257 20:09 < NeddySeagoon> Betelgeuse, I thought it was a month each for nomintions and votes ... maybe my memory is fading with age
258 20:10 <@ferringb> my memory concurs
259 20:10 <@jmbsvicetto> iirc, the election takes place on July and the new council will take office in August
260 20:10 <@ferringb> yep
261 20:10 <@Betelgeuse> NeddySeagoon: the timeline has probably fluctuated but I'll leave that to the elections team
262 20:10 <@Chainsaw> jmbsvicetto: Will we get new chairs?
263 20:10 <@jmbsvicetto> NeddySeagoon: no, 15 days each for council (nomination and voting)
264 20:10 <@ferringb> huh
265 20:10 <@ferringb> either way
266 20:10 <@jmbsvicetto> NeddySeagoon: the foundation is the one taking 1 month for each
267 20:10 <@Betelgeuse> jmbsvicetto: Our first meeting is marked for July 14, 2010 for some reason
268 20:11 <@jmbsvicetto> Chainsaw: hehe
269 20:11 <@jmbsvicetto> Betelgeuse: ok, then my memory is "skewed"
270 20:11 <@jmbsvicetto> I'll check the election schedule this week and will report it
271 20:12 <@scarabeus> ok guys i have to disappear :)
272 20:12 <@scarabeus> find next meeting chair and date, i am fine with everything :)
273 20:12 -!- alexxy[home] [~alexxy@gentoo/developer/alexxy] has quit [Remote host closed the connection]
274 20:12 <@Betelgeuse> I propose we start 5mins from now
275 20:12 <@scarabeus> and if anyone of you mail me log i will create proper summary and commit during this week
276 20:12 <@Chainsaw> Not the first Tuesday of the month.
277 20:12 <@scarabeus> Betelgeuse: xD
278 20:12 <@Chainsaw> Not a Friday/Saturday/Sunday.
279 20:13 <@Chainsaw> Any other day/time, I'll move stuff to make it work.
280 20:13 <@Betelgeuse> 2011-06-14 19UTC?
281 20:13 <@Betelgeuse> Or 06-15 as it was better to ferringb
282 20:13 <@Chainsaw> Either works for me.
283 20:13 <@jmbsvicetto> I can be the chair for next meeting
284 20:14 <@Chainsaw> That would be most appreciated.
285 20:14 <@ferringb> eenie meenie
286 20:14 <@ferringb> honestly my schedule just @!#*ing sucks
287 20:14 <@ferringb> all days exempting weekend aren't great
288 20:14 <@ferringb> wedn. is my preference, but it's not a hard req
289 20:15 <@Betelgeuse> wired: time preferences?
290 20:15 <@jmbsvicetto> So, 20110604 (Saturday) or 20110614 (Tuesday): what do you pick?
291 20:15 <@Betelgeuse> jmbsvicetto: 0615?
292 20:15 <@jmbsvicetto> sorry, 20110615 (Wednesday)
293 20:15 <@ferringb> err
294 20:15 <@wired> i prefer wednesday
295 20:15 <@ferringb> crap. forgot. 10-20 I'm moving.
296 20:16 <@wired> any time after 1800 utc
297 20:16 <@ferringb> specifically will be driving through redwood forests sometime on the 15th. :)
298 20:16 <@ferringb> week prior being my preference
299 20:16 <@ferringb> else I'll just have to send a proxy
300 20:16 <@jmbsvicetto> next attempt: 20110604 (Saturday) or 20110608 (Wednesday)
301 20:16 <@ferringb> 08. :)
302 20:16 <@wired> 08 +1
303 20:16 <@ferringb> <-- work beckons
304 20:17 <@jmbsvicetto> Wednesday - 1900 UTC
305 20:17 <@Betelgeuse> 08 ok
306 20:17 <@jmbsvicetto> Betelgeuse / bonsaikitten / Chainsaw / ferringb / scarabeus / wired: 20110608 1900 UTC, is that ok for you?
307 20:17 <@ferringb> yes
308 20:18 <@Betelgeuse> yes
309 20:18 <@bonsaikitten> yes
310 20:18 <@Chainsaw> jmbsvicetto: Yes.
311 20:19 <@wired> yes
312 20:19 <@Chainsaw> Consensus!
313 20:20 <@jmbsvicetto> we're missing scarabeus
314 20:20 <@Betelgeuse> 20:12 <@scarabeus> find next meeting chair and date, i am fine with everything :)
315 20:20 <@Chainsaw> Summary: Yes.
316 20:20 <@jmbsvicetto> ok, then we're settled :)
317 20:20 <@jmbsvicetto> Thanks everyone
318 20:21 * Chainsaw bows and leaves the room
319 20:21 <@Betelgeuse> is summary done?
320 20:21 -!- jmbsvicetto changed the topic of #gentoo-council to: Next meeting: 20110608 1900UTC | http://www.gentoo.org/proj/en/council/utctolocal.html?time=1900 | http://www.gentoo.org/proj/en/council/
321 20:21 <@jmbsvicetto> Betelgeuse: scarabeus promised to do it soon
322 20:22 -!- Chainsaw [~chainsaw@gentoo/developer/atheme.member.chainsaw] has quit [Quit: Leaving]
323 20:22 <@jmbsvicetto> wired: mail about automatic testing finally sent to the mls
324 20:22 <@Betelgeuse> 20:12 <@scarabeus> and if anyone of you mail me log i will create proper summary and commit during this week
325 20:22 <@jmbsvicetto> oh, ok
326 20:22 <@Betelgeuse> Someone needs to commit the log
327 20:22 <@jmbsvicetto> I'll take care of the log later today
328 20:23 -!- alexxy [~alexxy@gentoo/developer/alexxy] has joined #gentoo-council
329 20:23 <@jmbsvicetto> Let's close this meeting then
330 20:23 -!- alexxy [~alexxy@gentoo/developer/alexxy] has quit [Remote host closed the connection]
331 20:23 <@Betelgeuse> thanks
332 20:23 <@jmbsvicetto> If anyone wishes to call the council attention to any issue, please do so