Tuesday, 2023-01-10

spotzLet me get the right meeting name and I'll start14:01
fungigood call ;)14:01
spotz#startmeeting diversity_wg14:02
opendevmeetMeeting started Tue Jan 10 14:02:25 2023 UTC and is due to finish in 60 minutes.  The chair is spotz. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
opendevmeetThe meeting name has been set to 'diversity_wg'14:02
spotz#topic Roll Call14:02
spotz#chair fungi14:02
opendevmeetCurrent chairs: fungi spotz14:02
fungiohai14:03
spotzI don't think we'll have anyone else but lets give them 2 minutes14:03
fungisure14:03
spotzOk let's get going as we had a lot last time with these same topics14:06
spotz#topic Summit Planning14:06
spotzWere you able to get with Erin?14:06
fungithat was the one of two things i took on last meeting that i didn't get to yet, i think. but now i can't remember what the other one was14:07
fungiahh, right, i did reach out about the survey topic, but not the summit yet. i need to finish putting that list together14:07
spotzOk14:09
fungii'll stuff the list into our agenda pad so it's a little mor concise14:09
spotzOk is there anything we can work on for Summit ourselves in the meantime? I did put in for a BoF session, a 30 minute one as we could always move out into the hall after if needed14:11
fungithat sounds good. i don't know if there are specific topics anyone wants to present on (the cfp deadline has been quietly extended to next week so there's still time)14:12
fungithough also we can do forum sessions, those aren't decided until later14:12
spotzYeah in the system it says April 21 I think but when I asked Erin yesterday if didn't seem like that would be a hard date14:13
fungilooks like we already put the summit recommendations in the agenda etherpad last meeting, so unless there are any more you can think of i'll stuff those into an e-mail this week14:14
spotzI was going to just reach out to Erin and Allison if they want Git and Gerrit run vs going through the CFP and taking up a slot that is usually run during lunch anyways14:14
spotzYeah that looks good14:15
spotzI'm assuming most of that will be fairly easy easy being in Vanouver vs a longer haul14:20
spotzAnd once we truly get it as a routine our list will just be part of the larger checklist for events14:20
fungiyes, my goal was to have these suggestion over to them far enough in advance to be actionable14:21
fungier, these suggestions14:21
spotzYeah and some stuff might already be in process like the stickers. Comfort level I don't think we've done more then just Berlin14:24
fungiright, even if it's stuff they already planned to do, it's good to give them a reminder people are interested in continuing to do that14:25
spotzYeah and I do think going through the CHAOSS badging is important as well, I think we actually do some of it like Diversity Tickets and travel support but it's not worded clearly. We just all 'know'14:26
spotzOk anything else we need to discuss about Summit?14:33
funginope, i'll get this sent along14:34
spotz#topic 2023 D&I Survey14:36
fungii did at least get around to sending an e-mail about this after the last meeting14:37
spotzWoohoo:)14:37
spotzAny reply?14:37
fungii don't think i got a reply though, or did you see a reply i missed? if not i can ping14:37
spotzI didn't realize I was CC'ed let me look. 14:38
fungiyeah, i cc'd you14:38
fungisent on december 1314:38
fungiSubject: Guidance on 2023 updates for Diversity Survey14:39
spotzNo reply14:39
fungiaprice: did you get the e-mail i sent on december 13, guidance for updating the diversity survey for 2023?14:39
spotzIt was right before most folks wen out on PTO14:39
fungiyeah, i figured14:39
fungididn't see much point in hounding anyone for answers until now anyway ;)14:39
fungii can follow up with her this week to see if she's had a chance to read it or whether it needs re-sending14:40
spotzYeah. And I think we should include ildikov more in this to help get all the projects participating14:40
fungiagreed14:40
ildikovI’m around, but need to read back to respond properly :)14:41
spotzWith her now in PDT we might need to bump this meeting back but we'll see14:41
spotzhehe14:41
spotzWe were just getting started on the topic. Diversity Summit for 2023 nd making it work for all the projects AND them participating14:42
fungiif we want to push finalizing the survey changes to 2023, we could do a forum session to go through the current survey and proposed adjustments too14:42
ildikovHaha, no need to move just because of me, but appreciate the thought!14:42
fungier, push finalizing the changes to q3 of 2023 i mean14:42
spotzSo make it a 2024 survey?14:43
fungiwell, that's the question. second half of 2023 anyway14:43
spotzI'm not against it but we need to make sure it's not going to just be us in the session14:43
fungiwe could try to do it a lot sooner and then have a forum session about early responses i suppose, but that may be too early to have much feedback14:44
fungimainly just trying to work out whether it makes sense to incorporate a forum session about the diversity survey one way or the other. timing is sort of terrible for either approach14:45
ildikovif we want a shorter timeline than asking for feedback sooner is better14:45
spotzNo I don't mind doing a final review in Vancouver and if not much changed from it even releasing it in Vancouver14:45
ildikovthe Forum session is not fully inclusive anyway, but would be a great way to speed things up14:45
spotzWe could definitely use some hype of it being mentioned during the Keynotes14:46
fungiyeah, my take is that a forum session could get feedback from people we're generally unable to reach through mailing lists, but i don't know if that's really true14:46
ildikovspotz: if we want to release it in Vancouver then we could use the event to give more visibility to the survey, but it would need to be finalized before the event for that14:47
ildikovor just point to the effort and then release the new survey after the event to avoid it getting lost in all the other noise14:47
spotzYeah and that's the issue, we don't have much to change questionwise probably for OpenStack, we don't know if the other projects need specific questions added beyond what project are you submitting for14:48
fungiright. even if we finalized the survey this month and started circulating it, i doubt we'd have enough responses to be able to draw conclusions in time to present mid-year. on the other hand, if we wait until then to get final feedback on the updates to the survey, that's a bigger delay than we really need14:48
spotzHere's a thought. We have a working session to finalize the survey, and an announcement during the keynotes about the session and the 'expected' start date?14:49
fungiand as ildikov points out, the third option is to finalize it by mid-year and plan to hype it at the event in order to hopefully drive more survey responses14:49
ildikovfungi: do you expect significantly more participation in editing if we give it more time and make it a target for 2023 H2 or even 2024?14:50
fungiildikov: i don't really know14:50
fungithat's part of the problem14:50
fungiengagement is dismally low to nonexistent both in terms of helping us plan/produce the survey and in people taking the survey, historically14:50
ildikovI understand, it's hard to gauge14:50
spotzBut if we want to expand beyond OpenStack which we really do need to we need some help from folks in the project. I'd settle for the Community Managers if we cant't get contributors14:51
fungieven the monthly d&i wg meetings are usually just me and spotz unless we ping somebody during the meeting who happens to already be in here ;)14:51
ildikovin that case, I would go with what spotz was suggesting as well, to hype up the survey at the event14:52
fungiwfm14:52
ildikovwe can have an email campaign to the project MLs for input and review14:52
ildikovand 2 working sessions for people who want to talk about it14:52
ildikovI think the risk of not having enough participants even with the extended timeline is higher than not having a useful survey14:54
spotzOk I'll get a forum session in I'm not sure I can get 2 in, though if there was room we could add it. We also need to be weary of PTG conflicts14:55
ildikovif we have a version we can hype up during the Summit that'll give us more eyes and if people are unhappy with the survey after all, then they might be more motivated at that time to chime in and provide feedback14:55
ildikovspotz: oh, I meant two working sessions prior to the event to get the survey done by the Summit14:56
spotzAh:)14:56
ildikovI might've misunderstood the working session's purpose14:56
spotzWell the working session'forum' is to get folks in the room to discuss and finalize. It'd be really cool if it was about ready to release at the time14:57
ildikovwe could still have one Forum session for awareness and some rapid feedback14:57
spotzThen we'd know we could say look out in your email boxes the first week of July for the Diversity Survey or some such during keynotes14:57
ildikovIf we could get it ready by the Summit that would be beneficial14:57
ildikoveasier to hype people into filling it out, IMHO14:58
spotzYeah14:58
spotzI know my first User Survey I did in Barcelona for a t-shirt:)14:58
ildikovhaha, there you go :)14:58
fungiyeah, so is it two ad hoc working sessions scheduled between now and the summit to get project feedback, with a goal of finalizing the survey in time to promote it at the summit? or forum sessions to finalize the survey at the summit?14:59
spotzOk so our plan is to get Ildiko and team's help to have 2-3 working meetings to get the survey done or almost done by summit, announce during keynotes, and maybe a final session in Forums or something and release shortly after summit?15:00
fungisounds good, we still have time to refine that plan too15:00
fungiand i'll try to get feedback from aprice on the questions i sent last month15:00
spotzI don't think it's a good idea to hand folks out a D&I survey submittal t-shirt if they did the survey there no matter what. But maybe we could give out some small D&I item at the check in?15:01
fungiwe'd need to decide what, and probably find a sponsor to provide them15:03
spotzOk nix that idea I'd rather get the lunch or speed emntoring sponsored15:04
fungiyeah, prioritizing such things is tough15:05
fungiif the summit organizers are planning to do a sticker sheet as general swag, we might inquire about getting something diversity-related included, assuming there's room and the design work could be finished soon enough15:06
spotzSounds good15:07
fungii've tacked that onto the summit recommendations list from last meeting so i'll include it in the message i send to erin15:09
spotzThanks!15:09
spotzAnything else for the meeting? We' 10 minutes over15:09
fungii've got nothing else15:10
spotzOk ildikov can you check with your team about participating or finding folks in their projects? Then they can be invited to this meeting or if needed we find another day and time15:11
ildikovspotz: will do!15:11
spotzGreat meeting! Thanks for coming!15:12
spotz#endmeeting15:12
opendevmeetMeeting ended Tue Jan 10 15:12:16 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:12
opendevmeetMinutes:        https://meetings.opendev.org/meetings/diversity_wg/2023/diversity_wg.2023-01-10-14.02.html15:12
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/diversity_wg/2023/diversity_wg.2023-01-10-14.02.txt15:12
opendevmeetLog:            https://meetings.opendev.org/meetings/diversity_wg/2023/diversity_wg.2023-01-10-14.02.log.html15:12
fungithanks spotz!15:12
ildikovthanks y'all!15:12
-opendevstatus- NOTICE: One of our CI job log storage providers appears to be having trouble with log uploads and retrievals. We are in the process of removing that provider from the pool.22:43

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!