all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thorsten Wilms <t_w_@freenet.de>
To: guix-devel@gnu.org
Subject: Re: Stop it. Formerly - Re: Promoting the GNU Kind Communication Guidelines?
Date: Sun, 4 Nov 2018 22:01:26 +0100	[thread overview]
Message-ID: <ca3b6f8c-9aac-59e1-c49f-7ef605f970fc@freenet.de> (raw)
In-Reply-To: <87ftwhyzh2.fsf@netris.org>

On 04/11/2018 10.15, Mark H Weaver wrote:

> I've decided to withdraw my objections to the policy of requiring that
> project participants agree to our CoC.

I though of Mark as the only "insider" who understood what my prime 
issue with the CoC is. Now it seems that wasn't the case and surely 
isn't now.

Here's a pledge: This shall be my last email about this specific issue, 
on any Guix list, unless the text does get changed either in the 
Covenant project or here, or if I'm asked a question.

Maybe someone here still has the patience to help me understand where my 
interpretation would be unreasonable:

"In the interest of fostering an open and welcoming environment, we as 
contributors and maintainers pledge to making participation in our 
project and our community a harassment-free experience for everyone, 
regardless of age, body size, disability, ethnicity, gender identity and 
expression, level of experience, education, socio-economic status, 
nationality, personal appearance, race, religion, or sexual identity and 
orientation."

Contains the statement that "contributors" make a "pledge", i.e. give a 
promise, as outlined in the rest of the sentence.

I take "contributors" to be the group of people who ever contributed 
anything to the project. At the very least everyone who submitted code 
that is part of the current tree.

Hence, I see included a claim that the very people who walked away 
because of the CoC still make that pledge.


One may ask: who would object to pledging to not harass people, 
regardless of who and how they are? Sure, but as I see it, the "pledge" 
claim doesn't stop there. The first sentence establishes that "we" and 
"our" is supposed to mean "maintainers" and "contributors". Because of 
this, everything in "Our Standards" is an extension of the pledge. As is 
"Scope", quite literally being the scope of the pledge.

I assume the core maintainers may update/edit the CoC as they see fit, 
which in principal might change standards and scope. The CoC would then 
include the claim that all past and current contributors now suddenly 
pledged according to those new standards, perhaps with a wider scope. It 
is their right to set the rules, but they should not imply that "we" 
chose the rules.

Aside of that, a false statement about people is still a false 
statement, even if it says that the people promised to be nice.


Off-list, I have been asked, more or less, to not take the word "pledge" 
so seriously. Well, if I don't, at the very least, the promise regarding 
a harassment-free environment falls out of the CoC, which surely is not 
what anyone meant. If one assumes, not without reason, that the "we" of 
the CoC doesn't actually exist", then what is left?


Anyway, I may still opt to (try to) contribute, as nobody would gain 
anything from my withholding a package or whatever it may be.


-- 
Thorsten Wilms

thorwil's design for free software:
http://thorwil.wordpress.com/

  parent reply	other threads:[~2018-11-04 21:19 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-28 11:58 Promoting the GNU Kind Communication Guidelines? 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 23:54         ` OF-TOPIC: " Tonton
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 15:41                 ` Stop it. Formerly - " Pjotr Prins
2018-10-31 17:51                   ` Leo Famulari
2018-11-01 14:40                     ` Ludovic Courtès
2018-11-01 15:11                       ` Alex Griffin
2018-11-02  2:04                       ` Mark H Weaver
2018-11-04  9:15                         ` Mark H Weaver
2018-11-04 14:30                           ` HiPhish
2018-11-04 21:01                           ` Thorsten Wilms [this message]
2018-11-06 12:55                         ` Ludovic Courtès
2018-11-06 17:23                         ` Marius Bakke
2018-11-06 17:41                           ` 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 11:37 ` Promoting the GNU Kind Communication Guidelines? (-> convivenza) Nils Gillmann
2018-10-29 11:45   ` Nils Gillmann
2018-10-29 12:01   ` Alex Sassmannshausen
2018-10-29 12:48 ` Promoting the GNU Kind Communication Guidelines? Giovanni Biscuolo
     [not found]   ` <9066320.aHiQMI0tiE@aleksandar-ixtreme-m5740>
2018-10-29 18:49     ` HiPhish
  -- strict thread matches above, loose matches on Subject: below --
2018-11-06  1:19 Stop it. Formerly - " Jeremiah

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=ca3b6f8c-9aac-59e1-c49f-7ef605f970fc@freenet.de \
    --to=t_w_@freenet.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.