Open Stack

OK, I took the conversation to the Foundation mailing list. Please feel free to comment there or in the etherpad if you are interested in participating:

http://lists.openstack.org/pipermail/foundation/2016-June/002396.html

If it seems like most folks agree with the proposed changes, we’ll get this in front of the Board before the meeting next week. If it seems like there’s more discussion to be had, we’ll defer to a future meeting.


> On Jun 19, 2016, at 5:43 PM, Lauren Sell <lauren at openstack.org> wrote:
> 
> Hi Michael,
> 
> I made a few updates to the modified version in the etherpad:
> 
> - Added back in the “respect the election process” bullet, because it’s important that we be explicit about elections in the CoC
> - Added the reporting guidelines, based very closely on the process we developed for the Summit (with help from the Ada Initiative and based on the Python conference CoC a few years ago)
> 
> https://etherpad.openstack.org/p/CoC <https://etherpad.openstack.org/p/CoC>
> 
> We have 10 minutes on the agenda at the June 28th board meeting to discuss, which means we should ideally get proposed updates in front of the board to preview as soon as possible. 
> 
> I think this version is ready to socialize for community feedback on a broader mailing list. I know the Diversity Committee was interested in the project and primarily uses the Foundation mailing list, so that seems like the best forum for them to also weigh in.
> 
> Would you like to take the lead or would you prefer I send it out?
> 
> Thanks,
> Lauren
> 
> 
>> On Jun 16, 2016, at 5:51 PM, Lauren Sell <lauren at openstack.org <mailto:lauren at openstack.org>> wrote:
>> 
>> Hi Michael,
>> 
>> Sorry I missed your email last week while I was traveling. The next steps you mentioned sound good to me, and you should feel empowered to move forward. I'm out of the office tomorrow but can dig into the outstanding details around reporting protocol next week.
>> 
>> Like you said, I think the next steps are to socialize the edits with the community (probably foundation and community mailing lists) and then present the updated version to the board for approval. I'm happy to help arrange the latter, and will reach out now to see if there's room in the june 28th meeting.
>> 
>> Thanks for pushing on this. I agree it's important to get across the finish line!
>> 
>> Thanks,
>> Lauren
>> 
>> 
>> On June 16, 2016 5:19:51 PM Michael Krotscheck <krotscheck at gmail.com <mailto:krotscheck at gmail.com>> wrote:
>> 
>>> Hey everyone!
>>> 
>>> I've reached out to Lauren and Cindy on this issue to offer my help but haven't gotten a response. Given the tricky nature of gender discrimination, I don't feel comfortable (as a white male) taking on this work without their guidance, as it is likely to negatively impact its legitimacy. I'm sensitive to that "Male Privilege swoop-in-and-take-over" thing, so I'll leave it in the capable hands of Lauren and Cindy. 
>>> 
>>> I support this effort and what it means for the community but started this discussion because it looked like this important work might be stalling, but maybe it's just that I don't know where to look for the next steps & how I can help. Could someone direct me to where I can follow along in the discussions and maybe participate when I'm able to find the time between my other projects? This is really important to the community and I don't want to lose track of what's going on here.
>>> 
>>> Thanks!
>>> 
>>> Michael Krotscheck
>>> 
>>> On Fri, May 6, 2016 at 3:00 PM Matt Jarvis <matt.jarvis at datacentred.co.uk <mailto:matt.jarvis at datacentred.co.uk>> wrote:
>>> that's sad to hear Doug, 2 is definitely 2 too many. What do you think the drivers are for that kind of behaviour - are there cultural elements involved or is it just purely inappropriate behaviour in your experience ? 
>>> 
>>> On 6 May 2016 at 22:51, Doug Hellmann <doug at doughellmann.com <mailto:doug at doughellmann.com>> wrote:
>>> Excerpts from Matt Jarvis's message of 2016-05-06 22:24:55 +0100:
>>> > I have to say that I've never seen any of that kind of behaviour in my time
>>> > in the community, which is not to say it might not be happening elsewhere.
>>> > As we become a global community though, with all our brilliant cultural
>>> > differences as human beings, it is probably a good idea to set the
>>> > acceptable parameters in terms of how we interact with each other.
>>> 
>>> I'm personally aware of at least 2 episodes of harassment against women
>>> at our summit events. So, yes, this is a problem in our community.
>>> 
>>> Thanks, Michael, for picking up the work to finish the CoC updates.
>>> 
>>> Doug
>>> 
>>> >
>>> > On 6 May 2016 at 22:02, Jonathan Proulx <jon at csail.mit.edu <mailto:jon at csail.mit.edu>> wrote:
>>> >
>>> > > Hi Michael,
>>> > >
>>> > > Good points.  We should probably reach out to the Diversity Working
>>> > > Group for their input https://wiki.openstack.org/wiki/Diversity <https://wiki.openstack.org/wiki/Diversity>
>>> > >
>>> > > I'm not particularly familiar with other organization's codes of
>>> > > conduct or more importantly how they have worked in practice.
>>> > >
>>> > > Do you have any suggestions for models to emulate (or avoid)?
>>> > >
>>> > > -Jon
>>> > >
>>> > >
>>> > > On Fri, May 06, 2016 at 08:47:20PM +0000, Michael Krotscheck wrote:
>>> > > :Hello everyone-
>>> > > :
>>> > > :OpenStack's Code of Conduct does not have an explicit discrimination
>>> > > :clause, nor does it have any mention of what constitutes harassment.
>>> > > :
>>> > > :https://www.openstack.org/legal/community-code-of-conduct/ <https://www.openstack.org/legal/community-code-of-conduct/>
>>> > > :
>>> > > :There've been quite a few flashpoints recently, where individuals acting
>>> > > :inside of other open source communities have engaged in allegedly racist,
>>> > > :sexist, and other discriminatory behavior, to the detriment and loss of
>>> > > :their peer contributors. I personally feel that it is only a matter of
>>> > > time
>>> > > :before something similar happens inside of our community (if it hasn't
>>> > > :already), and I strongly believe we should decide how we, as a community,
>>> > > :should react should something like this happen, before it actually does.
>>> > > :
>>> > > :I've spoken to a member of the Board of Directors, and their
>>> > > recommendation
>>> > > :was that the user committee take on this task, and make a recommendation
>>> > > to
>>> > > :the Board and the Foundation.
>>> > > :
>>> > > :My personal opinion is that a zero-tolerance policy may not be effective,
>>> > > :as it provides little opportunity for correction, education, and
>>> > > :redemption. Even so, a policy that does not have teeth will be little more
>>> > > :than lip service.
>>> > > :
>>> > > :Michael Krotscheck
>>> > >
>>> > > :_______________________________________________
>>> > > :User-committee mailing list
>>> > > :User-committee at lists.openstack.org <mailto:User-committee at lists.openstack.org>
>>> > > :http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee <http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee>
>>> > >
>>> > >
>>> > > --
>>> > >
>>> > > _______________________________________________
>>> > > User-committee mailing list
>>> > > User-committee at lists.openstack.org <mailto:User-committee at lists.openstack.org>
>>> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee <http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee>
>>> > >
>>> >
>>> 
>>> _______________________________________________
>>> User-committee mailing list
>>> User-committee at lists.openstack.org <mailto:User-committee at lists.openstack.org>
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee <http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee>
>>> 
>>> 
>>> DataCentred Limited registered in England and Wales no. 05611763_______________________________________________
>>> User-committee mailing list
>>> User-committee at lists.openstack.org <mailto:User-committee at lists.openstack.org>
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee <http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee>
>>> _______________________________________________
>>> User-committee mailing list
>>> User-committee at lists.openstack.org <mailto:User-committee%40lists.openstack.org>
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee <http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee>
>>> 
> 
> _______________________________________________
> User-committee mailing list
> User-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20160622/838381e1/attachment.html>