From: HiPhish <hiphish@posteo.de>
To: guix-devel@gnu.org
Subject: Re: Promoting the GNU Kind Communication Guidelines?
Date: Mon, 29 Oct 2018 00:37:03 +0100 [thread overview]
Message-ID: <2243540.P3GW2o3ZaK@aleksandar-ixtreme-m5740> (raw)
On Sun, Oct 28, 2018, at 7:33 AM, Gábor Boskovits wrote:
> 3. GKCG seems to be inadequate in the opinion of the maintainers, as:
> a. it does not define acceptable behaviour, and
> b. it does not define processes.
To be honest, neither does the CC really. It throws out a vague list, but
never goes into any detail. I believe this is intentional, if you never define
what the goalposts are, then you can move them around as much as you want and
apply punishment as you see fit.
The same goes for due process, it does not define how to apply punishment, just
that the punishment can range from a warning to getting completely banned.
Also the accused has no right to defense, the accusation does not need to be
disclosed and if any maintainer disagrees they can be removed from the project
as well. This is just a kangaroo court system.
> I proposed to try to roll our own, essentially based on GKCG,
> but have the acceptable behaviour and the processes defined.
I am not totally opposed to it, but it's like writing your own license: other
people have already put thought into it, so just use what they have written.
The GKCG has the added bonus that it is an official GNU guideline, so it would
be nice to have it throughout the GNU projects. The Debian CoC seems fine, and
KDE has a decent one as well.
https://www.kde.org/code-of-conduct/
> Do you think that this could result in a better situation overall?
Improve in regards to what exactly? Are the maintainers afraid that the
mailing list will turn into 4chan if there is no CoC in place?
next reply other threads:[~2018-10-28 23:37 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-28 23:37 HiPhish [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-30 0:46 Promoting the GNU Kind Communication Guidelines? Alex Griffin
2018-10-30 2:09 ` Alex Griffin
2018-10-28 11:58 HiPhish
2018-10-28 12:33 ` Gábor Boskovits
2018-10-28 16:14 ` Alex Griffin
2018-10-28 20:55 ` Thorsten Wilms
2018-10-29 11:27 ` Alex Sassmannshausen
2018-10-29 17:00 ` Thorsten Wilms
2018-10-29 17:50 ` Ricardo Wurmus
2018-10-29 11:29 ` Alex Sassmannshausen
2018-10-29 8:23 ` Björn Höfling
2018-10-29 10:10 ` Thorsten Wilms
2018-10-29 11:13 ` Alex Sassmannshausen
2018-10-29 17:15 ` Thorsten Wilms
2018-10-29 17:43 ` Ricardo Wurmus
2018-10-29 20:44 ` Björn Höfling
2018-10-29 11:08 ` Alex Sassmannshausen
2018-10-29 18:50 ` HiPhish
2018-10-29 23:54 ` Tonton
2018-10-30 0:38 ` HiPhish
2018-10-30 5:13 ` Nils Gillmann
2018-10-31 9:27 ` Alex Sassmannshausen
2018-10-31 12:29 ` HiPhish
2018-10-31 12:46 ` Alex Sassmannshausen
2018-10-31 13:23 ` HiPhish
2018-10-31 14:14 ` Jelle Licht
2018-10-31 14:55 ` HiPhish
2018-10-31 12:30 ` HiPhish
2018-10-31 13:48 ` Jelle Licht
2018-10-31 14:55 ` HiPhish
2018-10-31 17:17 ` Thorsten Wilms
2018-11-01 10:35 ` Mark H Weaver
2018-10-31 13:48 ` Thomas Danckaert
2018-10-31 14:06 ` Alex Griffin
2018-10-31 14:55 ` HiPhish
2018-10-31 16:41 ` Thorsten Wilms
2018-11-01 2:58 ` Mark H Weaver
2018-11-01 9:14 ` Mark H Weaver
2018-11-01 8:40 ` Steffen Schulz
2018-10-29 12:48 ` Giovanni Biscuolo
[not found] ` <9066320.aHiQMI0tiE@aleksandar-ixtreme-m5740>
2018-10-29 18:49 ` HiPhish
2018-10-23 11:15 Mathieu Lirzin
2018-10-23 13:38 ` Tobias Geerinckx-Rice
2018-10-23 14:39 ` Mathieu Lirzin
2018-10-24 1:06 ` Alex Griffin
2018-10-24 3:02 ` Jack Hill
2018-10-24 10:02 ` Ludovic Courtès
2018-10-24 14:21 ` Alex Griffin
2018-10-26 21:36 ` Tonton
2018-10-26 22:37 ` Alex Griffin
2018-10-28 18:42 ` Tonton
2018-10-28 19:50 ` Alex Griffin
2018-10-28 20:25 ` Alex Griffin
2018-10-28 21:12 ` Thorsten Wilms
2018-10-28 21:26 ` Alex Griffin
2018-10-29 8:59 ` Björn Höfling
2018-10-29 10:49 ` Thorsten Wilms
2018-10-29 13:43 ` Alex Griffin
2018-10-29 17:48 ` Christopher Lemmer Webber
2018-10-29 22:58 ` Tonton
2018-10-29 18:16 ` Cook, Malcolm
2018-10-24 10:23 ` Ludovic Courtès
2018-10-24 16:06 ` Mathieu Lirzin
2018-10-25 10:23 ` Ricardo Wurmus
2018-10-25 15:25 ` Mathieu Lirzin
2018-10-25 23:03 ` George Clemmer
2018-10-26 2:43 ` Gábor Boskovits
2018-10-26 21:25 ` Alex Griffin
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2243540.P3GW2o3ZaK@aleksandar-ixtreme-m5740 \
--to=hiphish@posteo.de \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).