Monday, 2019-06-03

*** altlogbot_2 has quit IRC04:36
*** altlogbot_0 has joined #openstack-diversity04:37
*** janki has joined #openstack-diversity04:38
*** eglute has quit IRC07:41
*** irclogbot_0 has quit IRC07:44
*** irclogbot_2 has joined #openstack-diversity07:44
*** eglute has joined #openstack-diversity07:53
*** jchhatbar has joined #openstack-diversity08:20
*** janki has quit IRC08:20
*** jchhatbar has quit IRC08:40
*** janki has joined #openstack-diversity08:40
*** janki has quit IRC10:57
*** janki has joined #openstack-diversity10:58
*** janki has quit IRC11:33
*** janki has joined #openstack-diversity11:59
*** janki has quit IRC12:13
*** diablo_rojo has joined #openstack-diversity13:36
*** irclogbot_2 has quit IRC15:10
*** altlogbot_0 has quit IRC15:11
*** irclogbot_3 has joined #openstack-diversity15:11
*** altlogbot_2 has joined #openstack-diversity15:11
megheislerunfortunately I won't be able to attend the meeting today. I'll check back after to see what I missed but I know we want to get the next mentoring effort going and I still want to help with that16:01
fungithanks megheisler! we'll have meeting minutes and a log at least which you can read at your leisure16:06
spotzThanks megheisler I'll also try to get an introduction email out to everyone who was interested in helping with that. Just been busy with work and RL16:23
spotzWhich is why I'm not attempting to run it...16:24
diablo_rojospotz, happy to help in any way I can :)16:41
spotzdiablo_rojo: I'll include you on the email16:47
*** SWDevAngel has joined #openstack-diversity16:47
diablo_rojospotz, sounds good16:48
spotz10 minute warning16:50
SWDevAngelI’m here. :)17:00
apriceo/17:01
fungialoha17:01
spotz#startmeeting diversity-wg17:02
openstackMeeting started Mon Jun  3 17:02:20 2019 UTC and is due to finish in 60 minutes.  The chair is spotz. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: diversity-wg)"17:02
openstackThe meeting name has been set to 'diversity_wg'17:02
diablo_rojoo/17:02
spotz#topic Roll Call17:02
*** openstack changes topic to "Roll Call (Meeting topic: diversity-wg)"17:02
cmurphyo/17:02
spotzAgenda:17:02
spotz#link https://etherpad.openstack.org/p/diversity-wg-agenda17:02
fungi"roll call" makes me feel like i'm a mouseketeer17:03
* SWDevAngel waves17:03
spotzAnd while it's in the agenda the link for the CoC discussion is https://etherpad.openstack.org/p/diversity-wg-coc17:03
spotzfungi I used to have ears:)17:03
spotzWe'll get going even if more people show up today17:04
spotz#topic Summit17:04
*** openstack changes topic to "Summit (Meeting topic: diversity-wg)"17:04
spotzOverall I think we had a good summit as far as attendance at sessions and some really good conversations.17:05
SWDevAngelAgreed. But I was only there for the last day and a half.17:05
fungiwas good seeing everyone nonetheless17:06
spotzFrom the mentoring BoF we had 2 people interested in helping petevg and megheisler. And then one of Martial's coworkers17:06
SWDevAngelAgreed. Great community.17:06
fungiyes, new faces!17:06
spotz@action spotz to email the interested folks to make introduction, including diablo_rojo to assist17:06
spotz#action spotz to email the interested folks to make introduction, including diablo_rojo to assist17:06
spotzThat's better:)17:06
spotz#link https://etherpad.openstack.org/p/DEN-diversity-sessions17:07
spotzThis was the etherpad for the sessions17:07
spotzShoot I have IRCs and no emails for folks:( megheisler if you could email me at amy@demarco.com I'd appreciate it and I'll track down Peter in the Horizon channel I think I saw him in their PTG room17:08
spotzI went over the survey results and Jimmy has put them online officially vs in my GitHub if anyone wants to see them17:09
fungiit sounds like getting something like "mentorship" added as a top-level icon on the community portal ought to be doable17:09
spotzfungi: Cool, we just need to have something for it to go to:)17:09
fungi#link https://docs.openstack.org/contributors/common/mentoring.html17:09
fungiseems like that ought to be a decent initial placeholder?17:10
spotzThat will work!17:10
spotzOur stickers were out at registration, though didn't see many people with them but they were there!:)17:10
fungii heard some folks in the session say they didn't notice them at registration, but not sure how to make them more visible17:11
spotzfungi: Maybe stick some on the outside of the containers? I had to ask if they were there17:11
fungithat could help17:11
fungiif money were no object we'd just include one of each along with every badge, but... $$$17:12
spotzSpeed Mentoring had a nice turnout, I snagged 6 people out of a waitlist line next door or as we had plenty of food17:12
SWDevAngelWhich stickers?17:12
fungiSWDevAngel: pronoun stickers17:12
spotzYeah and even then would people notice them. What he said17:13
SWDevAngelAhhhh. Right. I missed those too but I registered a day late.17:13
SWDevAngelWhat they did at KubeCon is they had the person who registered you actually point you to them and ask you to put one on. It was pretty effective. They also had the color-coded do not disturb or talk to me stickers.17:13
spotzYeah or LF has a table next to registration with all the stickers at events. But having them there was a good start:)17:14
SWDevAngelYes17:15
spotzDiversity Lunch had a nice turnout, the IBM presentation was a good kickoff and I think well received17:15
spotzAnd new faces there as well17:15
SWDevAngelAgreed and it was great to have Jennifer Cloer back.17:16
spotzAny thing else on Summit? We have a few items I know we need to get to17:16
fungisorry i had to miss diversity lunch and speed mentoring for other obligations, but glad to hear there was a good turnout17:16
SWDevAngelAnd the screening17:16
spotzYeah I had UC at the same time as screening so missed that, and we moved the survey results as it was at the same time:(17:16
spotzI'm going to bump the WoO stuff over the CoC as I think it'll be quicker17:17
spotz#topic WoO ML and linked in17:17
*** openstack changes topic to "WoO ML and linked in (Meeting topic: diversity-wg)"17:17
SWDevAngelNicole did a good job hosting it.17:17
spotzSo I think the Diversity mails have always been under the FOundation list as to be open and as we're technically a WG under the Board and not UC or TC. aprice this was your topic if you want to lead it17:18
apricesure17:18
apriceso we have a linkedin group that has several hundred people and a WoO mailing list. With the recent shift to a broader sense of diversity, one of my questions was should we rename the mailing list?17:19
spotzThat's one reason I just gave that little blurb of history:)17:20
fungii was just browsing the list archive, and for at least the past year (i haven't gone back any farther yet) it looks like it's been used exclusively for announcements17:20
spotzfungi: And most are probably from me:)17:20
apriceThe linkedin group has 750 members in it, but is rather old. we have not posted in it for some time. My recommendation was going to do a last post that points to official OSF diversity initiatives like this WG and then close the group so it's not another channel to monitor.17:20
fungispotz: yep, a vast majority of them ;)17:20
apriceand people can get engaged in the right places17:20
spotzaprice personally I have no issue of doing that with LinkedIn but I'm not the best LinkedIn user:)17:21
diablo_rojoSounds like a good plan to me for the linkedin17:21
spotzAs far as the mailing lists if we did rename it might lead to more discussion as I personally don't want to spam the Foundation list, but at the same time would we be as open17:21
apriceyeah, my biggest concern is someone who is genuinely interested in getting involved, finds that group because it has good search, but then isn't able to find it17:21
diablo_rojoand a rename of the ML makes sense to me too17:22
fungithese sorts of announcements seem like they'd also be right at home on the foundation ml, to me17:22
aprice+117:22
spotzWould it be worth renaming and then announcements to both lists as the volume is so low on them?17:22
spotzAnd we'll do 2 polls, 1 for linkedin and 1 for the ML once we're ready as they're 2 topics17:23
fungiif anything, posting announcements about diversity-related topics to the general foundation ml raises visibility of them as something we think everyone should be concerned about, and not just some fringe effort you need to subscribe to another place for information on17:24
apriceyeah and i think that should be something we encourage for all WGs and SIGs. would probably help new folks find out how to get involved easier17:25
fungithe wg is chartered by the board for a reason, so i would consider that an indication they think it's an important foundation-level area of interest17:25
spotzfungi: So you're in favor of archiving WoO and staying as is? Just want to be clear17:25
fungiarchiving the women-of-openstack ml and moving future announcements of that nature to the foundation ml17:26
spotzwhere they are now:)17:26
fungiyeah, they're already being posted there as well17:27
spotzOk anyone have any other thoughts on this?17:27
fungibasically the volume of messages on foundation is within the same order of magnitude, so there's not much reason to echo this subset of announcements to a second ml17:28
cmurphysounds good to me17:28
spotzfungi: If we seem like we need more for conversations we can always make a new list. But yeah it seems to be just me with meetings and summit related announcemtns17:29
spotzOk making the poll17:29
fungithe alternative of making it clear that the women-of-openstack list is an announcement-only list and discussion should happen on foundation seems like a reasonable alternative17:29
fungialso, not the reason i'm arguing against, but renaming a mailing list is not easy and has a tendency to be disruptive to existing subscribers regardless17:29
SWDevAngelYes. Let’s streamline as much as possible.17:29
spotz#startvote Archive the WoO mailing list and continue using the FOundation list for Diversity? Yes No Abstain17:30
openstackBegin voting on: Archive the WoO mailing list and continue using the FOundation list for Diversity? Valid vote options are Yes, No, Abstain.17:30
openstackVote using '#vote OPTION'. Only your last vote counts.17:30
spotz#vote yes17:30
aprice#vote yes17:30
fungi#vote yes17:30
SWDevAngel#vote yes17:31
fungias an aside, i'm happy to assist in the technical steps for shutting down the ml17:31
cmurphy#vote yes17:31
diablo_rojo#vote yes17:31
fungijust did that recently for a bunch of technical lists on the same server17:31
spotzfungi: Thanks, I'll poke about and ping:)17:31
fungiat your convenience17:32
spotz#endvote17:32
openstackVoted on "Archive the WoO mailing list and continue using the FOundation list for Diversity?" Results are17:32
openstackYes (6): spotz, fungi, SWDevAngel, diablo_rojo, aprice, cmurphy17:32
spotzAnd before I put up the poll for linked in just want to make sure I'm clear. We will be shutting that down with a final post sending people to this meeting and the Foundation list? Or something similar17:33
apricecorrect - probably the wiki where it lives in one place17:34
apriceand we can leave it up for let's ay 6 weeks. and I can post multiple messages in case folks miss it17:34
spotzaprice: Ok and we can make sure it's up to date before we send people there:)17:34
apriceperfect17:34
spotz#startvote Archive the WoO LinkedIn group and send a message with follow-ups for people to join ML, meeting and checkout the wiki? Yes No Abstain17:35
openstackBegin voting on: Archive the WoO LinkedIn group and send a message with follow-ups for people to join ML, meeting and checkout the wiki? Valid vote options are Yes, No, Abstain.17:35
openstackVote using '#vote OPTION'. Only your last vote counts.17:35
spotz#vote yes17:35
aprice#vote yes17:35
fungi#vote abstain17:36
cmurphytbh i don't participate in the linkedin group so i have no opinion on its future17:36
cmurphy#vote abstain17:37
fungi(having never used linkedin, i'm happy to defer to others on this one, don't feel i can reasonably gauge)17:37
spotzcmurphy: I've seen maybe 1 message in years:)17:37
spotzBut like I said I'm not the best LinkedIn user17:37
spotzWe could always poke it with a we're think of doing.... and see if anyone even replies17:38
apriceyeah, the posts are largely irrelevant17:38
fungimy only exposure to linkedin is training invites from it into my personal spam detector17:38
apriceok - I can take that action of posting that it might be something we do17:38
apriceand report any feedback / concerns17:39
spotz#vote abstain17:39
spotzI'll officialyy abstain so we don't have a good vote and we'll do that step first17:39
spotz#endvote17:39
openstackVoted on "Archive the WoO LinkedIn group and send a message with follow-ups for people to join ML, meeting and checkout the wiki?" Results are17:39
fungimakes sense17:39
openstackYes (1): aprice17:39
openstackAbstain (3): cmurphy, fungi, spotz17:39
spotz#action aprice to Poke the linked in group and see if there's any response then we can decide to retire it17:40
fungii'm perfectly happy for aprice to do whatever she thinks as best on this17:40
spotzI think we'll retire it after the poke:)17:40
spotzAnything else on this?17:41
apricenope - thanks!17:41
spotz#topic CoC review17:41
*** openstack changes topic to "CoC review (Meeting topic: diversity-wg)"17:41
spotzAeva brought to our attention during sessions that our CoC is out dated and some of the wording might put people off from reporting things17:42
fungi#link https://www.openstack.org/legal/community-code-of-conduct/ current osf community coc17:44
spotzThe Django CoC we were based on has been updated and I've included a link to that on the etherpad I've made and linked to17:44
spotzfungi: Yep I cut and pasted it into the ether so we could mark it up as we wanted to:)17:44
spotzAny changes we make will need to go through the OSF and most likely they're legal17:45
fungithough the summit code of conduct includes the same phrases aeva brought attention to, and it claims to be based on the pycon conference coc17:45
fungiso odds are if we alter those bits of one, we'd do the same with the other17:45
apricewas there a particular section or phrases that were particularly off-putting?17:45
spotzSo Summit one was good and regular one was bad?17:45
apriceand yeah, it would definitely need to go through our legal team17:45
spotzOr both are bad?17:45
fungiboth have the same phrases aeva mentioned17:45
spotzOk so we'd need to update both17:45
fungiso that section, at least, is effectively identical17:46
fungi#link https://www.openstack.org/summit/shanghai-2019/code-of-conduct/17:46
fungifor reference17:46
fungithe response procedure is similar in both cases17:46
spotzaprice using will vs may was a big one as someone may want to report but have it go no further17:49
fungiit sounds like we do need to be clear though that you should not report an incident to osf staff unless you're okay with the idea that they may be legally obligated to follow up on some kinds of incidents17:50
apriceyeah, that was what i was about to say. even if someone doesnt want it reported, we may be legally obligated to17:50
apriceso it's definitely a fine line17:51
spotzI think using like complaintant and offender might be older wording as well17:51
fungicases like that could i suppose start with a hypothetical probe, but i'm unsure how to outline that sort of process in plain english17:51
spotzHere's their updated reporting17:52
spotz#link https://www.djangoproject.com/conduct/reporting/17:52
spotzAnd this is definitely not something we're going to solve in one meeting but maybe put aside time for a bit each upcoming meeting like we did the survey and see what we can come up with17:53
fungito be fair, i don't see anywhere in the django coc reporting guide which says that you can ask them not to follow up on a report17:54
fungibut also, one major difference i see is the scope17:54
spotzI think it's the use of may17:55
diablo_rojo(5 min left)17:55
fungiour coc includes reporting guidelines and process for the response, whereas django's just has the first thing and then an explanation of what to expect from the process but not the process itself17:55
spotzMaybe we can get Aeva to join us next meeting?17:56
fungi#link https://github.com/django/code-of-conduct/blob/master/reports.md17:56
fungithat seems to be the equivalent for them17:56
apriceyeah, i think that showing exact places, because i think that there are places where ours tries to add things like "if any" noting that sometimes no additional action is taken17:57
apriceso it may be worth going through and highlighting the issues and doing it all in one round so we can see what changes are needed / possible17:57
spotzIf it's as simple as will/may and toning down complainant/offender type wording is different then us throwing things out and redoing17:57
fungiwe could be like them if we moved the process somewhere else and replaced it in the coc text with a brief bit which sets expectations17:57
spotzI'll ping Aeva at least for some clarification if they can't join in17:58
spotz#topic open discussion17:58
*** openstack changes topic to "open discussion (Meeting topic: diversity-wg)"17:58
apricei think that will / may would be a hard change to accomplish fwiw17:58
spotzI'll skip Grace Hopper except to say we've accepted the invitation to be there and we'll be doing something Horizon related I hope with resources donated by City Network17:59
spotzI haven't actually tried doing what I'm hoping to do yet:)17:59
fungialso one other significant difference is that django's coc response handling is done by a committee of community volunteers, not a legal entity, so they may not be legally obligated to follow up on things the osf is17:59
spotzAnyone have anything for the last minute?17:59
spotzfungi: good point17:59
spotzOk thanks for coming everyone, we'll continue at least the CoC stuff next meeting!18:00
spotz#endmeeting18:00
*** openstack changes topic to "Please review the survey at https://www.surveymonkey.com/r/OpenStackDiversity and let spotz and/or aprice know if there's anything that needs updating per http://eavesdrop.openstack.org/meetings/diversity_wg/2018/diversity_wg.2018-06-18-19.00.log.html"18:00
apricethanks spotz!18:00
openstackMeeting ended Mon Jun  3 18:00:48 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/diversity_wg/2019/diversity_wg.2019-06-03-17.02.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/diversity_wg/2019/diversity_wg.2019-06-03-17.02.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/diversity_wg/2019/diversity_wg.2019-06-03-17.02.log.html18:00
fungigreat meeting, thanks for chairing spotz!18:00
spotzMy pleasure:)18:05
petevgspotz: ... and I'm still interested in helping, even if I managed to forget about today's meeting (I was taking a lunch break and playing some games with the kiddo -- just sat back down at my desk and saw the conversation). I'll try to make the next one!18:05
spotzpetevg: No prob, can you email me you email address so I can do an intro/organizing email? amy@demarco.com18:06
petevgspotz: sent!18:07
spotzThanks:)18:08
petevgnp!18:08
diablo_rojoThanks spotz!18:10
*** altlogbot_2 has quit IRC18:43
*** altlogbot_0 has joined #openstack-diversity18:44
*** altlogbot_0 has quit IRC19:21
*** altlogbot_3 has joined #openstack-diversity19:26
*** SWDevAngel_ has joined #openstack-diversity20:07
*** SWDevAngel has quit IRC20:15
*** eglute has quit IRC20:15
*** SWDevAngel_ is now known as SWDevAngel20:15
*** eglute has joined #openstack-diversity20:16
*** SWDevAngel has quit IRC20:17
fungijamesmacarthur has provided us with a lightbulb at https://www.openstack.org/community/ now... marvel at its wonder!20:26
*** altlogbot_3 has quit IRC20:45
*** diablo_rojo has quit IRC22:46

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!