[diversity-talk] OSM code of conduct: starting points

Dan S danstowell+osm at gmail.com
Thu Oct 9 07:46:24 UTC 2014


Hi all,

Great. I think I'd better mention that when I started this thread I
hadn't noticed that there is a current effort on github, which seems
an actual real-life starting point:
<https://github.com/osmlab/CoC-mailing-lists>
(See also the "Issues" discussed there.)

So I went through it to compare it against the 2010 wiki draft and
some other examples, and personally I feel that we don't lose anything
by going with the github draft as a starting point - as opposed to the
ones mentioned when I started the thread!

I think Serge's point about doing it bottom-up rather than trying to
cover the whole of OSMland at once makes a lot of sense. If people see
a CoC working well for one or more mailing lists, that feels a much
better route to adoption than some un-road-tested universal code.

Best
Dan

2014-10-09 4:49 GMT+01:00 Jo Walsh <metazool at gmail.com>:
> Okay, my gloss on this is that the Code of Conduct is a kind of shibboleth
> and a kind of insurance policy.
>
> You need one in order to be seen taking this stuff seriously, conversely to
> lack one suggests the community is not really engaging, at least OSM has
> several good faith efforts ;)
>
> I am imagining something really minimal, a few points that a person would
> obviously have to be a real asshole to disagree with. In OSM's case this
> might cover vandalising the map, as well as abusive behaviours. The below
> excerpt from the geekfeminism wiki is more targeted at conferences i think,
> and prescriptive sounding but reasonable in principle.
>
> "Important elements of an effective code of conduct include:
>
> Specific descriptions of common but unacceptable behavior (sexist jokes,
> etc.)
> Reporting instructions with contact information
> Information about how it may be enforced
>
>  Codes of conduct which lack any one of these items tend not to have the
> intended effect."
>
> If you kept a central Code very short and obvious then you could adopt it
> and then kind of subclass it when you had more specific needs - such as at
> SoTM or on the mailing lists...
>
>
>
>
>
>
>
>
>
> On Wed, Oct 8, 2014 at 8:14 PM, Paul Norman <penorman at mac.com> wrote:
>>
>> On 10/8/2014 3:03 AM, Dan S wrote:
>>
>> Plus I may have missed out suggestions from others!
>>
>> A very recent one is the proposed Stack Exchange one at
>> http://meta.stackexchange.com/q/240594/272090. One of the comments makes the
>> point that a one-size fits all CoC doesn't work, and there are specific
>> issues to any community. For example, SE deals with a lot of inexperienced
>> users asking questions, so issues were raised around that. For OSM, we need
>> to figure out what's needed for us and other open data projects. Do we have
>> examples of CoCs from other open data projects? I checked Freebase and
>> didn't find a CoC.
>>
>> Because we're intrinsically a geographic project, the following comments
>> from the SE CoC proposal are of particular relevance
>>
>> - http://meta.stackexchange.com/a/240638/272090
>> - http://meta.stackexchange.com/a/240635/272090
>> - General comments about not having English as a first language
>>
>> _______________________________________________
>> diversity-talk mailing list
>> diversity-talk at openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/diversity-talk
>>
>
>
> _______________________________________________
> diversity-talk mailing list
> diversity-talk at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/diversity-talk
>



More information about the diversity-talk mailing list