18:00:19 #startmeeting 18:00:19 Meeting started Thu Apr 29 18:00:19 2021 UTC. The chair is olasd. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:19 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:00:21 #chair pollo 18:00:21 Current chairs: olasd pollo 18:00:32 #topic Roll Call 18:00:41 please say hi if you're here for the meeting! 18:00:41 * nattie waves 18:00:45 ohai 18:00:47 o/ 18:00:52 proposed agenda: https://deb.li/oNCD 18:01:34 o/ 18:01:42 sometimes I wonder why we don't pingall at the beginning of the meeting 18:01:52 pretty sure we used to 18:02:11 * h01ger waves :) 18:02:14 We could, I just felt that would be trolling people 18:02:23 if people are ok with it I'll do it :) 18:02:45 \o 18:02:53 it'd probably help with attendance, yes 18:02:58 pollo: please use #topic, not /topic 18:03:05 oops 18:03:10 ;) 18:03:21 #topic Follow up on DC21 dates & tracks 18:03:32 #info The 21st Debian Conference is being held Online, due to COVID-19, from August 22 to August 29, 2021. It will also sport a DebCamp from August 15 to August 21, 2021 18:03:48 IIUC, atm we have 2 tracks (regular + pt_BR) ? 18:03:50 (the schedule may be contracted a little, but that's the gist) 18:04:12 + an ad-hoc one? 18:04:13 I think we should assume there's going to be a few more tracks 18:04:16 it's still early on 18:04:50 wouter: well, it affects us quite a bit, as we need to add machines for each additonal tracks :( 18:05:10 we need to add machines for each additional track running in parallel 18:05:20 I don't expect all language tracks to run on all days? 18:05:23 ah, that's what I meant by "tracks" 18:05:39 my point is that we should probably assume there's a deadline a few weeks or months from now 18:05:42 probably depends on their turnout 18:05:55 and not that we have all the numbers already 18:06:16 so "two" for now, but likely something like 3 or 4 in the end? 18:06:20 ok, so too soon to decide on that, but if someone could remind the content team each parallel track means a bunch of more work for us, that'd be nice :) 18:06:30 yes, that too 18:06:45 #topic Matrix integration 18:07:11 I haven't had time to follow up on that yet; wouter suggested talking to the element people, which I will do, getting in touch with the sponsors team 18:07:16 are people interested in my FOSDEM experience on that subject? 18:07:18 I'm on vacation next week 18:07:23 wouter: sure 18:07:25 so should have time to do so 18:07:30 and yeah, absolutely 18:07:43 so, basically, for FOSDEM we talked to the element people, and they did all the hard lifting for matrix 18:07:49 including hosting everything on their cluster 18:08:10 that included a bot which would start things on schedule and hard cut when time ran out 18:08:18 (which I honestly thought was a terrible idea) 18:08:23 that was pretty awful 18:08:26 yeah 18:08:44 anyway, so there was another bot which would invite people to a "speakers" room when their talk was about to start, 18:08:56 hmm, I'm somehow not super down with sub-contracting a very large part of our setup :( 18:09:06 and you could send it commands from a special "backroom" channel that only FOSDEM orga had access to 18:09:23 we don't have to, all the work they did is open source 18:09:31 a bot for coordinating speakers does sound useful 18:09:34 we would be able to talk to them but run it ourselves in the end 18:09:35 ok, nice 18:09:58 they did a writeup of how everything worked on their blog 18:10:01 some of the matrix dev is closed source for business reasons, that's why I ask 18:10:02 let me look it up 18:10:17 yeah, I don't think that happened here 18:10:21 not 100% sure, but like 99% 18:11:00 (still looking for blog post, sec) 18:11:01 thing is, we really mostly want to look at the widget for streaming + chat integration, and maybe the jitsi / backroom stuff for managing (recorded) Q&A in a smoother way than we did 18:11:13 you pasted it on the task 18:11:51 https://matrix.org/blog/2021/02/15/how-we-hosted-fosdem-2021-on-matrix 18:11:57 that's the blog post/writeup 18:11:57 right, just got it too :D 18:11:59 #link https://matrix.org/blog/2021/02/15/how-we-hosted-fosdem-2021-on-matrix/ 18:12:18 hehe :) 18:12:29 ok, so I guess the next step is to look at how disruptive that change would be and how hard it would be to use the FOSS thing they did 18:12:46 anything else? 18:12:48 yeah, I think so too 18:12:57 so I'll follow up on that next week: talk to the debian.social people to see how our matrix works, look at what element did, and maybe contact them 18:13:22 should we action that? 18:13:22 #action olasd follow up on matrix integration next week: talk to the debian.social people to see how our matrix works, look at what element did, and maybe contact them 18:13:33 I guess ;) 18:13:36 #topic Q&A webapp 18:13:52 so, if we are going to use matrix, then this may be superfluous? 18:13:54 We talked a bit on gitlab and decided we'd go with a django module 18:13:57 maaaybe 18:14:06 I still think it would be worth it for in person confs 18:14:19 (not saying it's useless, just that the matrix stuff includes some bits there) 18:14:43 It's a good point, but "real work" on this hasn't started yet, so we'll see :) 18:15:03 sure 18:15:04 I suspect a Q&A standalone thing would be worth it integrated as a widget in the matrix too 18:15:07 * fil sneaks in late 18:15:10 and at any rate, it wouldn't be wasted effort 18:15:23 anyway, not much more to add :) 18:15:32 #topic Streaming 18:15:40 not sure I remember why I added this 18:15:53 are we OK with our current streaming setup? 18:16:07 Ah, it was the Cloudflare CDN thing 18:16:16 there was the cloudflare thing, but cloudflare also did another cloudflare in the last two weeks 18:16:16 yeah, we should probably try it 18:16:34 (don't remember which cloudflare they did /this/ time) 18:16:35 olasd: EPARSE, can you clarify? 18:17:22 wouter: they did something stupid ethically/politically, again. I don't remember what 18:17:31 oh, right 18:17:45 ah, yes, the nft thing https://blog.cloudflare.com/cloudflare-stream-now-supports-nfts/ 18:17:50 ah, that 18:17:53 * olasd headdesks again 18:18:03 they're also trying to shut down another patent troll, +1 there 18:18:09 ooooohh, my goodness 18:18:21 anyway, I don't think any progress has been done 18:18:25 nope 18:18:39 #topic Ansible & migration to Bullseye 18:18:44 nothing on that side either 18:18:54 it's not urgent though? 18:19:01 it appears ansible will make it in bullseye though 18:19:02 I mean, buster still works 18:19:09 I think there was movement in the "getting up to date ansible in bullseye" front? 18:19:13 it appears it will, yes 18:19:21 wouter: sure, but we said we'd like to migrate if possible 18:19:22 it's waiting for 20-day aging 18:19:28 #info it appears ansible will make it in bullseye 18:19:29 nice 18:19:35 pollo: fairy nuf 18:19:57 #topic Video Archive Documentation 18:20:00 also, built-in mitogen, nice 18:20:03 day 5 of 20 (on mitogen) 18:20:39 should I make a start on the docs? 18:20:40 nothing new on the archive thing, my (small) appartement was under massive renos last week and kinda messed up my plans 18:21:00 something like "videos get copied to X, they get rsynced to video.Debian.net from there" 18:21:03 wouter: if you want, but I was planning on learning about the archive setup this way too 18:21:20 pollo: okay, if you expect you'll have the time soon, I'll leave it to you then 18:21:29 * wouter <- not very good at writing good docs anyway 18:21:31 it's not critical work, I'm just leaving it in the schedule not to forget 18:21:39 right 18:21:43 I skipped review! 18:21:46 #topic Review system 18:21:47 yes! 18:21:49 I was going to say :) 18:21:59 so I have made a start on the final review thing 18:22:04 \0/ 18:22:18 thanks! 18:22:22 basically it'll be a form that says "is it good" with a yes/no comntrol 18:22:24 control, even 18:22:29 and a comment field that will turn into a log 18:22:41 #info work has started on integrating the final review step in Sreview 18:22:44 (the regular review comment field will also be a log going forward) 18:22:59 so there's a few minor things changing there, nothing crazy though 18:23:27 #topic Any Other Business 18:23:44 oh, right 18:23:58 I was also thinking of replacing the bs1770gain thing by ffmpeg audio normalization 18:24:07 because bs1770gain *changes timing* 18:24:09 horrible 18:24:20 anyway, I've done some research there, but it's not ready yet 18:24:34 I should be able to get that ready by debconf though 18:25:00 #info audio normalisation should be ready for DC21 18:25:05 anything else? 18:25:47 #topic Next Meeting< 18:25:52 Next Meeting Thursday May 13th from 18:00 to 19:00 UTC ? 18:25:59 sounds good to me 18:26:03 sgtm 18:26:03 sounds good to me 18:26:08 #agreed Next Meeting Thursday May 13th from 18:00 to 19:00 UTC 18:26:12 #endmeeting