From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Temporary DevRel actions for CoC violations
Date: Fri, 21 Jun 2013 00:19:47 +0100 [thread overview]
Message-ID: <CAG2jQ8iTEjdasHZk0oZUwyXg=uj6_C6SvE3Zy-r-f78hUhUrnw@mail.gmail.com> (raw)
In-Reply-To: <51C37574.6080203@gentoo.org>
On 20 June 2013 22:34, Chí-Thanh Christopher Nguyễn <chithanh@gentoo.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Markos Chandras schrieb:
>> In the meantime, to prevent further escalations, I will use my lead
>> powers to request immediate bans whenever I see one of you violate the
>> CoC[2] and ignore the previous warnings.
>>
>> My fellow developers, it's time you finally realize that you are part of
>> a community and you must learn to behave and respect each other even if
>> you have different technical views. We are all people sharing a common
>> interest: Gentoo.
>
> So, gathering some of the responses I tried to draw a complete picture of
> what is going to happen (where references are not publicly archived, I
> supplied their Message-ID):
>
> Enforcement of CoC will be proactive, not reactive[0,1]. This in my
> understanding means that devrel will not wait for reports of CoC
> violations. Instead, they or their assistants will be policing mailing
> lists and bugzilla[2] for infractions, and make an example of the first
> developer who transgresses the CoC[3].
>
> Bannable offenses will not be limited to direct personal insults, but also
> include trolling, being judgmental[4], labeling proposals or software as
> "crap"[5], saying things that could be seen as offensive in certain
> cultures or to people with certain personality traits[6], as well as making
> non-constructive statements[7].
>
> To me this is a very grim picture. If hope it is not accurate, but if it is
> I hereby speak out against this. I'd like to see any emergency action
> limited to response to personal attacks and insults, and any stricter rules
> set only in place after Council decision.
>
>
No it is not accurate. You need to read the threads again. For
example, nobody ever said that
we will punish people for calling a software "crap". Please read more
carefully what I wrote.
I also said that we will warn people before we kick them out. Again,
please read more carefully what
I wrote before.
--
Regards,
Markos Chandras - Gentoo Linux Developer
http://dev.gentoo.org/~hwoarang
next prev parent reply other threads:[~2013-06-20 23:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 17:35 [gentoo-project] Temporary DevRel actions for CoC violations Markos Chandras
2013-06-19 17:59 ` Rich Freeman
2013-06-19 18:49 ` William Hubbs
2013-06-19 19:04 ` Tom Wijsman
2013-06-19 20:20 ` Ultrabug
[not found] ` <CAHcsgXS5kckuBec9C+pkrEG+t9HVaamY1T9KK8V2XGuSekq_zQ@mail.gmail.com>
2013-06-20 8:24 ` [gentoo-project] Re: [gentoo-dev] " Luca Barbato
2013-06-20 12:46 ` Petteri Räty
2013-06-20 14:28 ` [gentoo-project] " Rick "Zero_Chaos" Farina
2013-06-20 21:34 ` Chí-Thanh Christopher Nguyễn
2013-06-20 22:30 ` Rich Freeman
2013-06-20 23:19 ` Markos Chandras [this message]
2013-06-28 7:23 ` IAN DELANEY
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAG2jQ8iTEjdasHZk0oZUwyXg=uj6_C6SvE3Zy-r-f78hUhUrnw@mail.gmail.com' \
--to=hwoarang@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox