[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Add Code of Conduct (issue 575620043 by address@hidden)
From: |
David Kastrup |
Subject: |
Re: Add Code of Conduct (issue 575620043 by address@hidden) |
Date: |
Thu, 06 Feb 2020 16:21:44 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Kieren MacMillan <address@hidden> writes:
> Hi David,
>
>> The problem with an approach focused on punishment and expulsion is that
>> it helps isolating and eventually ostracizing bad actors, limiting the
>> total damage they may cause.
>
> "Limiting the total damage they may cause" is a "problem"? You
> definitely have me confused on that one. ;)
No, the problem is that this solution to the problems of bad actors
addresses a problem that we do not have to a relevant degree. At least
I hope we can agree that my intent is not doling out damage to the
project.
So a solution focused on punishment does not work. Punishment makes
sense for deliberately committed acts.
A committee to complain to also does not help against the problem of
rapid devolvement that Janek mentioned since it is just too late.
We'd need a web page for a large enough set of developers/users to
warrant speedy response where they can click a "Cool down, David" button
that sents an automatic mail to me and blocks submissions from me to the
respective list and/or topic until I have manually acknowledged having
gotten the mail and/or at least an hour(?) has passed.
In other word: to apply to the elephant in our interaction room
effectively, the "enforcement" mechanism would need to be quite
different.
> If I might turn your comment to the contrapositive: The benefit with
> an approach that includes the possibility for punishment and
> ultimately expulsion is that it potentially provides corrective
> feedback for bad actors and limits the total damage they may cause.
>
>> I have no good idea.
>
> One of the [so-far-unstated] goals of my Giant Hypergranular List of
> Jobs is to address the same problem as the CoC from a different
> angle. We’ll have to wait and see if it works out as I feel it could.
>
> Cheers,
> Kieren.
> ________________________________
>
> Kieren MacMillan, composer (he/him/his)
> ‣ website: www.kierenmacmillan.info
> ‣ email: address@hidden
>
>
--
David Kastrup
- Re: Add Code of Conduct (issue 575620043 by address@hidden), (continued)
- Re: Add Code of Conduct (issue 575620043 by address@hidden), Carl Sorensen, 2020/02/05
- Re: Add Code of Conduct (issue 575620043 by address@hidden), Werner LEMBERG, 2020/02/05
- Re: Add Code of Conduct (issue 575620043 by address@hidden), Janek Warchoł, 2020/02/06
- Re: Add Code of Conduct (issue 575620043 by address@hidden), James, 2020/02/06
- Re: Add Code of Conduct (issue 575620043 by address@hidden), Kieren MacMillan, 2020/02/06
- Re: Add Code of Conduct (issue 575620043 by address@hidden), David Kastrup, 2020/02/06
- Re: Add Code of Conduct (issue 575620043 by address@hidden), Kieren MacMillan, 2020/02/06
- Re: Add Code of Conduct (issue 575620043 by address@hidden),
David Kastrup <=
- Re: Add Code of Conduct (issue 575620043 by address@hidden), Kieren MacMillan, 2020/02/06
- Re: Add Code of Conduct (issue 575620043 by address@hidden), Wols Lists, 2020/02/07
- Re: Add Code of Conduct (issue 575620043 by address@hidden), Kieren MacMillan, 2020/02/08
- Re: Add Code of Conduct (issue 575620043 by address@hidden), David Kastrup, 2020/02/05
- Re: Add Code of Conduct (issue 575620043 by address@hidden), Werner LEMBERG, 2020/02/05
Re: Add Code of Conduct (issue 575620043 by address@hidden), karlinhigh, 2020/02/04
Re: Add Code of Conduct (issue 575620043 by address@hidden), jonas . hahnfeld, 2020/02/05
Re: Add Code of Conduct (issue 575620043 by address@hidden), jonas . hahnfeld, 2020/02/05
Re: Add Code of Conduct (issue 575620043 by address@hidden), nine . fierce . ballads, 2020/02/05