14:01:03 <spotz[m]> #startmeeting diversity-wg
14:01:03 <opendevmeet> Meeting started Tue May 14 14:01:03 2024 UTC and is due to finish in 60 minutes.  The chair is spotz[m]. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:03 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:03 <opendevmeet> The meeting name has been set to 'diversity_wg'
14:01:27 <spotz[m]> #chair fungi
14:01:27 <opendevmeet> Current chairs: fungi spotz[m]
14:01:34 <spotz[m]> #topic Roll Call
14:02:01 <spotz[m]> o/
14:02:11 <spotz[m]> See if anyone is hanging in the channel and wants to join
14:02:14 <fungi> ahoy!
14:05:01 <spotz[m]> We don't have anything in the actual agenda but we're pretty ad-hoc:)
14:05:05 <spotz[m]> #topic Survey
14:05:12 <spotz[m]> Any updates?
14:06:04 <fungi> so, we did start drafting communication points in an etherpad...
14:06:10 * fungi finds
14:06:40 <fungi> #link https://etherpad.opendev.org/p/surveyemail
14:08:37 <fungi> i think where we ended up a couple of meetings back was that once we're satisfied that covers our recommendations for what to communicate, you had said you'd send something to the foundation ml while i'd work with the other community managers on similar targeted outreach to their primary communication channels
14:09:19 <spotz[m]> Just added that link to the agenda so we don't have to search next time:)
14:09:23 <fungi> i don't remember if we'd decided that everything we want to cover is in that pad now, or whether there's anything missing
14:10:03 <spotz[m]> Ok so I'll put together an email this week, no I think it covers the basics except for where the actual survey is:)
14:10:31 <spotz[m]> Pulling up our page now
14:10:45 <spotz[m]> #link https://openinfrafoundation.formstack.com/forms/openinfra_diversity_inclusion
14:12:06 <spotz[m]> I'd like to get that kickstarted, it'd be have some results to maybe combine with information from the OpenInfra Days if any was taken
14:12:20 <fungi> i thought we had intentionally not deep-linked to the survey url in order to drive people to the diversity page so they'd also see how to get involved
14:12:51 <fungi> since we primarily made that page in order to have a better perma-link/landing page for promoting the survey anyway
14:14:27 <spotz[m]> I think we should do both at this point, no one is going to either
14:15:21 <fungi> well, we haven't publicized that page yet, which was supposed to be the next step after we got it added
14:15:57 <fungi> i agree nobody is likely to stumble across that at random either
14:16:17 <spotz[m]> So do we want to publicize first then in a month push the survey?
14:17:30 <fungi> well, since the primary think we put that page together for was to act as a place to link the survey (so that our promoting isn't pointing at some long/random formstack url), i thought we could do both at the same time
14:18:01 <spotz[m]> Ok so I was typing something like the following but then deleted it...
14:18:41 <fungi> that was why for point #1 in the pad i said the page includes a link to the survey (so that people know where to find it)
14:18:58 <spotz[m]> On the Diversity and inclusion WG page(link) you'll find information on how to get involved including information about the diversity survey(link)
14:19:33 <spotz[m]> Ok I'll work on something later today hopefully and put it on that etherpad and then ping
14:20:47 <spotz[m]> Anything else on this?
14:21:01 <fungi> i'm not wholly opposed to communicating links to both, but figured if people who want to take the survey are following the one and only link in the e-mail then they also have all the information about the mailing list and monthly meetings right there too, along with context as to what we're about, rather than following a direct link to the survey and missing the rest
14:22:01 <spotz[m]> True, let's see how it comes out when in email form. I know some of the events pages it's hard to find the links to things due to type and colors
14:22:06 <fungi> sending them to that page avoids needing to redundantly communicate details/links and additional context in the e-mail, freeing us up to keep it short and to the point
14:23:43 <fungi> and yeah, that was all i had for the survey topic
14:24:22 <fungi> we've got a community managers meeting in a few hours, so i'll update the rest of them on this
14:24:39 <spotz[m]> Sounds good.
14:24:53 <spotz[m]> #topic events
14:25:34 <spotz[m]> Any word back on the events? I know from looking at a few of the schedules diversity wasn't a major factor in picking the speakers
14:26:08 <spotz[m]> So that might be something we need to work on if we do the community events again
14:27:00 <fungi> yeah, also the foundation staff is in less of a position to control that for this year's events
14:27:17 <fungi> at least for the european roadshow events
14:27:58 <fungi> i think we still have some time to try to impress the importance of it on the korea organizers since that cfp doesn't close for a couple more weeks
14:28:03 <spotz[m]> Maybe a guideline, things to consider when selecting your talks and speakers
14:28:57 <spotz[m]> It's not just gender diversity, but company, nationality possibly as well language permitting
14:29:09 <fungi> but probably one of the other things we can try to do is encourage a greater diversity in speakers proposing talks. if the track chairs end up with very little diversity to pick from, then they're kinda stuck
14:29:52 <fungi> which i get the impression may have been part of the problem for the events this month
14:31:05 <fungi> the staff have at least made sure to impress on the event organizers the importance of publicizing and following the code of conduct
14:32:28 <spotz[m]> Yeah that could go back to the links being hard to find issue. I know Helena has sent emails to the foundation and community lists but that might not have gotten a broad enough audience from the OpenStack side, Ildiko emails the StarlingX list but they have 1, etc
14:32:30 <fungi> yeah, for "diversity" i've always felt we're trying to improve it along a variety of vectors: personal diversity, professional diversity, cultural diversity, geographic diversity
14:33:28 <spotz[m]> Maybe we can start a proposal help group, that would help with folks early in their speaking careers
14:34:27 <fungi> i've seen that tried in other communities, presumably it works well but i don't know that for certain. definitely worth a shot
14:35:08 <spotz[m]> That plus a track chair guidelines to help folks who maybe haven't organized a large event before
14:35:41 <spotz[m]> It works for devconf CZ for sure, I usually mentor looking at proposals and then helping folks with run throughs
14:37:54 <spotz[m]> We can offer that's all we can do
14:37:59 <fungi> back in the early days of the openstack infra team, we collaborated on putting together/sharing slide decks and associated abstracts that newer folks could propose to a conference and present without having to do a ton of work, though that was more for submitting to conferences that hadn't seen that same material previously
14:38:49 <spotz[m]> Yeah I've been wanting to have a few prepared talks for CentOS for a while
14:41:15 <fungi> also i'm told we have more travel support budget this year than we've had previously, so we can try to encourage speakers to take advantage of that
14:42:16 <fungi> if it comes down to deciding who will and won't get their travel comped, diversity aspects and whether they're speaking will play a key role in that
14:42:52 <spotz[m]> Yeah and Helena and I already talked about the overlapping cutoff dates
14:43:28 <spotz[m]> I also think there will be less talks because of the 2 days so that also adds in a way to the budget
14:43:41 <fungi> the regional nature of these events likely means we'll see lower levels of geographic, cultural and, to some extent, professional diversity for attendees, but we'll also be needing to try extra hard to pull speakers from farther afield
14:45:09 <spotz[m]> People are applying at least for Asia. Sweden and CERN have speakers from other continents but I think the Ironic meetup helped on that
14:45:33 <fungi> would be good to think about what we could do to encourage more people to submit talks
14:46:17 <fungi> at least if there are lots of talks to choose from, it gives the track chairs some options for choosing more diverse speakers out of the available pool of possibilities
14:47:29 <spotz[m]> Yeah I wasn't going to originally then I put 2 in to support the event
14:48:13 <fungi> much appreciated!
14:48:59 <spotz[m]> I kinda picked the topics based on the Okestra presentation so they'll either be much appreciated or not:)
14:49:37 <fungi> heh
14:50:18 <spotz[m]> It's all good
14:50:50 <fungi> i'm sure they'll be excited that people in other parts of the world are interested in the same things
14:51:46 <spotz[m]> I think we just keep promoting the CFP and travel support and that will help
14:52:28 <fungi> yeah, my to do list for this week is to do some broader communication about that across the openstack community
14:53:03 <spotz[m]> Sweet. Anything else you want to talk on, or you want a break before your next meeting?
14:53:24 <fungi> i don't really need a break, but didn't have anything else to cover either
14:54:56 <spotz[m]> Ok let's call it here then:)
14:55:02 <spotz[m]> #endmeeting