18:00:17 #startmeeting 18:00:17 Meeting started Mon May 24 18:00:17 2021 UTC. The chair is nattie. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:17 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:00:25 #topic roll call 18:00:28 hi 18:00:30 zleap 18:00:30 holler if you'rehere 18:00:33 Hi 18:00:38 Hi 18:00:40 hi 18:00:41 (I will need to drop at :40 FWIW) 18:00:41 ji 18:00:42 o/ 18:00:47 * bittin^ hollers 18:00:47 Hello! 18:00:52 hi 18:00:58 wow that was loud bittin^ :D 18:01:04 Hello 18:01:08 hi 18:01:19 hey 18:02:10 that looks like a reasonable number of participants 18:02:22 thx @bittin for inviting me here in the debconf-team! 18:02:35 np 18:02:35 #topic last meeting's actions 18:02:51 #info there were no action items at the last meeting 18:02:59 really? 18:03:04 hi! 18:03:08 there was a CFP that terceiro sent out yesterday 18:03:12 well, the cfp was pending since a few meetings back 18:03:12 terceiro: it was all infos and agreeds 18:03:14 that's done now 18:03:29 #topic community team 18:03:42 mollydb, amacater: over to you 18:04:15 has anyone contacted you since the last meeting to get involved? 18:04:20 * amacater has just put in a CFP submission for a BoF for CT 18:04:23 No, but i suspect I need to write an email. :) 18:04:34 Basically my update is "I think I was supposed to write an email and forgot to." 18:04:43 mind if i give you an action item for that mail? 18:04:48 Please do! 18:05:11 #action mollydb to write an email inviting people to get involved in the community team 18:05:12 Quick discussion over on IRC suggests that we should try to be here for you on IRC/email for the whole of main DebConf - do you agree? 18:05:26 yeah 18:05:45 yes 18:05:47 sounds a good idea, I will be on IRC anyway at some point so can join 18:06:10 amacater, I don't quite understand what you mean by 'here for you'. Please could you explain a little? 18:06:17 Do you need us for DebCamp as well - or is that likely to be lower profile / slower speed of response needed. 18:07:05 seabass, probably someone being in the room to answer any questions in case anyone drops in here during debconf 18:07:13 We'll be around on IRC/email to deal with any CT "stuff" and try and defuse any situations - IRL in physical presence we'd be there anyway 18:07:35 amacater: perhaps for the benefit of newer participants you could explain what the CT actually does? 18:07:54 amacater, thanks for explaining. That sounds like a very good idea to me 18:08:19 The Community Team is the team people contact when someone is violating the Code of Conduct or otherwise behaving inappropriately, 18:08:26 https://wiki.debian.org/Teams/Community 18:08:31 Community team is there to try and make Debian a welcoming place: to suggest nicely to people they follow CoC - and follow up as necessary 18:08:35 mollydb: ok thx for explaining! 18:08:57 A method that worked very well for LibrePlanet 2021 was that community team members would become IRC operators only when actually available. 18:09:22 That meant that participants would always get a swift response when they brought anything up with an IRC operator. 18:09:26 in an online debconf context there will be the IRT (incident response team) to respond to anything that comes up 18:09:36 and at the same time, yes, room moderators will kick people out for violating the CoC 18:09:43 generally debian doesn't have active ops in IRC channels, admins give themselves ops when they need to deal with a situation 18:10:39 tumbleweed, ah, I see. In this case, LibrePlanet team members used ops to indicate that they were available at short notice, rather than actually to kick or otherwise moderate a channel. 18:10:51 i was a mod at libreplanet so was given the power to op self at start of 2 hour shift 18:10:57 BTW, community team: Do you have an OFTC chanserv team that we can add to debconf channel ACLs? 18:11:50 CT's IRC channel is #debian-ah - more than that, I don't know - IRC not very experienced Andy 18:11:54 tumbleweed: amacater, corred me on this if i'm wrong, but i think the answer is "not currently, but we could make that happen/" 18:12:03 Please do not share#debian-ah 18:12:21 Correct - ignore last from me 18:12:22 it's used as a private channel for team meetings. 18:13:13 ok 18:13:36 FWIW: as with dc20, the admins of the conference-specific infrastructure are generally the core video team 18:15:31 and both the DCC and the Debian IRCops have admin on IRC channels 18:15:38 so far 18:15:56 DCC = debconf commitee 18:16:03 ah 18:16:24 if the community team creates a chanserv team, we can grant them admin too 18:16:39 yes 18:16:53 tumbleweed: that makes sense and sounds good 18:17:12 anything else for community team just now? 18:17:22 mollydb: you've got your action item :) 18:17:27 nattie: thanks! 18:17:37 how many people do we need to monitor the chat ? 18:17:56 zleap: guess it kinda depends on how many chat and how fast the chat goes etc ? 18:18:01 i think that's something to discuss closer to the start of the conference? 18:18:02 CT is only four or five people all told but in different TZ 18:18:05 but thats just a guess 18:18:19 nattie: i don't have anything else 18:18:34 * amacater has nothing else: in future listen to mollydb :) 18:18:43 right. because of time constraints i've swapped the next two agenda items, so we will discuss the opening and closing videos next 18:18:50 #topic opening and closing videos 18:18:54 terceiro: speak :) 18:19:11 so, last time I lead the effort of doing those videos 18:19:26 they were composed from lots of contributions from lots of people 18:19:32 including editing (a lot of work) 18:20:03 I can still take part is planning (script etc), but I will need help with the editing part 18:20:09 if the plan is same as next year (i can help speak some lines and record) (and hopefully get the levels right on the mic, if i have more time this time around) 18:20:16 same as last year i mean* 18:21:13 so we need someone to lead the effort, and to find someone who will do video editing 18:21:13 this is a good way for people to get involved in advance a bit 18:21:38 well video editing - which skills are needed? 18:21:46 i can give you some help to editicion 18:21:47 1 a good computer 18:21:57 andi89gi: mostly just sticking people's contributions together 18:22:05 video editing skills 18:22:06 andi89gi: if its the same as last year, editing togheter a bunch of videos of people saying things to a long video 18:22:08 fancier things are optional 18:22:12 and normalize audio etc 18:22:57 bittin^: well, then I may also give it a try and doing this ;) 18:23:33 i can do some saying things into a webcam part and try to boost and check my microphone working better this year as i hopefully have more time 18:24:15 could those who want to help with editing the opening and closing videos stay just a few minutes after the meeting, please? 18:24:47 just the editing volunteers. those who want to make recorded contributions will be called upon later 18:24:50 TBH I'm not sure the whole "get clips from several people" works great though 18:24:58 the quality of the videos is completely out of control 18:25:11 just to be clear, whoever volunteers for this needs to commit to being available in the week before the conference, to coordinate figuring out a script, collecting videos, and editing it together (assuming we use that approach again) 18:25:18 but well, the people who do the work can do whatever they want 18:25:20 I have a nice micro or gaming headset from Logitech 18:25:20 terceiro: fair enough it was just a guess from last year 18:25:47 the alternative is for one person to do the opening & closing 18:25:55 should not have made assumptions 18:26:02 sorry for that 18:26:05 the nice thing about the clips from several people was that it brought together a remote disparate team 18:26:11 yes, that was nice 18:26:24 but it's not nice to the volunteer putting them together :) 18:26:26 yea this sounds really cool! 18:26:32 :D 18:27:16 terceiro: :P 18:27:17 I think getting clips from several people can work, specially if done in advance and not in the last week 18:27:27 this is why we're discussing it now :) 18:27:32 i.e. with enough time to give people recommendations to get some quality recordings 18:27:55 yeah, this kind of thing is probably better done well in advance 18:28:01 +1 18:28:04 at the last minute, everyone is busy 18:28:17 (as someone who recorded her voice to low last year) 18:28:54 not only voice, we need consistent/quality video as well 18:29:21 noted 18:29:45 OK, so, as said, people interested in joining this team, please stay a few moments after the meeting closes 18:29:57 s/team/effort/ 18:30:21 #info those interested in joining the opening/closing video effort are encouraged to remain briefly after the meeting 18:30:31 is that all on that for the moment? 18:30:54 #topic blockers to opening registration 18:31:01 registration is not yet open! 18:31:13 thanks 18:31:15 pretty sure i could login to the site with salsa now atleast 18:31:17 please don't be under the impression that you've registered 18:31:29 ah 18:31:52 also, reminder to new attendees, it's a two-step process, and having an account on the website is not the same as being registered for the conference 18:32:12 ah i see 18:32:26 that confused me 18:32:27 it'll open when it's ready :) 18:32:35 so, we should open registration, but that needs to be ready 18:32:43 okay so we have to register on debconf site and where the other ? 18:32:45 #topic blockers to registration - bursaries 18:32:53 you can test it right now on wafertest.debconf.org (but be sure to unregister there if you're already registered there from a previous year) 18:32:55 andi89gi: i'll explain it briefly after the meeting 18:33:00 err unregister first 18:33:15 nattie: thx 18:33:38 so, bursaries 18:33:52 andi89gi: signing into a website is not the same as registering for a conference. Nobody is going to keep food for you, or give you a t-shirt, etc. without more details than a sign-up 18:34:27 tumbleweed: nattie: thanks for the information i got confused 18:34:49 tumbleweed: ahh ok 18:35:01 so once registration is actually open, you can do that 18:35:16 we will announce it :) 18:35:16 nattie: ok thx :D was confused like bittin^ 18:35:40 so, getting back to the things that are preventing us from opening it right away: bursaries 18:35:41 tumbleweed: do we sponsor with someone to deliver food :D *joking* 18:36:10 last year we offered some smallish bursaries to cover expenses incurred for attending debconf if needed 18:36:33 such as a better mic/headphones for speakers who didn't already have those, etc. 18:36:45 i think the current questions is whether that should be offered again 18:36:49 *question 18:37:14 if we have the money i don't see what not, for a resonable budget 18:37:40 * terceiro drops 18:37:50 that said not for all speakers, that wants to have free money to update their gear, but would be good if people could prove they need it 18:38:03 i agree there 18:38:07 DLange: Are you around / any views on this? 18:38:12 almost nobody applied for this funding last year 18:38:36 define "almost nobody"? five people? ten? 18:38:37 so the assumption is that virtually nobody will this year (surely we're all set up for video-conferencing at this point) 18:38:41 I think 2 18:38:49 oh ok, that is indeed very few people 18:39:02 * tumbleweed checks 18:39:11 so maybe we can have it for 5-15 people 18:39:16 depending on what the budget allows 18:40:02 tumbleweed, yeah, people can easily borrow a head set if need be from friends surely 18:40:06 ah, I see 21 on https://debconf20.debconf.org/register/statistics/ 18:40:09 not sure how many were actually claimed 18:40:27 How much was roughly the total of bursaries payed last yer? 18:40:28 i applied.. and i think that was very nice to me 18:40:57 cannot think of a good reason to not offer it again. 18:41:20 But I really expected more people to ask 18:41:35 tzafrir: I don't have stats, but someone from the bursaries team may 18:42:01 the bursaries team don't seem to be there just now 18:42:16 hopefully we can get that information soon 18:42:22 the bursaries team was not involved last year; IIRC, the request went directly to highvoltage[m]? 18:42:31 bursaries team: It would be good to get that into our ledger, too 18:42:43 Anyway, is this really a blocker? 18:42:52 tzafrir: deciding whether to offer it or not is a blocker 18:43:24 personally, I think it's reasonable to offer that again 18:43:28 +1 18:43:31 (but I'm not the one who has to do the work to handle them) 18:43:58 would it make sense to discuss this when the people involved are actually around, and reach an agreement then? 18:44:18 gregoa: I think it only went to the DPL if you needed >$50 18:44:19 all being well, we can then either tell people at the next meeting what's been decided, or open registration 18:44:28 (but in practice I think the bursaries team was DPL+DLange last year) 18:44:55 yeah, or that, but it was not the "old" bursaries team and not the "old" bursaries process 18:45:19 yeah 18:46:08 shall we agree to continue this when the bursaries team are around? 18:46:17 sounds good 18:46:20 and not wait until the next meeting 18:46:36 #agreed discussion on bursaries to continue when the bursaries team are present 18:46:38 ideally, I'd like to open registration ASAP (esp if there are bursaries) 18:46:49 #topic blockers to registration - t-shirt addresses 18:47:20 this is specifically about shipping addresses for t-shirts, and changing the input from a single block of text to separate fields 18:47:47 yeah! 18:48:17 Are you OK with: Adressee Name, Address Line 1, Address Line 2, City, State/Province, Country? (with validation onl on the country field) 18:48:31 tumbleweed: post code too please 18:48:38 oh, and Postal Code / Zip, yeah 18:48:41 although not everywhere has postcodes, still 18:48:52 * nattie gives tumbleweed a gratis comma 18:49:26 Not everyone has street addresses either (I think around here addresses are more descriptive than number + street) 18:50:12 o: 18:50:16 perhaps if people have an address that doesn't fit that format, they should contact us directly by mail, or in a note on the form 18:50:33 I'd imagine they're used to stuffing it into 2 address line fields 18:50:43 though mail is probably better if necessary 18:51:27 small we move on? 18:51:30 sure 18:51:31 another important piece of information is to highlight the final time of the orders, with time in UTC. 18:52:01 hrm, we do have that 18:52:20 I mean, we have a timestamp that registration was completed 18:52:27 or otherwise, explicitly expand it to anywhere-on-earth 18:52:34 (but they could have chosen not to select a t-shirt, on the first time around) 18:52:42 United Kingdowm is UTC+1 18:52:51 zleap: thank you for the information 18:52:58 July: Last day to register with guaranteed swag. Registrations after this date are still possible, but swag is not guaranteed. 18:52:59 I think we just export the shirt list at the deadline time 18:53:23 or block new shirt selection after it 18:53:52 the system does have a concept of a swag deadline 18:54:11 so the question is just to decide whether we make the deadline UTC or anywhere-on-earth 18:54:24 AoE is nice because it avoids complaints 18:54:25 sure, but BR ia UTC-3.. we have some people that fill form at 23h in Brasil.. 02UTC... 18:54:43 and they asked for tshirts.. :-( 18:54:43 and Swedish is UTC+2 18:55:03 *Sweden 18:55:04 we are allowed to say no, too 18:55:25 Berlin is UTC+2 as well 18:55:28 cut off at 00:00 UTC a day ? 18:55:34 let's make is AoE, but be strict about that 18:55:41 but no ok.. if are possible to put this information, Ok.. if not.. let's move on.. 18:55:45 action me for the strictness 18:56:03 #action tumbleweed all the temporal strictness 18:56:15 can you select a cutoff date? 18:56:17 #undo 18:56:17 Removing item from minutes: 18:56:21 right now, it's TBD on https://debconf21.debconf.org/schedule/important-dates/ 18:56:29 #action tumbleweed all the temporal strictness (setting the cutoff date/time for t-shirts) 18:56:30 but sometime in July 18:56:44 i think the test site suggests the 25th of July 18:57:00 you good with that? 18:57:02 and TTBOMK most t-shirts arrived before or during the conference 18:57:05 sure 18:57:07 sure 18:57:22 i guess, it's OK 18:58:05 the thin line we're trying to walk there is to make it early enough to get shirts to as many people as possible before the event 18:58:25 and late enough to allow as many people to register for them as possible 18:58:37 sure 18:58:55 how long does it take for delivery 18:59:08 depends on the country 18:59:10 that depends on the distributor 18:59:12 and where they are printed 18:59:37 we have someone organising the order for the UK, thankfully, so that will at least avoid import holdups 18:59:49 :) 19:00:08 we have thought about this 19:00:34 do you still need more printing volunteers, or is the globe covered at this point? 19:00:36 one can think its britts who take care of the shirt 19:00:38 shirts 19:00:39 :D 19:00:55 other distributors will be arranged by region 19:01:18 remembering freewear working good last year 19:02:11 anything else on shirts for now? 19:02:36 https://www.freewear.org/news however this is kinda bad news 19:02:36 #topic sponsorship tiers 19:02:51 anyone here from the fundraising team? 19:04:27 looks like not today 19:04:34 #info the fundraising team is not present today 19:04:43 #topic scheduling the next meeting 19:05:00 Freewear will be closed 24th May - 29th June and don't sell their regular stuff online conference shirts 19:05:09 two weeks from now puts us at the 7th of June 19:05:16 next meeting, same channel, same time in 2 weeks? 19:05:21 bittin^: i think they're just clearing backlog, and will be back after that 19:05:40 7th of June at 18:00 UTC? 19:05:56 can't attend then myself as its https://developer.apple.com/wwdc21/ but will read the logs 19:05:57 yea for me that's fine! 19:05:57 :) 19:06:03 #agreed next meeting 7th of June, 18:00 UTC 19:06:04 sure.. 19:06:06 #topic AOB 19:06:31 Are there any press releases for promotion ? 19:06:34 There are a few of us working on documentation for new volunteers. We'll let you know when that's ready 19:06:42 zleap: that's the job of the publicity team 19:06:44 Cheese: Will there be another C&W from home this year? 19:06:46 ok 19:06:51 tumbleweed: eh, sure, why not 19:06:54 i am in that channel so will discuss, thanks 19:07:39 anything else before i close? 19:07:44 don't think so 19:07:54 thanks all for attending; see you in a fortnight 19:07:57 #endmeeting