17:59:23 #startmeeting Debconf 22 Team meeting 17:59:23 Meeting started Mon Feb 7 17:59:23 2022 UTC. The chair is pwaring. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:59:23 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:59:31 #topic Roll call 17:59:40 as always, please introduce yourself if you're here (I'm Paul) 17:59:46 hello 18:00:00 o/ Hi Paul :) 18:02:10 I'll give it another minute or two before moving on in case people are running late 18:04:00 Hi there :) 18:04:14 hi. i'm still nattie 18:04:16 hi 18:04:32 #topic In-person event planning 18:05:07 is there anything specific that needs to be done for the in-person event planning? The CfP is coming up (not due yet but will be in a 2-3 weeks)? 18:07:49 I assume general preparations is more or less in place by now? 18:08:34 (crickets) 18:08:34 things are okay in our side 18:09:44 Do you have somebody to lead the content team from Kosovo? 18:11:08 well, its me and Arianit. But Im more of a technical person. We would be working together 18:11:54 for content we usually copy & paste a lot from previous years 18:12:10 you will nonetheless want to work together with someone experienced in dealing with content 18:12:13 I advise to get familiar with those 18:12:38 is there a list of standard content that is needed? perhaps all the links on the DC22 site? 18:12:47 so they can be ticked off one by one 18:13:52 * terceiro looks 18:14:51 Yeah I think ensuring that the "Schedule" menu points to valid content should be "enough" 18:15:24 with the caveat that everything under /schedule and /talks is autogenerated 18:15:59 so what we need is the cfp (c & p) and important dates (not so much) 18:16:22 unless we have innovative ideas for the cfp, that is 18:16:23 are the emails to send out templates somewhere? 18:16:36 okay, does anyone want to take the CfP as an action to do by the next meeting (as in, have it on the website, not necessarily emailed out) 18:16:39 Or copy from last years' out of the email archive? 18:17:07 yeah, the team will handle this, me and Era 18:17:15 great 18:17:22 I don't think we have that ready as templates. I have been cargo culting from previous years 18:17:31 #action Content team to prepare CfP for next meeting 18:18:35 is the content team assembled? 18:18:36 EnkelenaH[m]: if you need something on the submission system side you can talk to me 18:18:52 I think we need at least to populate the tracks/talk types etc 18:19:13 alright 18:20:39 #action tracks + talk types to be populated for next meeting 18:21:16 please also remember that people who have done this before are available and very willing to work together in this, so you don't have to face it alone! 18:21:46 great :D 18:22:47 okay cool, I think if we can get the CfP and other content ready in the next couple of weeks that puts us in a good place 18:23:39 😀 18:23:56 #topic Remote contingency planning 18:23:57 I've put this on the agenda because I think we need at least some contingency planning for a remote-only event (even though everyone hopes/wants an in-person one) 18:24:39 indeed. it feels better if there's a solid backup plan 18:25:22 IMO if do a remote conf again, we need to seriously rethink the format 18:25:34 not sure if I already ranted about this before 18:25:50 there will be some overlap I presume, e.g. we'll need a CfP either way 18:27:10 we could just skip if we were forced to do online again (which I currently - luckily - doubt will happen) 18:28:54 or do something a lot smaller, async 18:29:59 yes, like the CCC one ... essentially multiple video stages in random Hackspaces that wanted to 18:30:12 did anybody participate in Fosdem online last weekend? 18:30:27 Was that anything you enjoyed? 18:30:37 I didn't this year, but last year worked quite well 18:30:57 however there was a huge amount of upfront effort involved (e.g. getting talks professionally captioned) 18:33:19 what we could do is ask a few people who were involved in the behind the scenes of a related remote conf (DC21, FOSDEM etc.) to come to the next meeting to guide us through the possibilities perhaps? 18:34:28 that could be useful indeed 18:35:10 okay, let's collate suggestions of who we can ask (specific people) to invite to the next meeting 18:35:16 or ask for suggestions / volunteering via email? 18:35:28 I think both options would be good 18:35:40 it is useful to be able to ask questions synchronously I think 18:35:50 I think people are more willing to share thoughts & experiences via email than to join a random IRC group at a specific time that may be inconvenient for them 18:36:02 well, have a go at it 18:36:13 if it works out fine, if not ... nothing is lost 18:36:14 let's get in touch with a few people and see which they prefer 18:36:19 we are not in a hurry yet 18:36:20 if they prefer email, great 18:37:00 #action All to think of people who have experience with remote confs and ask for advice either via email or to join the next meeting 18:37:14 #topic Meeting schedule 18:37:30 Next meeting in two weeks, 21st February 2022 at 1800 UTC 18:37:50 #info Next meeting in two weeks, 21st February 2022 at 1800 UTC 18:37:56 #topic AOB 18:38:01 Anything else that people would like to discuss? 18:39:56 o/ I won't be around next meeting, but can help with working through remote options 18:40:09 great, thanks for that :) 18:40:28 \o/ 18:40:31 as there's nothing else, thank you all for coming and see you in two weeks! 18:40:34 #endmeeting