18:01:02 #startmeeting Weekly DebConf Video meeting 18:01:02 Meeting started Thu Jul 23 18:01:02 2020 UTC. The chair is tumbleweed. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:02 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:01:06 #topic roll call 18:01:10 ohai 18:01:10 o/ 18:01:13 hi 18:01:31 #topic actions from the last meting 18:01:37 #link http://meetbot.debian.net/debconf-video/2020/debconf-video.2020-07-16-18.00.html 18:01:52 #link http://deb.li/oNCD Agenda 18:02:18 neither of my items got done; I'll carry them over to next week 18:02:20 I didn't touch VNC 18:02:32 wouter reported back on sreview earlier this week 18:02:35 I have a multi-hour train ride on wednesday, might get some hacking done 18:02:44 he said early next week 18:03:04 #action olasd to update the docs for RTMP streaming option (carried over) 18:03:16 #action olasd to look at making a thomann basket for the missing equipment (carried over) 18:03:21 thx 18:03:21 meh, we should probably be using tickets rather than this 18:03:38 at least for the first one 18:04:03 I made some progress on recording playback, but that whole thing needs to be reworked 18:04:23 #action tumbleweed to continue to work on recording playback 18:04:41 paddatrapper has been ansibling jibri 18:05:04 dunno about his resolution action 18:05:13 or the documentation one 18:06:05 ah, you're taking notes, I was wondering 18:06:11 yeah 18:06:15 done 18:06:21 #topic salsa issues 18:06:30 #link https://salsa.debian.org/debconf-team/public/data/dc20-online/-/issues 18:06:49 I think most of these are on the agenda later, or mentioned before (action items) 18:06:59 looks that way 18:07:05 moving on 18:07:11 #topic Video Stack 18:07:11 I suggest moving these two points to the end of the meeting for next time 18:07:16 (partly reading here due to power failure) 18:07:18 Sensible, yes 18:07:56 so, been making some progress on voctoweb 18:08:06 I decided to learn modern frontend web-dev and write it in vue.js 18:08:10 pretty happy with that 18:08:24 it's a lot more maintaniable like this (but less hacktastic) 18:08:25 I think that's what gitlab uses too 18:08:29 yeah 18:08:43 I honestly just picked it because I'd heard of it and never used it 18:09:09 they creation of the previews kills the voctocore output, so that's an import issue to look at 18:09:14 they keep talking about how happy they are with it, so it can't be too bad. usually people start hating a library as it ages :) 18:09:18 after last week's meeting, I've been poking at casparcg a little; it might be a decent option to have a remote-controllable source for playback, web display and other static stuff 18:09:46 cool 18:10:14 yeah, I don't think we're going to get gstreamer pipelines done to do this 18:10:57 (I could get it to play the loop, to render the now/next schedule, and to show a web page with some javascript and a clock) 18:11:15 olasd: can you try feeding that into vocto? 18:11:48 I should, yes 18:11:57 you need a VM for it? 18:13:20 yeah, I was about to say I should try to run it on infomaniak, which means finding where to run it 18:13:52 supposedly it /can/ use a GPU, but I don't think we're going to use much fancy stuff so a plain vm should be fine 18:14:15 start with a plain one, see how it goes, I guess 18:14:21 yeah 18:14:29 #action tumbleweed to spin up a VM for casparcg 18:14:44 #action olasd to attempt to set up a loop with now/next in it in casparcg 18:15:09 lgtm 18:15:15 #topic Streaming setup 18:15:19 meh? 18:15:26 no changes detected 18:15:27 dunno how much there is to say here 18:15:37 #topic Advice for directors & talkmeisters 18:15:48 paddatrapper had an action here, without him, we may want to skip 18:15:54 well 18:15:58 feels like we need o volunteer wrangler, too 18:16:15 maybe we should talk about the idea of multiple parallel tracks (which is somewhat related): 18:16:41 my feeling is that the setup for directors/talkmeisters will be rather complex, so we'll probably need people around with detailed knowledge of it 18:16:51 so that makes it harder to run 2 tracks at once, so we should try to avoid that 18:19:10 yes, we should try to avoid that 18:19:12 yeah, I guess I agree 18:19:15 ha 18:19:24 or at least fall back to a much simpler second track (jitsi-only) 18:19:43 well, jitsi-only isn't really a track 18:19:50 but people can do that if they want 18:19:55 it's a webcam in a hallway :P 18:20:30 it can have a record button 18:20:46 but yeah 18:21:20 I'm not following along the meeting, but will chime in nonetheless 18:21:28 Content Team did not receive so many talks 18:21:42 I believe we can push for a single-track DebConf 18:21:51 that's good :) 18:22:07 it has the added benifit that people can follow everything if they want (assuming they don't sleep, maybe) 18:22:17 It'd be better communicated betwen the teams better than just by a comment in a meeting ;-) But I think it can be done 18:22:31 The only point that would irk me is... language-specific miniconfs 18:22:41 well, that's the concern here 18:22:41 gwolf: I think ivodd's concern was about the new language tracks popping up over the last few days 18:22:41 that's not likely to be on the "main" track 18:22:46 2 of those suddenly appeared 18:22:51 right 18:22:54 after we all thought they were not happening 18:23:33 I guess in the end this all will depend on how much interest these really gather, and how their schedules can be accommodated 18:23:35 as a lurker, the setup seems more involved than what I'd be happy to operate being "just" an outsider volunteer 18:23:57 yeah, that's why we said having a core video team member on board for each miniconf was required 18:24:03 *nod* 18:24:03 not just outside volunteers 18:24:04 olasd: The Spanish one is quite likely to happen... Although I insist, it's much closer to a DebianDay than to a DebConf 18:24:32 tumbleweed: Yes. Say, now that you are a bonafide Californian, do you care to take accelerated Spanish lessons? 18:24:44 * tobi is late again... srry… 18:24:45 gwolf: not a bonafide Californian for much longer :P 18:25:04 tumbleweed: Oh, are you being deported? They are great deporting to my country, y'know 18:25:12 ( /me stops hijacking a meeting) 18:25:38 don't know if we can conclude any actions from this discussion 18:25:54 tumbleweed: we'll know more once we have done a test run 18:25:55 make sure the scheduling / content team knows of our concerns about parallel tracks 18:25:58 well, I will ask Content to keep what we do aligned to a single track 18:26:07 yeah 18:26:18 #topic advice/training for presenters 18:26:23 But as for lang-specific... I think it's up to the video team to be very clear about the need for involvedness... 18:27:05 gwolf: yeah, I don't think there's an issue there 18:27:06 document is done, published 18:27:12 tumbleweed: I've seen some positive feedback from people about this advice 18:27:27 so, all good :) 18:27:30 any negative feedback yet? I do worry that it's not prescriptive enough for somebody who has no idea 18:27:47 (but that's a sample of 1 feedback, so...) 18:27:49 * gwolf relayed to -content 18:28:05 when's the deadline for pre-recordings? 18:28:17 (i.e. "when should we expect people to start panicking?") 18:28:23 16th 18:28:43 #topic Any Other Business 18:28:48 Anybody? 18:29:16 not from me 18:29:33 #topic Upcoming Meetings 18:29:38 I guess agian next week 18:29:45 We postponed the test run. It feels like we should, again 18:30:01 yeah, there's nothing to test yet 18:30:39 I'll have time on Saturday to poke at my actions 18:31:41 * tumbleweed intends to do more of that too 18:31:51 maybe this will be an impromptu sprint 18:32:08 maybe we should just call it a sprint 18:32:21 sounds good to me 18:32:36 #agreed impromptu sprint this weekend 18:32:46 then... we're done 18:32:49 #endmeeting