On Aug 13, 2015 10:16 PM, "Oliver Keyes" <okeyes(a)wikimedia.org> wrote:
On 13 August 2015 at 16:10, Antoine Musso <hashar+wmf(a)free.fr> wrote:
> Le 07/08/2015 02:17, Matthew Flaschen a écrit :
>> We're in the process of developing a code of conduct for technical
>> spaces. This will be binding, and apply to all Wikimedia-related
>> technical spaces (including but not limited to
MediaWiki.org,
>> Phabricator, Gerrit, technical IRC channels, and Etherpad).
>>
>> Please participate at
>>
https://www.mediawiki.org/wiki/Code_of_conduct_for_technical_spaces/Draft
.
>> Suggestions are welcome here or at
>>
https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Dr…
.
Hello Matt,
It seems the code of conduct is fairly similar to the friendly space
policy. Though the later was meant for conferences, it can probably be
amended to be applied to cyberspace interactions.
https://wikimediafoundation.org/wiki/Friendly_space_policy
Do we have any examples of unfriendly behaviour that occurred recently?
The thread you are replying to contains both examples of unfriendly
behaviour in a technical context and discussion over the direct
applicability of the friendly spaces policy; reviewing it may be a
good idea.
Oliver, I must be a little blind but I do not see examples of unfriendly
behaviour in this thread.
In general, Matt, I do experience that the wikimedia movement is
criticized having too many rules and policies. Add another one does not
help. At the end of the day your target group is code contributors, not
policy readers. If somebody does not behave and not contribute, the person
is easily shut up. If somebody contributes a lot, some diplomacy is
required. What you do here is, imho, an example of an organization busy
with itself. I won't be angry if you stop this thread and delete the wiki
page. Let me add, I really appreciate and find very valuable all the other
technical contributions and discussions. And Matt, of course I appreciate
that you know what you are talking about beeing software and Wikipedia
content contributor.
Best,
Rupert