17:58:19 #startmeeting 17:58:19 Meeting started Tue Dec 1 17:58:19 2020 UTC. The chair is olasd. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:58:19 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:58:27 #addchair tumbleweed 17:58:31 #chair tumbleweed 17:58:31 Current chairs: olasd tumbleweed 17:58:36 better 17:58:36 ohai 17:58:41 #topic Roll Call 17:58:51 hi 17:58:54 #link Agenda http://deb.li/oNCD 17:58:58 hello o/ 17:59:05 (will that work? who knows!) 17:59:07 0/ 17:59:40 any paddatrapper or highvoltage s around? 17:59:46 woo, people from both .br and .in minis 18:00:05 hi 18:00:07 br-in-g them in! 18:00:10 * pollo hides 18:00:19 har har 18:00:24 what's g? 18:00:32 * nattie extracts the pun tax from pollo 18:00:46 g = global or germany? 18:00:54 global then 18:01:10 pollo: one jar of preserved tomatoes, please! 18:01:23 alright, I guess that's all of us 18:01:25 highvoltage is around but working 18:01:32 ah, I just had to ask :P 18:01:36 #topic 2.1. mdcobr2020 - Video encoding check-in 18:01:53 all done, I think 18:01:55 oh yeah, i'm hereish, in my usual way 18:01:59 I forgot, yet again, to swich LQ to VP9... 18:02:10 but meh, don't think it's crucial 18:02:16 I'll try to not forget before the .in one ;) 18:02:16 terceiro: you probably want to import video links to th esite 18:02:18 it did sound that way; is there a final review expected? 18:02:25 olasd: done 18:02:27 great 18:02:31 pollo: are we going to do an etherpad export again? 18:02:34 (did they even use etherpad) 18:02:38 #info All encodings done, and a final review happened 18:02:44 tumbleweed: for? 18:02:45 tumbleweed: yes, I will 18:02:51 pollo: .br mini 18:02:55 ah, yes etherpad export, sorry 18:02:58 #action terceiro to import video links to the website 18:03:05 #action pollo to export the BR etherpads 18:03:22 anything else for this topic? 18:03:38 tumbleweed: did you do that for mdco games? 18:03:46 (otherwise I can do it at the same time) 18:04:21 terceiro: yes 18:04:29 cool 18:04:30 although the games one had to deal with weird data issues that you won't have to 18:04:40 k 18:04:49 alright 18:04:52 #topic 2.2. mdcobr2020 - Feedback 18:05:01 I think things went well? 18:05:05 they did 18:05:07 I've seen happy organizers, at least :-) 18:05:14 yes, it was very nive 18:05:15 nice 18:05:20 #info Things went well overall 18:05:25 didn't see any fires, we never got called in to fix anything 18:05:27 there were some hiccups, but mostly caused by speakers not listening to advice 18:05:39 yes, very few pre-recorded videos 18:05:45 terceiro: can you summarize them? 18:05:48 and some firefox 18:05:53 perhaps it's something we might be able to work on? 18:05:57 speaker with flaky internet connection 18:06:02 ... then again, perhaps not :) 18:06:02 speaker without a proper mic 18:06:13 did y'all have test calls? 18:06:15 it's mostly a matter of being more on top of them 18:06:18 right 18:06:38 it might be useful if we had a low-speed Internet option for people to join the conference 18:06:43 just 2 pre-recorded videos 18:06:43 we have 18:06:44 but I'm not sure that's possible 18:06:51 oh 18:06:51 wouter: there's a phone option in jitsi 18:06:57 * wouter goes quiet 18:07:00 #info Some issues were caused by presenters not following the advice, e.g. poor quality of internet connection or bad microphone 18:07:08 pollo: not what I meant, but okay 18:07:20 not sure what you mean then 18:07:29 we have low-res streams too 18:07:30 i believe it's a good idea add a warning on the doc for more than one jitsi room sending streaming to vogol 18:07:54 pollo: nvm, I'm actually not sure myself :) 18:08:16 phls: what was the issue there? were they fighting each other? 18:08:17 video conference requires bandwidth, we're not magicians, I shouldn't have said anything 18:09:07 IMO it's unreasonable to expect someone to present at an online conf without having a minimally decent internet connection 18:09:35 tumbleweed, no, because I asked here first what could happen if we do that 18:09:50 terceiro: live, definitely; but uploading slides somewhere and talking over them on mumble could work 18:09:51 terceiro: well, pre-recorded videos + phone Q&A would certainly be an option 18:10:29 I mean, there's a few options for low-bandwidth live talks that /could/ be explored if the need is present (I'm not sure it actually is) 18:10:33 sure 18:10:51 Sorry, I've had irl commitments tonight. Not going to be around for the meeting 18:10:55 my point is we should not optimize for that 18:11:09 yeah, definitely 18:12:28 tempted to "#info We could give clearer advice to organizers for what happens when multiple Jitsi rooms try to stream to the same vogol" but I'm not sure that's what you meant, phls 18:12:48 (and then I'm not sure where and how) 18:12:56 I also don't actually know what would happen 18:13:00 I'd have to try it out to see 18:13:11 IIRC at dc20, it'd just kick the old one out, which seems fine 18:13:14 the advice should be "don't" 18:13:14 should I #action you? 18:13:23 #info there were some issues with speakers not following advice and having bad equipment/internet connections, but these were minor overall 18:13:24 terceiro: err, in that scenario, it seems fine 18:13:34 wouter: I already did that, I think 18:13:42 #undo 18:13:44 yes, you did 18:13:55 but apparently I can't undo -- tumbleweed, could you do that for me? ;) 18:14:02 you can't #info either 18:14:04 so that's fine 18:14:05 tumbleweed: I think they flicker in and out, alternating, until one dies 18:14:22 olasd: the docs say #info is for everyone 18:14:24 oh, hah 18:14:28 ah, interesting 18:14:30 #undo 18:14:30 Removing item from minutes: 18:14:31 #undo 18:14:31 Removing item from minutes: 18:14:33 lol 18:14:34 lol 18:14:35 olasd, basically a warning saying: don't start more than on streamings on the same time 18:14:40 I was hoping it would say what it removed 18:14:40 #info Some issues were caused by presenters not following the advice, e.g. poor quality of internet connection or bad microphone 18:14:41 hah 18:15:00 tumbleweed: it does, to some extent 18:15:07 so, anyway, tumbleweed: #action or not? 18:15:31 or anyone else (to check what happens when 2 jitsi rooms stream to the same vogol) 18:15:41 (and write the resulting advice) 18:15:54 sure, I'll take an action 18:16:16 #action tumbleweed to check what happens when 2 jitsi rooms are streaming with the same streaming key, and write the resulting advice 18:16:45 #topic 2.3. mdcobr2020 - tear down streaming CDN 18:16:55 that's been done? 18:16:57 yeah 18:17:00 #info all done by tumbleweed 18:17:04 now that we have this long-lived stack 18:17:11 there is a question of whether this should stay up 18:17:14 or some of it should 18:17:22 right now, there's a single streaming frontend at hetzner 18:17:30 which is probably enough for a miniconf 18:17:31 I don't think we need a full distributed CDN via DO 18:17:36 or whether we really need it at all 18:17:39 indeed 18:17:51 it cost us 12USD to run it, I don't think that's a problem? 18:17:52 it probably makes sense to have one regional one for regional miniconfs 18:18:02 the next one is nect month I don't think the CDN needs to stay up but it might be nice keeping it up for collective experiments and improvements 18:18:34 or make it very easy to bring it up when needed 18:18:37 it is 18:18:43 (sorry too much caffeine that sentence needed some punctuation :p) 18:18:44 it could be even easier, of course 18:18:46 I think it already is? 18:19:02 but it's half an hour's work at most to bring it up 18:19:19 most of which is "wait for ansibl to finish", I guess? 18:19:20 provided one gets a hold of one of you 18:19:21 :) 18:19:25 or olasd 18:19:27 or a DSA 18:19:42 define "easy". before DC20 it was easy to bring the stack up but in reality it took quite a while to sort everything out (of which some time was sorting out which 'hardware' to use which at least did take up quite some of that time) 18:19:42 I don't think DSA has access to the DO account? 18:19:42 they'll need to anyway if they want to have a miniconf 18:19:43 wouter: no, clicking things in DO, adding DNS records 18:19:45 at least for now 18:19:54 and then a few mins of ansible, eah 18:19:55 yeah 18:20:04 ah sounds ok at least 18:20:11 isn't there an ansible module for DO too? 18:20:11 yeah I don't think we have a problem with this atm 18:20:16 if so we might be able to use that 18:20:24 actually I have a 10 line python script somehwere to automate most of that 18:20:24 (should make things slightly faster) 18:20:28 pollo: actually, no, I think a miniconf doesn't need this 18:20:31 but it's nice to have 18:20:39 certainly would have been nice to have one in .br for the mini there 18:20:52 or we should ask talk to DSA about using one of their CDN providres 18:20:55 I mean "they'll need to reach out to us anyway if they want to have a miniconf, for now" 18:21:28 when peertube gets HLS support we can try to get a minimal "you don't need us" config 18:21:38 cool 18:21:59 I don't know if I'd trust our peertube instance for conference live streams 18:22:03 without signifciant beefing up 18:22:16 I'd steer clear of that 18:22:22 but that's because we've got something that we know works 18:23:23 shall we move on? 18:23:29 do we have anything to agree on within this topic? 18:23:29 yes please 18:23:34 don't think so 18:23:47 #topic 3.1 .in mini - timeline 18:24:33 #info The dates for the MiniDebConf online India are 23-24 January 2021 18:24:42 #link https://wiki.debian.org/DebianIndia/MiniDebConfOnlineIndia2021 18:24:50 I was proded in private mail about a site; will be bringing it up RSN 18:24:59 (wafer) 18:25:06 was about to ask that :) 18:25:23 terceiro: will you let me know when it's live? I can then add it to SReview 18:25:30 (recently fixed the parser, so it's now idempotent again) 18:25:30 tumbleweed: i don't think we'd have a problem setting up a cdn to serve debconf stuff, fwiw. let us know. 18:25:41 #link first meeting minutes: https://wiki.debian.org/DebianIndia/MiniDebConfOnlineIndia2021/Meeting1 18:25:47 wouter: yes 18:26:20 tumbleweed: I will ping you wrt DNS 18:26:30 jcristau: thanks, let's chat after the meeting 18:26:45 what should be *our* timeline wrt the .in minidebconf? 18:27:12 I think we should ask for a schedule to be ready a week in advance 18:27:30 and give them a list of things we need (title slides, etc.) 18:27:49 pollo: whoops, missed in your recent edits 18:28:10 do the .in minidc people want to use the SReview upload functionality for prerecorded talks? 18:28:37 tumbleweed: edits where? 18:28:37 do you know if MDCO India will be in english? 18:28:45 Yes for me. Will ask around and revert here. (about SReview) 18:28:49 pollo: https://debconf-video-team.pages.debian.net/docs/working_with_videoteam.html 18:29:01 phls: I think multiple languages, according to the first meeting 18:29:04 ah it's ok, paddatrapper reviewed th rest 18:29:14 For MDCO we plan, English, Hindi, Malaylam + one or two. 18:29:17 pollo: no, I mean, we could have listed all the things we will need 18:29:19 sahilister[m]: okay, I'll make that happen then 18:29:28 e.g. schedules, opening slides 18:29:29 cool 18:29:32 tumbleweed: I don't think that's the goal of that page 18:29:49 anyway, wrong topic :) 18:29:50 should we pad the list after the meeting? 18:29:57 so it can be sent afterwards? 18:30:00 olasd: +1 18:30:07 and I think we should find a place for it in our docs 18:30:19 #agreed write the list of videoteam requirements on a pad after the meeting so we can send it to the .in organizers 18:30:54 training of volunteers in the week before the conf? dry run of a talk at that point too? 18:31:02 we haven't talked about timezones... 18:31:13 it'll be hard for me to do anything for that miniconf 18:31:28 what will the timezone be? 18:31:37 india 18:31:38 UTC+5:30 18:31:41 UTC + 5:30 18:31:42 yes, obviously :) 18:31:59 that's a 10h shift on my side 18:32:04 #info conference timezone will be UTC + 05:30 18:32:12 I might be able to help out -- it's not too bad for me 18:32:27 depending on what time the miniconf is going to start 18:32:38 (although I won't be able to help until the end, probably) 18:32:45 I may be able to be around for the start of their days, if they do start earlier 18:32:53 but hard to commit to that at this point 18:32:56 anyway, we'll need a rough idea of the schedule blocks so we can plan our core volunteers 18:33:03 fairly soon 18:33:05 yeah, absolutely 18:33:25 Will discuss and mention the rough schedule in a week here. 18:33:32 for .in MDCO. 18:33:41 sahilister[m]: thanks 18:33:51 great, thanks (we probably won't have a meeting *next* week, but we'll be around) 18:34:03 #info rough schedule for .in mdco expected some time next week 18:34:05 #action sahilister[m] to give us the schedule outline 18:34:09 ... 18:34:14 we need to stop doing that ;) 18:34:24 backseat chairing ;p 18:34:30 something like that 18:34:31 #chair wouter 18:34:31 Current chairs: olasd tumbleweed wouter 18:34:44 iek 18:35:06 #topic 3.2 .in mini - Meeting schedule? 18:35:23 I'm pretty sure we need a break for one or two weeks (or three) 18:35:26 for the videoteam or the local team? 18:35:30 for the video team 18:35:41 it's a video team meeting, isn't it? 18:35:44 this is a .in subitem 18:35:53 tumbleweed: you wrote it 18:35:55 because we need to come back at a good point to engage with them 18:35:57 maybe he meant the local video team or the global video team 18:36:00 *ducks* 18:36:11 anyway, yes, I need a break 18:36:26 tumbleweed: yeah, definitely; but we've been having weekly meetings forever at this point 18:36:33 I'm guessing about 2 weeks before .in sounds about right? 18:36:42 would 1st week of jan be too late? 18:37:02 meeting on jan 5 gives us two more meetings before the event 18:37:05 which sounds fine? 18:37:09 +1 18:37:09 yeah, I think that works 18:37:16 and I'm not doing anything before then anyway 18:37:24 I mean, I don't think we'll want to upend the stack before then anyway 18:39:16 the other question is meeting time; 18:00 UTC is 01:30 AM India time which isn't great for the organizers; can we push that earlier? 18:39:53 2 hours earlier is the most that's comfortable from here 18:39:56 3 at a push 18:40:12 both work for me 18:40:30 I guess we should talk it through with sahilister[m] and others when we send our list of requirements? 18:40:39 see what works for them 18:40:39 yeah 18:41:08 #agreed next meeting on or about January 5th; in the meantime, send a list of requirements and agree on a meeting time that would work for .in volunteers as well as video team members 18:41:10 wfm 18:41:32 #topic 4. Video Archive Documentation 18:41:47 nothing yet, let's add it to the next agenda 18:41:51 ack 18:42:08 #info no progress so far 18:42:20 #topic 5. Working with the video team guidelines email 18:42:28 #link https://storm.debian.net/shared/iBkmYf38dqUk6y4hrKvFxFe2yVPsWT2G_vnz3GFB0YD 18:42:51 what triggered this? the vietnam announcement or anything else? 18:42:52 if people are ok with the text, I'll send it after the meeting 18:43:07 there's a vietnam minidc? 18:43:13 well, lack-of-announcmenet 18:43:27 ah, thailand, not vietnam 18:43:29 (ugh) 18:43:45 no, I just felt our documentation didn,t have a great starting point for organisers 18:43:51 you may just have errored MiniDC Vietnam into existance 18:43:58 highvoltage: :) 18:44:20 pollo: I think the text is fine; I wonder if this should be turned into a "bits from the video team" also announcing availability of videos from the other events (and thanking volunteers)? 18:44:44 in that case maybe extend to say that this infra is up 18:44:50 that could be done, although phls already sent an email wrt minidc_br videos 18:44:54 and you can feel free to use it for adhoc things 18:45:24 tumbleweed: you mean vogol+jitsi? 18:46:07 + streaming + obs 18:46:11 i.e. online conference stuff 18:46:22 it still needs manipulations on our side though 18:46:42 I think we're not yet at the point where people can do stuff without us 18:46:54 should teh text also encourage people to organize miniconferences? 18:47:14 wouter: "To encourage you to organise local events" 18:47:15 pollo: sure, but it's not like it's a huge ask to support an event 18:47:35 we used the example of the .br weekly streams before. We could totally support things like that 18:47:35 do we still have a lot? dinner's here 18:47:46 although if there was enough of that, we'd need a calendar 18:47:48 it does take one of us to be available for the duration of the event in case something goes wrong 18:48:00 tumbleweed: I'm not up for that on my side though 18:48:03 pollo: shall i join in the effort of writing? 18:48:06 pollo: ah yes, missed that 18:48:17 (not exactly *paying attention* but being available to react) 18:48:23 I was excited about peertube for that reason 18:48:38 nattie: sure 18:48:49 I assume peertube streaming needs something to feed it 18:48:57 the kind of infra we have :P 18:49:14 yes, but we can make that 100% automated 18:49:14 sure, fair point about needing some support 18:49:19 anyway, I think the original scope of the mail is fine, and I think the current text is ok, even though it's a bit open ended 18:49:40 yeah peertube also takes an rtmp feed for live streaming 18:49:50 if the videos for past events have been announced we don't need to do that again, I guess 18:50:10 (can't find the announcements but...) 18:50:16 probably the biggest thing we need to be involved with, in our setup, is recordings 18:50:23 and support 18:50:42 the jitsi, mixing, streaming stuff all basically runs itself 18:51:08 agreed 18:51:13 yeah 18:51:19 I'm quite happy with not advertising anything, though 18:52:59 olasd: https://lists.debian.org/debian-project/2020/11/msg00019.html 18:53:02 shall pollo send the email as-is (after some wordsmithing) then? 18:54:08 *crickets* 18:54:18 I'm all for it :) 18:54:22 +1 18:54:25 sure 18:54:39 #agreed pollo to send the working with the video team guidelines email 18:55:02 #topic 6. INSERT NEW ITEMS HERE 18:55:08 #topic 7. Any other business 18:55:10 (scnr) 18:55:40 *crickets* 18:55:41 tumbleweed: I fixed the config for lq encodings 18:55:43 ah 18:55:48 they now will be vp9 18:55:54 great 18:55:55 #info wouter fixed the config for lq encodings to make them vp9 18:55:57 thought it also means that it will lie about the json files 18:56:01 I guess that will double encoding times :) 18:56:05 s/thought/though/ 18:56:06 probably 18:56:17 any other other business? 18:56:20 the json files are full of lies about the encoding profiles anyway 18:56:25 :) 18:56:29 tumbleweed: sorry about that 18:56:46 #topic 8. Next Meeting 18:57:00 np. I don't think it's reasonable to expect sreview to use the archive-meta data format for that, internally 18:57:00 #agreed next meeting: January 5th 2021 (time TBD with the .in minidebconf team) 18:57:13 #endmeeting