all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jack Hill <jackhill@jackhill.us>
To: Alex Griffin <a@ajgrf.com>
Cc: guix-devel@gnu.org
Subject: Re: Promoting the GNU Kind Communication Guidelines?
Date: Tue, 23 Oct 2018 23:02:55 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.20.1810232158410.2975@marsh.hcoop.net> (raw)
In-Reply-To: <20181024010640.GA14776@antares.lan>

Alex,

On Tue, 23 Oct 2018, Alex Griffin wrote:

> FWIW once I noticed that Guix had adopted the Contributor Covenant, it
> factored strongly into my decision to stop contributing to the project
> last year.

Interesting. I too am eager understand your thinking on this.

When thinking about this issue today, I remembered some of Sage Sharp's 
writings [0][1]. What struck me about those writings is that it is not 
just about the language in our policies, but about how we use the policies 
when conducting ourselves as a community. In particular, it is about more 
than just how we communicate. It is about who is included and empowered in 
the community, and how we handle problems that arise. Getting all of this 
right is hard work, and I am happy to take all the advice I can get from 
people who have done more thinking and had more real world experience in 
this area, whether that be the Contributor Covenant, the GNU Kind 
Communication Guidelines, or other writings about community building (even 
those not specific to software).

When embarking on the hard work or community building (like the hard work 
of promoting software freedom), I find it helpful to see where we are 
heading. In Guix the Free Software Distribution Guidelines did this for 
the software freedom issues, and, while perhaps imperfect, the CoC did 
this for the community building issues. Regardless of how we sort out the 
details of implementation, I hope that we set, document, and communicate a 
high goal for our community building work.

Best,
Jack

P.S. Apologies if guix-devel is not the right place to be having this 
conversation. I like Guix a lot and am interested in it being a just 
community.

[0] http://sage.thesharps.us/2016/01/25/code-of-conducts-warning-signs/
[1] http://sage.thesharps.us/2015/10/06/what-makes-a-good-community/

  reply	other threads:[~2018-10-24  3:03 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.20.1810232158410.2975@marsh.hcoop.net \
    --to=jackhill@jackhill.us \
    --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 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.