17:01:25 #startmeeting diversity-wg 17:01:26 Meeting started Mon Jan 6 17:01:25 2020 UTC and is due to finish in 60 minutes. The chair is spotz. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:01:30 The meeting name has been set to 'diversity_wg' 17:01:33 #topic Roll Call 17:01:45 Hi! 17:01:49 \o hi 17:02:30 Hey 17:02:52 fungi: Joining? 17:03:03 ohai 17:03:17 Sweet that's everyone I think:) 17:03:17 seems i need to update my calendar for this 17:03:41 I had to verify it was the first Monday and then figure out the correct time:) 17:03:51 me too. 17:03:56 #link https://etherpad.openstack.org/p/diversity-wg-agenda 17:04:08 Agenda for anyone interested 17:04:54 I've changed the UC meetings more into an old business and new business format, not sure we want to do that or not 17:05:20 I also updated the year. It's 2020. ;) 17:06:09 The only thing I've got on the agenda is discussing our branching out to the other OSF projects as we report to the board and not OpenStack persay. megheisler as you're here if you have anything to report on mentoring we can do that too 17:07:21 #topic Diversity for all projects 17:07:35 sure! 17:08:38 so in the agenda you ask the question, "would they like help?" 17:08:56 I can't remember if we came up with this in an official meeting or just chatting when there wasn't a meeting. But as this group as I just mentioned reeports back to the board the idea waas that after the break we should reach out to the other projects and see if they're interested and how we can help 17:09:00 was typing:) 17:09:18 maybe we'd be better first figuring out what sort of help we're talking about, or what sorts of things we currently do that are openstack-specific 17:09:49 it seems like a lot of the focus is already on general osf involvement 17:10:04 events, surveys 17:10:09 The speed mentoring is kinda more OpenStack but doesn't need to be and the survey definitely was 17:10:47 And well regular mentoring is ttoo 17:10:57 yeah, that's mostly content in both cases 17:11:07 So mentoring is easy to change we just need vollunteers from the other projects 17:11:28 At summit and as ongoing meentors 17:11:31 i'll posit they're already getting help from the osf diversity wg in a number of ways 17:12:06 Survey I don't thtink we would do an OPenStack onee again for at lelast a year but we could do one for the othter projects 17:12:58 i'd suggest it just be a general osf community survey. we can always add a question asking the respondent to list the projects in which they're involved 17:13:15 keeping in mind there's going to be a fair degree of overlap 17:13:20 And I agree we probably are already giving them help, but it might be nice to reach out and see if there's anything specific they need 17:13:26 For me I already feel very x-project in the community work I do. Actually even beyond the OpenStack Foundation. My focus has been all things Cloud Native, and especially open source. So from a community or Ambassador standpoint, I'm happy to help out where applicable. 17:13:53 but at least if the survey asks them to indicate the projects they're participating in, we can slice results along that axis to get project-specific demographics too 17:14:22 and it cuts down on survey fatigue for people participating in multiple projects 17:14:33 fungi yeah my only concern with a big joint survey is being ablle to determine what project answers came from and maintain anonymity 17:15:06 i definitely agree, outreach (asking projkects if they have specific diversity challenges they're struggling with) is a great idea 17:15:14 Even now we don't know what OpenStack projeect 17:15:47 i see, concern that a specific project or list of projects could out th eanonymity of a respondent? 17:17:05 Possibly or even when responses say there was an issue within a project we don't know which one they had that issue with 17:17:15 (by project i'm talking about osf level projects, so currently airship, kata, opensatck and zuul... maybe soon starlingx too) 17:19:01 Yeah:) But say someone fills out the survey and we get a comment that says they couldn't get code mergeed because of X or Y. We might not be able to narrow it down to say a Zuul issue vs a Kaata or OpenStack issue, similiar to how wee don't currently know if it was Kollla or OSA 17:19:22 That concern make sense? 17:19:56 Yeah, I could see where needing to know if the issue is project specific would help out in fixing it 17:20:25 yep, definitely would be an item in favor of separate surveys 17:21:16 But if we ask to many narroowing questions we risk anonymity issues. Now to bee honest without talking to thee other projects we don't know how large their communities might be 17:21:52 Could you put in a box to check that states which project that response was directed toward, on survey questions like that? 17:21:52 If it's 100 people a broader survey might have a better chance of being answered if it was combined with another group 17:22:34 I don't think we can with how we did the last survey. fungi what about that system you had set up? 17:23:20 so in favor of a single survey, we've got the deduplication of results (allowing us to have overall osf demographic numbers) and avoiding survey fatigue among cross-project participants. in favor of separate surveys is that it could be hard to map a project-specific complaint to a corresponding project/community and also combining project participation could make it harder to maintain anonymity 17:23:22 of respondents 17:24:28 #link https://docs.openstack.org/infra/system-config/survey.html#admin-survey-user 17:24:31 Yeah and of course those might be non-issues if the other projects don't want to be included ot utilize this group 17:25:23 survey.openstack.org hasn't gotten heavy use yet, i think a few folks have beta tested it for small stuff but i've not really gotten any feedback 17:25:58 I just remembered reviewing documentation for it 17:26:15 I think we wee a google form last time which greeatly limits what we can do 17:27:16 I can't imagine that a project wouldn't want to utilize this group. We're only here to help. :) 17:27:25 So my first suggestion is we get a list of contacts for the other projects from OSF and compile an email and reach out 17:28:05 Well when UC reached out they didn't want assistance, but they all have their own governance and most didn't even have users at the time 17:28:22 well, it's the osf diversity wg's mission to report on and assist with member diversity concerns within the osf. that doesn't necessarily mean project-specific diversity concerns, but it has been leveraged that way so far 17:28:45 Welll there hadn't been any ooother projects:) 17:29:03 the uc is openstack-specific in the same way that the tc is opensack-specific. they're delegated similarly in the bylaws 17:30:02 so i think keeping the uc focused on openstack is reasonable in the same way that not imposing a common tc over all osf projects was reasonable 17:30:14 Another benefit of reaching out and getting buy in is hopefully new members to this group:) 17:30:44 yep! 17:31:48 as i said, i like the idea of asking project communities what they need help with, but i also think the osf diversity wg shouldn't try to make its general osf activities specific to particular projects 17:33:00 enlisting help from additional projects in general osf activities would be good. making additional silos maybe not 17:33:43 I don't think it was ever intentional I think it just wasn't planned appropriately for when the other projects joined 17:34:57 So we get some contacts from Allison and Jimmy and reach out to them welcoming to the OSF and lletting them know we exiist to help all project aas part of OSF and not OPenStack and trry to get follkls to join the efforts 17:35:23 yep, i didn't mean to suggest anything is being done wrong, just that new project-specific tasks may not be within the scope of the wg 17:35:37 I so can't type;( I think I need a new keyboard again 17:35:50 your keyboard is incompatible with 2020 17:35:53 We won't know until we aask what they need 17:36:28 Anything on this or are we in agreement for the next steps? 17:36:44 i'm cool 17:37:07 SWDevAngel and megheisler? 17:37:24 yep, I think that is all good 17:37:24 Just want to make sure I'm keeping us on track with time:) 17:37:47 Yes, I'm fine. Like I said above, from a community standpoint, I'm already cross-project. I've done meetups on Zuul, Kata, etc. Happy to always help wherever. :) 17:38:11 Ok cool:) 17:38:22 #topic Mentoring Update 17:38:28 You're on megheisler:) 17:38:33 Great! 17:39:01 So like I dropped in and said once I was out of commision for a while because of health stuff 17:39:17 unfortunately the mentoring effort seems to have gotten dropped a bit 17:39:48 but with the new year I am contacting a few people who expressed interest in mentoring/being mentored 17:40:03 just to see if they are still interested 17:41:32 but that's the current status of thing, if anyone has any thoughts or suggestions please let me know! 17:41:37 Great thanks, and hopefully with the outreach we were just tallking about we'lll be ablle to either start or maybe merge in other efforts 17:42:28 yeah, I'd be interested to find out what sort of mentoring individual projects have done if any 17:43:32 that'll be great 17:44:31 In terms of a mentoring plan I am going to wait to see how many people respond back 17:44:53 Yeah I'm not sure if anyone is doing something besides possibly Oatreachy? 17:45:30 Yeah and we might need to do a more formal push to get things going again 17:45:46 yeah, that makes sense 17:46:44 Sometimes just seeing it 'fresh' gets new interest 17:47:04 We have just under 15 minutes. Anything on this? 17:47:12 OK, thanks, I'll work on that. 17:47:18 Thats all from me 17:47:45 #topic Open Discussioon 17:49:51 Anyone have anything else or we get 10 minutes back 17:49:59 Just a quick note (again, from a community standpoint). 17:50:16 i brought up with osf event peeps that more specifically incorporating community diversity topics in the agenda/planning for the vancouver ptg/opendev in may thing would be appreciated, and will try to make sure i keep on top of that as organization around content begins to crystalize 17:50:44 Great thanks fungi 17:51:08 I've been noticing more mainstream publications actually taking an interest in how these big communities are built and sustained. I've been interviewed in different circles than usual lately. Did you see the piece that ran in Forbes last month? 17:51:16 https://www.forbes.com/sites/oracle/2019/12/10/kubernetes-hungry-businesses-recruit-to-fill-their-skill-gaps-at-kubecon/#3a4950117d41 17:51:59 My point is that YES, people are understanding better the relationship of community to open source (and other) projects. AND it's a great place to point out the importance of diversity in building these communities. 17:52:58 that's awesome 17:53:03 Cool 17:53:23 (and no, i hadn't noticed that article) 17:53:35 thanks for pointing it out! 17:53:54 Yeah, totally. I did this Marketing Influencer thing, and also theCUBE last fall. I've been doing this community thing for God knows how long but it seems now that it's finally sinking in mainstream, how it all ties in. 17:53:59 I hadn't seen the article, great piece 17:54:55 Yeah I think communities as a whole are getting the idea of diversity matters and trying to do the right thing fromo the start or early at least 17:55:04 I think it was pushed to Forbes by a blogger at Oracle. So that's another thought. Not sure who runs that kind of stuff for the OpenStack Foundation but it'd be good to let them know that mainstream business pubs are interested in stories like this, and they can help place them. 17:55:44 That's a good point 17:55:56 Actually, maybe that's a point for Robert Cathey. I think he still does the PR outreach for the Foundation. I can ping him. 17:56:14 yep, he's sho i'd suggest 17:56:21 er, he's who i'd suggest 17:56:38 Got it. Will do. 17:56:43 thanks again! 17:57:03 he's really the one with all the contacts 17:57:22 Thanks SWDevAngel 17:57:32 Ok anything else? 17:57:43 Yes. I know he saw the article cuz he tweeted it out, but I'll talk with him to make sure he made the connection that he could help place an article like this for the OpenStack Foundation projects and communities. 17:57:58 That interview was done at KubeCon. Something similar could be done at the next Summit. 17:58:09 Nope, I'm good. Happy New Year everyone!!!! 17:58:16 nothing else from me 17:59:02 #endmeeting