On Sun, Sep 6, 2015 at 9:19 AM, Brian Wolff <bawolff(a)gmail.com> wrote:
On 9/5/15, rupert THURNER
<rupert.thurner(a)gmail.com> wrote:
On Fri, Sep 4, 2015 at 10:37 PM, Matthew Flaschen
<
mflaschen(a)wikimedia.org>
wrote:
> There is consensus at
>
>
https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Dr…
that the
best way to finalize the CoC draft is to focus on a few
sections at once (while still allowing people to comment on other
lol, consensus among whom, to what? i am against it (i'd love to send the
reasons in another mail though), do i count, and it is still consensus?
Consensus, of the people participating in the talk page of the draft,
in the typical Wikimedia definition of the word (Most arguments have
.puttered out, and a super-majority of those participating seem to
have settled on some agreement).
i
would prefer if you would be so kind to define one measurable criteria
for
the question "do we need a code of
conduct", no matter if entry or
success
criteria. e.g
* 50 volunteers from different part of the world saying that we need it
* 20% of committers want it
* after one year 20% more volunteer commits are done
other critieria like "people attending conferences", or "mails
written"
would be a bad idea, as the goal is to have more contributions, not more
conference tourists or mailing list tourists. what you think, matt, or
quim
?
I feel like this is mixing up the question of whether we "need" a code
of conduct, with whether we will get a code of conduct.
the mails sent here the last week made me think more thorough about what
the actual problem is, and reconsider my posiiton. i added comments to the
phabricator ticket at:
https://phabricator.wikimedia.org/T90908#1612033.
to summarize the phabricator comments briefly, i experienced the wikimedia
technical community as arrogant and ignorant, paradoxically despite the
persons in the community are not arrogant and ignoring. mails get no
answer, ticktes get closed immediately or reshuffled, patches sit in gerrit
for years. contrary, the most successful open source community, linux /
git, tolerates things which we would not tolerate (e.g.
https://youtu.be/MShbP3OpASA?t=2895 f*ck nvidia). i experienced that
community as extremely welcoming and helpful.
after rethinking, i am now convinced that our community can be come more
welcoming with two measures. first, the mindset need to change to be
welcoming. if constant talking about the approach on the mailing list is
not enough a 10 lines code of conduct might help, containing a "WMF persons
assure on every contact that the client walks away happy." instead of a
"WMF punishes misbehave". contrary to all the punishment suggestions above,
it would be a positive policy. the ones involved in raising children
already saw how much more effective a praising and lauding approach is -
which i find works as well with adults. good is also that praising works
international, no cultural barriers.
second i think that our technical products should have a skilled programmer
as product owner who likes tinkering with the product. but - this ideally
goes into a separate mail thread.
best,
rupert