17:59:16 #startmeeting 17:59:16 Meeting started Mon Aug 10 17:59:16 2020 UTC. The chair is nattie. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:59:16 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:59:24 tumbleweed: did i tell you to say hi yet? 17:59:36 #link agenda, as ever, at https://deb.li/dc20meet 17:59:39 hi if you are here 17:59:42 no :( 17:59:47 #topic roll call 17:59:48 do the holler 17:59:55 hi!! \o/ 17:59:56 ahoy 17:59:59 do the shuffle 18:00:08 \o\ 18:00:34 #topic schedule 18:00:39 it's been released! 18:01:04 yeah! 18:01:14 #info the schedule is released! 18:01:14 awesome work terceiro and the content team 18:01:17 Great work from content team! 18:01:23 schedule is up, announced went out as well 18:01:29 three cheers for content! 18:01:31 o/ 18:01:34 the spanish track is supposed to be ready RSN 18:01:35 on that topic, terceiro a small MR for you: https://salsa.debian.org/debconf-team/public/websites/dc20/-/merge_requests/79 18:01:43 nattie: modulo some bits we Spanish-speakers still owe... 18:01:45 tumbleweed: yes, I will go over that ASAP 18:01:54 (highlighting nattie because of the #info) 18:02:08 #info the spanish track is nearly ready 18:02:11 there are also a few empty slots, and we got 2 requests for late submissions so far, and I told them to go ahead and submit 18:02:20 (both good stuff) 18:03:06 sounds good! 18:03:16 #topic process for AH and CoC 18:03:24 this sounds like a big topic 18:03:34 terceiro: MySQL ponders sending another speaker for European timings. Just FYI. 18:03:43 (they told me today) 18:03:56 DLange: that's probably one of the late submissions 18:04:05 that we already know about 18:04:09 aah, that would be awesome 18:04:10 o/ sorry I am late 18:04:11 #undo 18:04:11 Removing item from minutes: 18:04:15 terceiro: IIRC it was not (I have two others on my mind) 18:04:32 but anyway, you are much more over the issue than me! 18:04:37 gwolf: yeah? anyway, we've got space, so let them come 18:04:43 anisa: no worries, you just missed the dance party 18:04:43 good 18:05:14 ready for the next topic? 18:05:38 we should say yes and cause you to #undo regardless :) 18:05:41 let's move forward 18:05:55 #link https://debconf20.debconf.org/schedule/ 18:05:58 just for good measure 18:06:03 ah 18:06:07 #topic process for AH and CoC 18:06:32 thoughts? 18:07:21 we should have one™ :) 18:07:45 well, yes 18:07:46 do we know who from the community team plans to attend? 18:08:08 do they have a "on call" schedule or so? Should we ask for one? 18:08:28 i can see at least one person on the list who's attending 18:08:34 I'm there 18:08:56 FWIW one of the late submissions we are accepting is mollydb's 18:09:02 and of course, srud__ is here :-] 18:09:21 I hope sledge will attend too, he's really a DC regular 18:09:23 And others are also willing to be there.. 18:09:50 will we have people with the right IRC permissions? 18:09:55 We first need to have a proper procedure set up for incidents 18:10:10 terceiro: so, all of the debconf committee members have IRC ops powers in debconf channels 18:10:15 ah 18:10:16 and the usual debian IRC ops do too 18:10:17 cool 18:10:20 srud__: does that procedure fall in the hands of Community Team or in DebConf Orga? 18:11:46 gwolf: we need to discuss.. I think mollydb sent a mail sometime back.. But was not followed up I think 18:12:01 We can initiate a discussion.. 18:12:11 srud__: Could we then... leave the #action on your side for this, and continue? 18:12:23 (or does people think I'm too pushy with this, as close to the conf as we are?) 18:12:48 I don't think we can come up with a plan during the meeting, #action is probably the best we can do atm 18:13:04 gwolf: I will discuss there and send a mail to dc-committee may be? 18:13:06 #action srud__ to investigate the procedure for incidents for the community team 18:13:08 ack. May be as part of this, srud__, could you ask whether the community team would be willing to assign "on call / duty" days for yourselves? 18:13:29 DLange: sure 18:13:37 cool, thanks! 18:13:50 ready for the next one? 18:14:02 #topic bursary status 18:14:40 I put the info into the agenda, shall I paste? 18:14:41 #info out of 14 bursary requests, 11 recipients have done the necessary steps, and first payments are already going out 18:14:48 thanks nattie :o) 18:15:02 any more details, or is that good? 18:15:24 #topic fundraising status 18:15:25 if anybody has questions pls ask, otherwise I just wanted to give a status 18:15:33 and you get to give another one! 18:15:47 I sense a pattern :) 18:16:06 nattie: please make my babble nice English again and #info it 18:16:21 'cause you add value even to pastes! 18:16:27 oh, the pressure 18:17:04 commas 18:17:23 #info two contracts are pending, most invoices are paid (except two for Debian Switzerland) 18:17:31 that's the very short version 18:17:47 thanks! 18:17:51 never sure whether to include full details in the #info bits 18:17:58 #topic AoB 18:18:04 seems perfect 18:18:23 anything we should know about? 18:18:33 shirt status? 18:18:48 it seems I'll be able to get mine this week ;-) 18:18:54 all fine for the FreeWear order 18:18:54 :) 18:19:04 any idea when they start shipping? 18:19:09 (despite some attendees not supplying a phone number, but that's been dealt with) 18:19:33 i'll check with them! 18:19:36 I start to send today shirts. 18:20:05 nattie: Why does a T-shirt depend on a phone number? 18:20:12 gwolf: shipping 18:20:16 lenharo: are you going to invoice debconf for the shirts you got printed? 18:20:20 * gwolf repeats question 18:20:36 gwolf: the shipping company demanded it apparently 18:20:48 nattie: I understand the S&H people might like to chat with me... But they never take the opportunity to do so 18:20:50 gwolf: because delivery companies like to have the ability to phone a recipient when they need to deliver a package 18:20:52 tumbleweed, yes. 18:21:20 good, that was a reminder :) 18:21:25 gwolf: it's just mandatory in some shipping companies and for customs 18:21:33 anyway, that only applies to some of the recipients in this case 18:22:58 anything else to do but set the date for the next one? 18:23:18 nothing from my side 18:23:20 oh my, next week is the 17th already! 18:23:43 time sure flies 18:23:56 everyone good for then? same time, same channel, etc? 18:24:17 Ok 18:24:19 #agreed next meeting 17 August, 18:00 UTC 18:24:25 last orders... 18:24:34 #endmeeting