Open Stack

On Thu, Sep 12, 2013 at 12:13 PM, David Mortman <launchpad at mortman.com>wrote:

> I think an ombudsperson is a great idea.
>
> With regards to the code of conduct, the current one is pretty great, I'd
> add to it some pieces from the pycon code of coduct though. I took a stab
> at it below. Would love feedback edits etc.
>
> *Be respectful.* The OpenStack <https://wiki.openstack.org/wiki/OpenStack>community and its members treat one another with respect. Everyone can make
> a valuable contribution to OpenStack<https://wiki.openstack.org/wiki/OpenStack>.
> We may not always agree, but disagreement is no excuse for poor behavior
> and poor manners. We might all experience some frustration now and then,
> but we cannot allow that frustration to turn into a personal attack. It's
> important to remember that a community where people feel uncomfortable or
> threatened is not a productive one. We  expect members of the OpenStack<https://wiki.openstack.org/wiki/OpenStack>community to be respectful when
> dealing with other contributors as well as with people outside the
> OpenStack <https://wiki.openstack.org/wiki/OpenStack> project and with
> users of OpenStack <https://wiki.openstack.org/wiki/OpenStack>. All
> communication, regardless of medium (mailing lists, summits, etc) should be
> appropriate for a professional audience including people of many different
> backgrounds.
>
>
>
> Harassment of any sort is unacceptable. Harassment includes but is not
> limited offensive verbal or written comments related to gender, sexual
> orientation, disability, physical appearance, body size, race, religion,
> deliberate intimidation, stalking, following, sustained disruption of talks
> or other events, inappropriate physical contact, and unwelcome sexual
> attention.
>
>
>
> Participants asked to stop any harassing behavior are expected to comply
> immediately. Any issues related to harassment can be communicated to an
> event/mailing list owner or the OpenStack ombudsperson.  Consequences for
> harassment can include being removed from the relevant event, mailing list
> or being banned from the OpenStack community.
>
>
>
>
>
>

Yes, this wording is nicely put, and I like the placement in the code of
conduct itself. Thanks.

I think more than one ombudsperson may be needed to assure coverage and
avoid anyone being reluctant to report, but I'm not familiar with how
ombuds work in general. I do know that I wouldn't ever report something to
a nameless phone number or generic email address, so I'd like there to be
some identity in place, whether it's "any staff member of the Foundation"
or "staff at the conference identified by a badge or shirt" or some sort of
spread-out reporting mechanism. Offering training, even just an hour for
role play, for those identified people would be helpful as well.

Thanks,
Anne


>
>
>
>
> On Wed, Sep 11, 2013 at 2:09 PM, Tim Bell <Tim.Bell at cern.ch> wrote:
>
>> ** **
>>
>> I like the pycon code of conduct but I also want to be sure that
>> communication outside of the summit is also covered (from mailing lists,
>> user groups, etc). Pycon clearly has a limited scope but as a foundation
>> and community, we are more than a single event. I feel that Incorporating
>> the best of breed into our foundation Conduct document, along with
>> requiring participants of the OpenStack summit to respect the code of
>> conduct, even if they are not members of the foundation.****
>>
>> ** **
>>
>> An ombuds would be very useful.****
>>
>> ** **
>>
>> Tim****
>>
>> ** **
>>
>> ** **
>>
>> *From:* David Mortman [mailto:launchpad at mortman.com]
>> *Sent:* 11 September 2013 19:41
>> *To:* Anne Gentle
>> *Cc:* openstack at lists.openstack.org
>>
>> *Subject:* Re: [Openstack] Fwd: Making the Hong Kong Summit as inclusive
>> as possible****
>>
>> ** **
>>
>> I like the idea of framing it as a code of conduct which definitely has a
>> more positive spin than anti-harassment policy and the general one you
>> linked to is a great start. I'd love to see something added about
>> consequences of violating the code as well.****
>>
>> ** **
>>
>> On Wed, Sep 11, 2013 at 9:47 AM, Anne Gentle <anne at openstack.org> wrote:*
>> ***
>>
>> I would greatly support a reporting process for issues for our Summits.
>> Thanks David for bringing it to the mailing list. I can help in any way
>> needed. ****
>>
>> ** **
>>
>> One bit of input, I'm not sure wording as strong as "anti-harrassment
>> policy" is required, though that's at the heart of it. We can probably
>> follow in PyCon's footsteps with a Code of Conduct for conferences, [1]
>> which refers to the Ada Initiative's wiki. [2] ****
>>
>> ** **
>>
>> Also, as a gentle reminder (ha!) as members of the community, we do have
>> a code of conduct in place already [3]. I'd like to ensure we carry some
>> processes for ensuring we all are welcomed at Summits and have a safety net
>> for reporting and correcting issues.****
>>
>> ** **
>>
>> Thanks,****
>>
>> ** **
>>
>> Anne ****
>>
>> 1.
>> http://pyfound.blogspot.com/2012/12/psf-moves-to-require-code-of-conduct.html
>> ****
>>
>> 2. http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy *
>> ***
>>
>> 3. https://wiki.openstack.org/wiki/Conduct****
>>
>> ** **
>>
>> On Wed, Sep 11, 2013 at 8:18 AM, David Mortman <launchpad at mortman.com>
>> wrote:****
>>
>> ** **
>>
>> Given the recent and ongoing issues with sexism (not to mention racism,
>> homophobia and general bigotry) at tech conferences, I recently engaged
>> with several folks on twitter about what was being done to make sure that
>> the Hong Kong Summit was as inclusive as possible regardless of an
>> attendee's age, sex, orientation, race or anything else. I think a good
>> place to start would be an official  anti-harassment policy and a process
>> for people to report issues to the event organizers who can then deal with
>> the issue appropriately. I am happy to help with the drafting of both the
>> policy and the process. What do folks think?
>>
>> ****
>>
>> -David****
>>
>> ** **
>>
>> ** **
>>
>> _______________________________________________
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to     : openstack at lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack****
>>
>> ** **
>>
>> ** **
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130912/3b5bd5af/attachment.html>