all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jeremiah@pdp10.guru
To: guix-devel@gnu.org
Subject: Re: Stop it. Formerly - Re: Promoting the GNU Kind Communication Guidelines?
Date: Tue, 06 Nov 2018 01:19:42 +0000	[thread overview]
Message-ID: <87lg670zpt.fsf@ITSx01.pdp10.guru> (raw)


Perhaps, it is human nature to think in terms of conflict; right and wrong.

Absolutes are naturally attractive, especially to those of us who
program. It just feels so natural because what we work with the most is
in many ways exactly like that.

But one needs not get stuck on such a perspective.

The Code of Conduct is an entirely rational and correct solution to a
population of only cognitively normative individuals.

But that is not the argument being made by both sides.

But rather we as a community have those who fall outside of bounds of
what is considered Cognitively Normal in our set of productive members
and for them the Code of Conduct is a point of contention.

It is entirely counter productive for that population and it isn't what
historically been effective at growing productive software development
communities in the past.

But we need not think in such limited terms as have or not have in
regards to the Code of Conduct but rather; can we carve out a zone of
exclusion where those who are productive members of the community can
act and interact without fear of the Code of Conduct or other normative
pressure placed upon them?

I propose we institute a Tony Stark <-> Pepper Pots mechanism.

We create channels for people who can't or will not conform to the Code
of Conduct are free to collaborate and contribute to the project through
a few designated individuals who have thick skin and are willing to put
up with Flaming assholes in private for the good of the project.

There are multiple details we will need to hammer out over time but the
general idea is we stop trying to force people who are different from
contributing in a positive manner.

-Jeremiah

             reply	other threads:[~2018-11-06  1:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06  1:19 Jeremiah [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-10-28 11:58 Promoting the GNU Kind Communication Guidelines? HiPhish
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
2018-11-06 12:55               ` Ludovic Courtès
2018-11-06 17:23               ` Marius Bakke
2018-11-06 17:41                 ` HiPhish

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=87lg670zpt.fsf@ITSx01.pdp10.guru \
    --to=jeremiah@pdp10.guru \
    --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.