From: Thorsten Wilms <t_w_@freenet.de>
To: guix-devel@gnu.org
Subject: Re: Patch submission should not imply agreement to policy (was Re: Promoting the GNU Kind Communication Guidelines?)
Date: Tue, 30 Oct 2018 20:39:08 +0100 [thread overview]
Message-ID: <e19b6ad3-7413-6d0a-67f2-988b98e77f66@freenet.de> (raw)
In-Reply-To: <87bm7bef6y.fsf@dustycloud.org>
Thanks to Mark H Weaver for writing ... how to say .. the mirror
perspective of what I wish I would have written as sole input so far :)
On 30/10/2018 14.28, Christopher Lemmer Webber wrote:
>>>> It used to be that you could pick a Free Software project and send a patch.
>>>>
>>>> Now sending a patch is supposed to imply agreeing to the equivalent of
>>>> an EULA? Everyone is expected to welcome that as progress?
>
> The statement above makes it sound like the Code of Conduct is
> dramatically new.
It is based on the fact that there are many projects that existed for
some time before adopting a CoC. The EULA comparison is only about CoCs
with "covenant" and "we contributors pledge" type of language.
While benefiting from and accepting a copyleft license is pretty much a
precondition for a patch, that is not the case for a CoC that tries to
bind one on contribution.
> My claim here was that in both cases, there is a
> policy the community has adopted. One is legal and copyleft, the other
> is behavioral and a code of conduct. In both cases, your participation
> in this community is dependent on your willingness to agree to respect
> the policies and norms that the group upholds.
Submitting a patch might involve only the most minimal interaction with
one maintainer. Staying within a very narrow subset of rules that a
group might uphold should suffice to cause no harm to anyone while
allowing people to benefit from the work.
The group is not clearly delineated. The actual norms are only shown in
how the maintainers and regulars act.
> The code of conduct
> does not provide a legal enforcement mechanism, so the EULA comment in
> that sense does not hold up; this is just a codification of some of the
> norms that we have. But someone made the EULA comment, and the extent
> that it *did* make sense (that there are policies, in some way), I
> wanted to reply to it.
What I had in mind is: Unpacking an old-school software that has a
shrink-wrap EULA is meant to imply acceptance of the license.
Likewise, contributing to Guix is apparently meant to imply that one
makes the pledge as outlined in that CoC.
In both cases, you are meant to not get one without the other. It
happened that one could not read the EULA in advance and it happened
that I contributed before reading the CoC carefully. I distrust it's
origin and I'm not happy about a few details, though they most likely
will never matter. So I could almost, but not quite make such a promise,
but I cannot be made to make such a promise. Especially retroactively.
Even less can I be made to make a promise that might change:
I assume that Ricardo and Ludovic want to have the option of editing the
CoC without asking every single contributor. Well, people should better
know what the current state of their pledge is.
Not that I think the two would introduce a nasty surprise, it's just
that the "covenant" and "we as contributors ... pledge" language is
dishonest.
Reject a contribution, talk to me, warn me, set an ultimatum, ban me if
I did wrong by your norms as you see fit, that's all fine and expected
with or without CoC anyway, but please don't try to make me say: those
norms are mine (independent on whether they could be).
If I sound like a drama royal person ... so be it! ;)
--
Thorsten Wilms
thorwil's design for free software:
http://thorwil.wordpress.com/
next prev parent reply other threads:[~2018-10-30 19:42 UTC|newest]
Thread overview: 36+ 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
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 [this message]
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
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=e19b6ad3-7413-6d0a-67f2-988b98e77f66@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 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).