From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Alex Griffin <a@ajgrf.com>
Cc: guix-devel@gnu.org
Subject: Re: Promoting the GNU Kind Communication Guidelines?
Date: Mon, 29 Oct 2018 09:59:13 +0100 [thread overview]
Message-ID: <20181029095913.25aa3829@alma-ubu> (raw)
In-Reply-To: <20181028195054.GA10708@antares.lan>
[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]
On Sun, 28 Oct 2018 14:50:54 -0500
Alex Griffin <a@ajgrf.com> wrote:
> On Sun, Oct 28, 2018, at 1:42 PM, Tonton wrote:
> >From sentence 1 of the Contributor Covenant:
> > In the interest of fostering an open and welcoming environment, we
> > as contributors and maintainers pledge to [...]
>
> This snippet right here is a problem even before we get to the meat
> and potatoes. I don't appreciate the presumption that my mere
> participation indicates my agreement with this document. It rubs me
> the wrong way even when I'm only reporting a bug (which does fall
> under its scope, because 'issues', as found in an issue tracker, are
> explicitly mentioned further down).
>
You can harass in just one bug report: "Module foo does not work for
me. [Normal bug report things here] This beast is written in
such a bad way, the bug is more its contributor Bar, he/she/zhe is so
[inappropriate phrase here], get rid of him/her/zhe immediately and the
problem is resolved."
Nobody asked about reporting, nobody asked to sign a CoC or anything,
yet this is harassment and the project (maintainer) should take
immediate steps to protect Bar.
The same harassment can pretty well be packed in a patch.
In law, there is the term of "conduct implying an intent". So even not
signing anything you could argue that by sending a bug or a patch you
silently agree with the community guidelines, CoC, etc. You enter the
community be interacting the first time. And will be judged by their
guidelines.
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-10-29 8:59 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 11:15 Promoting the GNU Kind Communication Guidelines? 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 [this message]
2018-10-29 10:49 ` Thorsten Wilms
2018-10-29 13:43 ` Alex Griffin
2018-10-29 17:48 ` Christopher Lemmer Webber
2018-10-30 7:48 ` Patch submission should not imply agreement to policy (was Re: Promoting the GNU Kind Communication Guidelines?) Mark H Weaver
2018-10-30 13:28 ` Christopher Lemmer Webber
2018-10-30 19:39 ` Thorsten Wilms
2018-10-31 8:58 ` Alex Sassmannshausen
2018-10-31 12:17 ` Thorsten Wilms
2018-10-31 12:48 ` Alex Sassmannshausen
2018-10-31 11:17 ` Mark H Weaver
2018-11-01 3:47 ` Mark H Weaver
2018-10-31 20:51 ` Thorsten Wilms
2018-10-29 22:58 ` Promoting the GNU Kind Communication Guidelines? 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
-- strict thread matches above, loose matches on Subject: below --
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-28 23:37 HiPhish
2018-10-30 0:46 Alex Griffin
2018-10-30 2:09 ` 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=20181029095913.25aa3829@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=a@ajgrf.com \
--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).