17:58:46 #startmeeting 17:58:46 Meeting started Mon Jul 27 17:58:46 2020 UTC. The chair is nattie. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:58:46 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:59:04 #topic roll call 17:59:09 hi 17:59:14 as ever, holler if you're there 17:59:26 o/ 17:59:34 \o 17:59:49 hello 18:00:17 small meeting so far... 18:01:07 #onlythededicated :) 18:01:23 well, we might as well press on, then 18:01:31 #topic last week's actions 18:01:46 looks like Aigars is happy to receive pictures by mail, so yay 18:02:16 and i've got what feels like seven billion shipping addresses, so also yay 18:02:30 #topic registration update 18:02:55 #info the deadline to register for t-shirts has passed 18:03:25 and we have a little over 400 people registered so far 18:03:30 #popular 18:03:47 #link https://debconf20.debconf.org/register/statistics/ 18:03:58 #topic content team update 18:04:01 o/ 18:04:20 any news from content? 18:05:10 I cannot produce any 18:05:22 (I was mostly unavailable the past couple of weeks) 18:05:49 FWIW, we have 85 proposed talks in total 18:05:50 80 talk submissions so far 18:06:02 We have been receiving some talks for the language-specific miniconfs 18:06:06 5 of those are canceled or withdrawn :-) 18:06:13 DLange: good poiint :) 18:06:19 I know :D 18:06:29 modest as always 18:06:37 looks like submissions are being reviewed 18:07:09 We have reviewed most, if not all... And last I remember the discussions in the -content channel, basically we have space to schedule everything 18:07:17 ...but building a schedule will be a tough task IMO 18:07:48 We are aiming at a single-track DebConf, as requested/agreed with video team 18:08:16 so the language-specific tracks will happen within the single track? 18:08:18 _but_ language-specific miniconfs will probably break this rule (and... they will need to providepeople to do the videoteam work) 18:08:21 ah 18:08:52 which is... well, again, don't take me as authoritative, I have been mostly AFK 18:09:54 anything else for content? 18:10:09 #topic t-shirts 18:10:09 * gwolf shuts up 18:10:40 the deadline was midnight UTC just gone, and we have many people wanting t-shirts 18:11:14 which ... kinda was to be expected :) 18:11:36 do we have a final design? 18:11:36 there are some localised printing efforts, and we're dividing up the ordering and distribution between those 18:11:44 (like with a fixed back etc.) 18:11:59 we need to decide between monochrome and diversity, the back is very simple 18:12:26 yeah, but it words the wrong way around last time tumbleweed and me looked together 18:12:41 that can easily be fixed 18:13:02 i have fixed here https://salsa.debian.org/lenharo/drafts/-/blob/lenharo/DC20/tshirt_diversity.svg 18:13:14 good, whoever sends the final order to the printer needs to be aware 18:13:22 yep, we'll make sure of that 18:13:54 lenharo: Debian *Developers* conference not Development 18:14:18 we'll get it sorted, fear not 18:14:31 you can say Developers' (correct) or Developers (looks nicer) 18:14:36 ops, typo error. easy to fix. 18:14:39 lenharo: let's get that into the team repo 18:14:47 need commit access? probably... 18:14:51 and reviewed before sending to the printer please 18:15:08 I know this is all easy but mistakes happen and more eyeballs are better in this 18:15:09 i tried, no access :( 18:15:17 that can be changed 18:15:28 what's your salsa username? 18:15:35 lenharo 18:15:48 looks lik eyou have access 18:16:33 you're looking at the wrong repo, tumbleweed 18:16:48 no, he has access via /public 18:17:21 o.k., now he has direct access, too 18:17:42 Thanks! 18:18:07 ls 18:18:37 so, are the shirts green? 18:19:09 not to my knowledge 18:19:41 green as in "go" or green as in color? :) 18:19:48 good pivot 18:19:48 (sorry people I got distracted as I hurt me finger and was going after a bandaid) 18:19:52 what needs to happen next? 18:20:12 we're placing orders imminently 18:20:36 ... should team-specific shirts be added to this? 18:20:51 team shirts, would certainly be good 18:20:54 Or are we foregoing(sp?) the traditional video- and staff- 18:21:20 FWIW I think we could live with the simplified reality of not having to deal with extra ones ;-) (but that's just me) 18:21:29 yeah, we certainly don't need them 18:21:43 they'd be nice to have, but i'm not pushing very hard for them 18:21:49 we can't give them out in exchange for volunteering, because the shipping will be done before the conference 18:22:06 so, the best that can happen is extra shirts for *us* 18:22:08 i can check to see if our suppliers have the capacity to do some in another colour, i guess? 18:22:11 (thought about this because... well, if we don't know whether the shirt background is green, I guess we also don't know the shirt background for staff and video) 18:23:13 I think One Shirt to Rule Them All is fine 18:23:34 yeah, +1 18:23:37 nattie: you said you're expecting a deposit 18:23:47 (expecting the supplier to want a deposit) 18:24:07 yes, i will find out from the supplier what percentage they want in advance 18:24:15 and get an invoice to get that rolling 18:24:18 yep 18:24:30 any idea what the timeframe is after that? 18:24:35 are they ready to print? 18:25:40 pretty much, yes 18:25:47 they're just waiting for my official go 18:26:13 and I guess the other printings will all be on their own pace. Same process applies, we'll try to get them all out of the same budget 18:26:27 I think One Shirt to Rule Them All is fine <- +1 18:27:19 that's all i've got on t-shirts now 18:27:23 #topic budget 18:27:28 it's been approved! 18:27:28 I know we don't tend to decide like this... but could we do a show of hands? 18:27:34 anything else to add? 18:27:35 Wait, still for shirts 18:27:45 #undo 18:27:45 Removing item from minutes: 18:27:53 Does anybody feel we have to push for >1 shirt per person if deserved? 18:28:04 BTW: just throwing an idea: masks 18:28:09 * gwolf +1s one-shirt-to-rule-them-all 18:28:17 * nattie is for just one t-shirt 18:28:21 dunno about you, but I have like 10x more t-shirts than I really need 18:28:33 tumbleweed: I feel your pain... :-] 18:28:50 so, we have to decide before placing the order. 18:29:15 I don't think we should be inventing new stuff that requires logistics at this point 18:29:16 tzafrir: Sounds like a sweet idea, but it has to be looked deep into (don't know if our shirt provider can also provide facemasks) 18:29:21 We (IL) will probably print masks for local consumption. If anybody wants some: we can send those, but we can't handle delivery logistics. 18:29:24 terceiro: precisely 18:30:02 yeah, the primary t-shirt supplier can't do masks, so masks aren't happening there 18:30:06 i think we more or less have consensus not to bother with orga/video shirts this year 18:30:07 tzafrir: keep one for me. Pickup in 2021 :) 18:30:11 So... ① Only one shirt style will be printed 18:30:14 nattie: #agreed 18:30:23 +1 18:30:24 #agreed we will have only attendee t-shirts this year 18:30:24 ② No masks will be centrally produced 18:30:40 ok, I'm fine to proceed to cheer about budget 18:30:52 #topic budget 18:30:58 #info the budget as been approved 18:31:04 yay!!! \o/ 18:31:08 cheer \o/ (as requested :)) 18:31:13 woo yay! 18:31:14 heh 18:31:23 anything else on this matter? 18:31:36 well, highvoltage could just say "yes, but..." 18:31:48 so better move on! 18:31:57 #topic videoteam 18:32:12 not much to say, things plod forward 18:32:39 feeling confident, but there's still work to be done 18:32:39 tumbleweed: What do you suggest for logistics for people interested in language miniconfs? 18:32:50 Who should be the point of contact to be the videoteam trainee? 18:33:03 the video team could really use a volunteer wrangler to be that point of contact 18:33:13 doesn't seem like anyone in the team is stepping up to do that, atm 18:33:19 plan is still jitsi with PINs and a rtmp stream for everybody not talking? 18:33:49 plan is mostly prerecorded talks 18:34:00 jitsi for things that aren't, including Q&A, and BoFs 18:34:23 Not sure where we stand with PINs, we only just started touching the jitsi streaming bit this weekend 18:34:46 rtmp low-latency streams are available 18:34:51 lower-latency, I should say 18:35:27 I think DLange means PINs for the jitsi room(s)? 18:35:35 and, back to gwolf: It's still far too soon to train anyone, becuase we don't have the things to train them on, yet 18:35:41 terceiro: yes 18:35:42 terceiro: yeah, that's what I meant 18:36:05 aren't those trivial as jitsi has that builtin? 18:36:17 everything that touches jitsi has to be OK with them 18:36:22 yes, we just need to distribute the info 18:36:26 DLange: no 18:36:26 tumbleweed: Right. But I guess we (content) need to make sure that whoever is "pushing" language-specific has this need in head 18:36:28 not at all 18:36:32 in mind 18:36:35 Guadec did the same with their BBB instance and sent a mail every evening 18:36:39 the streaming infra couldn't support PINs which was why we didn't use them for mdco 18:36:53 that was a bit a pita as ... not everybody received them :o) 18:37:07 aaah 18:37:10 makes sense 18:37:12 we have hacky PIN support in the SIP to jitsi bridge 18:38:37 anything else? 18:38:56 gwolf: I think we've communicated that to everyone who has spoken to us so far (marga) 18:39:41 OK. Well, as for Spanish, I don't think we have done anything on that regard (but we will) 18:40:03 There is the other language from India (don't remember the name)...? 18:40:12 have they spoken to us yet? 18:40:15 yes 18:40:59 srud is leading that AFAICT 18:41:11 ah, cool 18:41:12 and they are aware of the need for video volunteers 18:41:27 in that case, that looks pretty promising 18:41:47 last call for video before i go to AoB 18:42:24 #topic AoB 18:42:33 next week, same time, same channel? 18:43:28 * gwolf +1s 18:43:33 yes! 18:43:46 #agreed next meeting 3 August, 18:00 UTC 18:43:53 anything else before i close? 18:44:02 yes 18:44:37 I missed the content part, sorry about that. just to let you know I will try to organize the team around starting with the schedule 18:44:44 . 18:44:58 cool 18:45:18 right, going once, twice... 18:45:22 #endmeeting