[Osmf-talk] Proposal - OSMF Should Adopt a Code of Conduct

Dylan Moriarty moriartymaps at gmail.com
Sat Dec 2 18:00:51 UTC 2017


>
> Now I do make the admission that for somebody that has never been involved
> in OSM in an active way before, being dropped on to this mailing list has
> to be bewildering, which goes for any mailing list in times of high
> traffic, but to turn it in to an essentially moderated list on which you
> don't dare raise issues or say your mind because you might frighten
> somebody away that doesn't have the context of the discussion yet, cannot
> be the solution


This argument seems to be assuming that a violation would immediately
result in suspension or something extreme. *Presumably* if someone raised
an issue, but did it in an incredibly rude way, at least the first time
it'd be a warning or notification.

The person you're talking about frightening away in this situation is
making others feel uncomfortable by some means. That means their message is
getting muddled, will be misinterpreted, and everyone involved will walk
away mad. If there's a CoC, there'd be incentive to actually be considerate
about how one expresses themselves. Surely any issues that need raising
could be discussed in ways that wouldn't violate common CoC's?







On Sat, Dec 2, 2017 at 11:27 AM, Simon Poole <simon at poole.ch> wrote:

> Hi Clifford
>
> I find it interesting that you choose to not include the organisation most
> similar in mission to the OSMF (the Wikimedia Foundation (WMF)) in your
> list, particularly given the OSMF is clearly not an "Open Source"
> organisation (with exception of a short stint by Andy Allan immediately
> prior the licence change to finish the redaction software, I'm not aware of
> the OSMF ever contracting for, distributing, or overseeing the development
> of any software at all).
>
> The WMF is of particular interest, not just because they, at least in
> theory, have a similar role in their overall movement as the OSMF, but
> because they have multiple CoC or similar documents tailor made for the
> venue, activity and groups that they concern. Taking particular care on the
> hand to allow people working together on a specific task do so in a
> friendly non-discriminatory environment (in our case this would be mainly
> the working groups) and on the other hand being careful not to stifle
> debate and critical discussion of matters that concern policies, elections
> and the central organisation  (in our case the OSMF).
>
> Now I do make the admission that for somebody that has never been involved
> in OSM in an active way before, being dropped on to this mailing list has
> to be bewildering, which goes for any mailing list in times of high
> traffic, but to turn it in to an essentially moderated list on which you
> don't dare raise issues or say your mind because you might frighten
> somebody away that doesn't have the context of the discussion yet, cannot
> be the solution. Maybe we should simply revive osmf-announce and not
> automatically subscribe everybody to this list, though I'm sure that will
> simply result in people complaining that they are being cut out of
> important discussions.
>
> That, very seldom, we have events in which unacceptable language is used,
> I count three in seven years of OSM (the major one being two Americans
> calling each other names on talk-diversity,). is the risk that we take by
> providing open communication forums, no CoC will stop that happening,
> except of we turn this list in to fully moderated. But that risk is by far
> outweighed by the benefits.
>
> Simon
>
>
> Am 01.12.2017 um 04:25 schrieb Clifford Snow:
>
> OpenStreetMap is one of the few open source initiatives that operates its
> mailing lists without a formal Code of Conduct. Many [1] of the large open
> source projects have adopted a Code of Conduct for their mailing lists,
> forums and conferences.
>
> Why would we want to have a formal standard for contact? OpenStreetMap
> longevity depends on our being able to attract and keep new mappers,
> developers and third party users. Good behavior means more people feel
> comfortable engaging in community discussions. Bad conduct not only drives
> people away but can lead to giving OSM a bad reputation. Our reputation is
> key to raising funds needed for operation and growth. The OSMF Board has a
> fiduciary responsibility to protect our project. Adopting and enforcing a
> Code of Conduct is a step in that direction.
>
> Some examples of CoC guidelines are:
>
>    -
>
>    Be respectful
>    -
>
>    Be friendly and patient
>    -
>
>    Be civil and considerate
>    - Be collaborative
>    -
>
>    Assume good intentions.
>    -
>
>    Respect time and attention
>    -
>
>    Disclose potential conflicts
>    - Take responsibility for our words and our actions
>    -
>
>    Be welcoming
>    -
>
>    Be careful in the words that you choose
>    -
>
>       Discriminatory remarks based on stereotypes
>       -
>
>       Violent threats or language directed against another person.
>       -
>
>       Discriminatory jokes and language.
>       -
>
>       Posting sexually explicit or violent material.
>       -
>
>       Posting (or threatening to post) other people's personally
>       identifying information ("doxing").
>       -
>
>       Personal insults, especially those using racist or sexist terms.
>       -
>
>       Unwelcome sexual attention.
>       -
>
>       Repeated harassment of others. In general, if someone asks you to
>       stop, then stop.
>       -
>
>       Deliberately spreading FUD (Fear, Uncertainty, Doubt)
>       -
>
>       Advocating for, or encouraging, any of the above behavior.
>
>
> Adopting a CoC is just one step in the process. If we only post the CoC
> when members sign up on a mailing list or attend our conferences, nothing
> will change. Instead the Board should:
>
>    -
>
>    Define the scope of the policy: may include mailing lists, conferences
>    and other in person gatherings, forums, comments on changesets, IRC,
>    -
>
>    Decide who is responsible for responding to reports of abuse
>    -
>
>    Determine consequences for violating the CoC
>    -
>
>    Provide appropriate avenues to report abuse
>    -
>
>    Periodically remind members of our CoC
>
>
>
> [1] Example of Codes of Conduct by Open Source organizations:
>
>    -
>
>    Linux Foundation - https://www.linuxfoundation.
>    org/events/code-of-conduct/
>    -
>
>    Ada Initiative - https://adainitiative.org/2014/02/18/howto-design-a-
>    code-of-conduct-for-your-community/
>    <https://adainitiative.org/2014/02/18/howto-design-a-code-of-conduct-for-your-community/>
>    -
>
>    Open Source Initiative - https://opensource.org/codeofconduct
>    -
>
>    OSGEO - http://www.osgeo.org/code_of_conduct
>    -
>
>    Ubuntu - https://www.ubuntu.com/about/about-ubuntu/conduct
>    -
>
>    Mailman - https://www.gnu.org/software/mailman/coc.html
>    -
>
>    HOTOSM - https://www.hotosm.org/hot_code_of_conduct
>    -
>
>    Django - https://www.djangoproject.com/conduct/
>    -
>
>    Mozilla - https://www.mozilla.org/en-US/about/governance/policies/
>    participation/
>    -
>
>    Rust - https://www.rust-lang.org/en-US/conduct.html
>    -
>
>    Eclipes - https://www.eclipse.org/org/documents/Community_Code_of_
>    Conduct.php
>    -
>
>    Fedora - https://docs.fedoraproject.org/fedora-project/project/
>    code-of-conduct.html
>    -
>
>    Climate CoLab (crowdsource climate change)  -
>    https://climatecolab.org/wiki/Community%20philosophy%20and%20policies
>    <https://climatecolab.org/wiki/Community%20philosophy%20and%20policies>
>
>
> Resources
>
>    -
>
>    Defining and Developing an Effective Code of Conduct for Organizations
>    - http://www.icaew.com/~/media/corporate/files/technical/
>    ethics/defining%20and%20developing%20an%20effective%
>    20code%20of%20conduct%20for%20organizations.ashx
>    <http://www.icaew.com/%7E/media/corporate/files/technical/ethics/defining%20and%20developing%20an%20effective%20code%20of%20conduct%20for%20organizations.ashx>
>    -
>
>    Ada Initiative How to design a code of conduct for your community -
>    https://adainitiative.org/2014/02/18/howto-design-a-
>    code-of-conduct-for-your-community/
>    <https://adainitiative.org/2014/02/18/howto-design-a-code-of-conduct-for-your-community/>
>    - The Geek Feminism CoC Evaluations- http://geekfeminism.wikia.com/
>    wiki/Code_of_conduct
>
>
> Respectively,
> Clifford
>
>
> --
> @osm_seattle
> osm_seattle.snowandsnow.us
> OpenStreetMap: Maps with a human touch
>
>
> _______________________________________________
> osmf-talk mailing listosmf-talk at openstreetmap.orghttps://lists.openstreetmap.org/listinfo/osmf-talk
>
>
>
> _______________________________________________
> osmf-talk mailing list
> osmf-talk at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/osmf-talk
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/osmf-talk/attachments/20171202/39aa0b68/attachment.html>


More information about the osmf-talk mailing list