Thursday, 2015-11-12

*** oomichi has joined #openstack-diversity00:34
*** rolandchan has joined #openstack-diversity05:46
*** gb21 has joined #openstack-diversity06:39
*** sc68cal has quit IRC06:45
*** rolandchan has quit IRC07:57
*** gb21 has quit IRC08:22
*** sc68cal has joined #openstack-diversity08:31
*** gb21 has joined #openstack-diversity08:34
*** oomichi has quit IRC10:48
*** rolandchan has joined #openstack-diversity13:29
*** KLevenstein has joined #openstack-diversity14:27
*** spotz_zzz is now known as spotz15:02
*** rolandchan has quit IRC16:07
*** rolandchan has joined #openstack-diversity17:57
eglute#startmeeting diversity18:00
openstackMeeting started Thu Nov 12 18:00:09 2015 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
openstackThe meeting name has been set to 'diversity'18:00
egluteHello Everyone! Raise your hand if you are here for the diversity meeting o/18:00
eglute#link https://etherpad.openstack.org/p/OpenStackDiversity.1618:00
*** Dan_Fineberg has joined #openstack-diversity18:00
rolandchanI am18:01
egluteHello rolandchan!18:02
Dan_Fineberggood morning18:02
rolandchanHiya18:02
spotzHey guys18:02
egluteHello Dan_Fineberg!18:02
egluteEveryone: please review the agenda: https://etherpad.openstack.org/p/OpenStackDiversity.1618:02
eglute#topic work plan18:03
eglutewhen we started this working group, we came up with a work plan, and now we need to re-evaluate it and see if it needs updating18:04
eglute#link https://docs.google.com/presentation/d/1I0KJEzqdpwFMWPX-G7H-Arx4uCHDkR7E76kttlZfNZU/edit#slide=id.p318:04
eglutewe have done some of the things on the plan, mainly we sent out the survey.18:05
Dan_FinebergAre the categories and preiorities agreed by the key decision makers?18:06
eglutethe survey showed us some common issues, but of course it was not quite what we were expecting18:06
spotzeglute We discussed resending the survey out at summit, should we maybe schedule doing that as the next step?18:06
eglutespotz i dont think it would be good to resend it soon after the summit. Perhaps before the next one? unless you have good reasons for sending it out again?18:07
egluteDan_Fineberg yes, they were18:07
Dan_Finebergcool--then I presume the survey did not generate sufficient response?18:08
rolandchanI don't think we need as much detail as we got from the survey very often18:08
spotzeglute mainly to see if we get more responses. There was one person atleast in the working session that said they didn't get it18:08
egluteWe got enough responses, they were not what were expecting :)18:09
Dan_Finebergcan we set the base lines from the data we got back?18:09
eglutewe can set some. Also, we got some clear blockers for people to participate in the community18:09
eglutebut they are not specific to any particular group, besides being new to openstack18:10
Dan_Finebergperhaps that should be dealt with after the base lines are set, when we consider the "desired state"...18:10
eglutespotz i dont think that would work, the system said it went to 32K people. A lot of people filter their emails, so we have no way of knowing what really happened to that particular person18:11
spotzok18:11
egluteDan_Fineberg I agree, we should come up with desired state :)18:11
Dan_Finebergan analysis of the base lines for each category would be a good start18:12
egluteAgreed, we need to share the results of the survey. I will take that as an action item18:13
rolandchanThere are two sides to desired state: population distribution, and the satisfaction rating.18:13
eglute#action eglute will work on sharing the survey results with the community18:13
Dan_Finebergagree that "quantity" and "quality" metrics make sense...18:14
rolandchanOn the population side: we need to work on getting a more diverse overall population and also on enabling that population to "progress though the ranks", ie into leadership positions.18:15
egluteright, so how do work on outreach?18:15
Dan_Fineberga PR effort would be a good start, getting feature stories in the Foundation blog and magazine, for example...18:16
rolandchanFor geographic diversity, we need the diversity message to be the first thing anyone says. We have lots of events going on all the time, but the "join the community" message is not the highest priority18:17
egluterolandchan what is the first message people hear now?18:18
Dan_Finebergcan you clarify the audience you're referring to?  New recruits?  Existing members?  Other?18:18
rolandchanDepends: meetup groups talk about different thingsneach meeting. The regional meetings have different tracks.18:18
spotzSo something like pictures of a diverse group of people and then a tag line to encourage joining?18:20
Dan_FinebergMaybe we should take an audience-by-audience approach:  existing members; prospective members; by-geo?18:20
rolandchaneglute: something like that. We probably need a guide for them  to use18:21
eglutefor new people, the ramp up to use/code/run openstack is also challenging, that is something that needs closing18:21
egluterolandchan what do you mean by a guide18:21
Dan_FinebergIs there any meaningful info to offer besides goals on how diverse we want the community to be?  Maybe social gatherings?  Dispute resolution channels?18:22
rolandchanSomething asking them to deliver a particular message, and some content. Slides etc.18:22
egluteI would also propose that when there is something like OpenStack Day, the organizers offer some number of free diversity passes18:23
rolandchanBasically some marketing collateral.18:23
egluterolandchan can you work with the foundation on getting some marketing collateral done?18:24
rolandchanYes! Any hints we can provide as well.18:24
rolandchanSure.18:24
eglute#action rolandchan will work with the foundation on getting some marketing collateral done18:25
eglutethe next big issue is onboarding new people18:25
eglutenot enough to join the community, need to enable ways to participate.18:25
eglutethis is larger than this WG though18:25
Dan_Finebergmaybe a way to get more "cores"?18:26
rolandchanWe need to liaise with the TC on mentoring. What is/isn't possible etc.18:27
eglutemore cores too, but even getting started is a big issue18:27
Dan_Fineberga step-by-step training offering for becoming a core reviewer would be good for may reasons...18:27
Dan_Finebergmany reasons, that is..18:27
egluteyes, we do have someone from TC we can work with. Need to make sure he knows about these meetings :)18:27
eglute#action eglute to talk to Flavio about diversity meetings18:28
rolandchanI think we need to get detail from the foundation on what their plans are. There is a lot of money set aside for "technical work", we need to ensure that the feedback from the survey is included in the requirements for that work.18:29
egluteDan_Fineberg I agree! however, people need help just getting started too. For example, Nova has a really good guide on how to get started and their whole process. the difficulty there is the size of the project and people not knowing where to start/find the start guides18:29
egluterolandchan +118:29
Dan_Finebergmaybe we have more than one offering:  getting started for newbies, and moving up for older hands...18:30
spotz+1 dan_fineberg I like that18:30
rolandchanYep. Need both.18:30
egluteyes, all levels could use more help + clarity18:31
Dan_Finebergperhaps a 3rd would be "leadership" for senior folks...18:31
egluteso the question is, how much should the Diversity Working Group drive of this? This is such a huge area, and way more than we can do.18:32
Dan_Finebergcan we piggy-back existing HR programs for training and onboarding?18:33
rolandchanIt needs to be a distributed system :)18:33
rolandchanThere's no HR for members18:33
Dan_FinebergDo we have a list of exosting programs that we could influence?18:34
eglutei think we would need to work with the foundation here. there are some programs,18:34
spotzI can see us providing overall guidance and suggestions like the 'come join the community' mentioned earlier and working to come up with guides?18:34
rolandchanPerhaps we take the best of what is out there (Nova perhaps) and ask all the projects to aim at that level.18:34
Dan_FinebergI'm thinking we could target whatever  existing programs there are for onboarding, training, and executive development...18:34
egluteone is Outreachy, but it cannot support a lot of people18:35
Dan_Finebergmaybe we recruit a member from that program to join us, and then extend our efforts through their program...18:36
eglutewe can look into it. also, see what else has been successful18:37
rolandchanTraining is a good one: there is training on being a contributor. Maybe it should be run through i18n.18:37
egluterolandchan do you have a link to that?18:38
rolandchanUm..18:38
rolandchanhttps://wiki.openstack.org/wiki/OpenStack_Upstream_Training18:39
rolandchanThere were some sessions at summits18:39
rolandchanBut perhaps a webinar format18:40
spotzFrom talking to folks I think the upstream training was held on Sunday before summit18:40
egluteright, looks like it is before summit next time as well.18:40
Dan_FinebergIf we had a member from the training team in this team, they could help us understand what format works best.  Then we could pur in the content...18:41
eglutenot sure if it can be scaled18:41
rolandchanIt we can convert it to a youtube video it'll scale :)18:41
rolandchanI haven't actually seen the content though18:42
egluteright, i meant in-person at the summit18:42
Dan_Finebergthen send an email to the community with the YouTube link...18:42
eglutehere is the outline: http://docs.openstack.org/upstream-training/18:42
egluteone thing that we saw from the survey is that people have hard time finding the information, even when it is available18:42
egluteso to address that issue, we would need to talk to the docs/foundation people see what can be done to make it easier for people find the info18:43
rolandchanThis sort of thing should be part of the guides we send out in the previous action point18:44
eglutei think the issue is that there is the openstack site, teh wiki, mailing lists, IRC. lots of different channels18:44
egluteyes.... but how will they find it :)18:44
egluteif they are not on the mailing list, or filter and dont read everything?18:44
Dan_Finebergif we use existing online repositories like the Foundation's online slide index, then we can send links to people via multiple channels:  email, IRC chats, etc.18:45
spotzYeah not sure I would have thought to search for upstream training to get how to contribute18:45
rolandchanSo we need to look at rationalising the user experience.18:46
Dan_FinebergWe should do this as an active campaign rather than a pssive posting of content, in my humble opinion...18:46
rolandchanOrganising the content to have a simple entry point and then pushing that entry point out all the channels18:46
Dan_Finebergyes!18:47
rolandchanAnd do that push repeatedly18:47
eglute+118:47
spotz+118:47
egluteso, who would like to take this as an action item?18:47
eglutethough we might all need to own it18:47
rolandchanFirst step would be to identify all the bits of content.18:48
Dan_FinebergI can help with content editing, wordsmithig, etc.18:48
eglutethanks Dan_Fineberg that would be helpful18:48
rolandchanI think that can be a shared task. If we have an etherpad to list it all out, we can all do it.18:48
egluterolandchan that is a huge task18:48
rolandchanYep. That's basically the core of problem.18:49
eglutealso, we need to make sure we dont loose track that we are trying to increase diversity... ideally, we work with the community/foundation to help us18:49
rolandchanI think we can work on the common stuff. Each project has their own content.18:50
rolandchanAnd we are starting to build a list of thing we need from each project.18:50
eglutetrue18:50
eglutethe last item on today's agenda is the code of conduct updates.18:50
eglutespotz do you remember who owned that as an action item? was it you?18:51
spotzcpallares18:51
egluteah ok18:51
eglutewould you be able to work with her on it?18:51
spotzI just tend to know what's going on with it:) She was going to get with Carol last I heard18:51
cpallareso/18:52
egluteJonathan Bryce has asked for more context behind the proposed changes. He would like to understand what's behind the change, so he can both understand and determine if there are other places changes are needed related to the code of conduct change.18:52
spotzsweet!18:52
egluteoh hi Cindy!18:52
cpallaresHow do I contact Jonathan?18:52
egluteyou are here just in time, to do work! :D18:52
cpallaresThrough the mailing list?18:52
cpallareshaha18:52
egluteemail! I will get it to you18:52
cpallaresOk18:52
rolandchanWe're clear on what needs to be said to him? AFAIK its pretty straightforward18:53
cpallaresrolandchan: Yeah18:53
rolandchanOk cool18:54
cpallaresrolandchan: I think I have an email on my drafts somewhere18:54
eglutecool! thank you cpallares18:55
eglutewe have 5 more minutes, anything else?18:55
rolandchanI'll take an action to start on listing the onboarding content. Will distribute a link to the etherpad18:56
eglutethank you rolandchan!18:56
eglute#action rolandchan will take an action to start on listing the onboarding content. Will distribute a link to the etherpad18:56
eglute#action cpallares will email jbryce regarding code of conduct18:57
egluteThanks everyone! we have a lot to do...18:58
spotzrolandchan if you need a hand just ping me18:58
eglute#endmeeting18:58
openstackMeeting ended Thu Nov 12 18:58:51 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/diversity/2015/diversity.2015-11-12-18.00.html18:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/diversity/2015/diversity.2015-11-12-18.00.txt18:58
openstackLog:            http://eavesdrop.openstack.org/meetings/diversity/2015/diversity.2015-11-12-18.00.log.html18:58
rolandchanWill do18:58
rolandchanThanks spotz18:59
egluterolandchan i have spotz email if you need it!18:59
rolandchanCool.18:59
*** Dan_Fineberg has left #openstack-diversity18:59
rolandchanBye everyone. Time for a quick nap.18:59
egluteBye!18:59
spotznight rolandchan!19:00
*** spotz is now known as spotz_zzz19:20
*** spotz_zzz is now known as spotz19:21
*** spotz is now known as spotz_zzz19:25
*** spotz_zzz is now known as spotz19:25
*** rolandchan has quit IRC21:07
*** KLevenstein has quit IRC23:15
*** spotz is now known as spotz_zzz23:56

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