all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Dunn <dunn.alex@gmail.com>
To: "John Wiegley" <jwiegley@gmail.com>,
	"Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Development suggestions from an ENSIME developer
Date: Sat, 06 Aug 2016 11:42:32 -0700	[thread overview]
Message-ID: <m2shuhlox3.fsf@snow.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <m2popqgzff.fsf@newartisans.com>

John Wiegley <jwiegley@gmail.com> writes:

> Some make the argument that publishing a code of conduct announces to others
> what our standards are, and that we are accepting of all peoples, of all
> persuasions.

It does this, and it’s good to have it formalized, but it’s also a very
useful way to signal that the community has chosen to adopt a certain
stance; namely one according to which social justice _is_ important.  If
this upsets people who sneer at “SJWs” and share ESR’s paranoid
fantasies about feminists trying to honeypot Linus, then so much the
better.  A community can’t be welcoming to everyone, when some groups
are openly antagonistic toward others.  A code of conduct helps clarify
which groups can expect to feel welcome in a community, and which aren’t
(e.g., those who compare CoCs to nuclear weapons:
https://github.com/fontforge/fontforge/issues/2765#issuecomment-237721149).



  reply	other threads:[~2016-08-06 18:42 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20 13:54 Development suggestions from an ENSIME developer Lars Ingebrigtsen
2016-07-20 14:02 ` Clément Pit--Claudel
2016-07-22 22:48   ` Robert Cochran
2016-07-23  7:30     ` Eli Zaretskii
2016-07-23  9:00     ` Lars Ingebrigtsen
2016-07-23 19:52       ` Richard Stallman
2016-07-23 13:50     ` Clément Pit--Claudel
2016-07-23 20:14     ` Phillip Lord
2016-07-25 18:34       ` Robert Cochran
2016-08-03  6:05   ` John Wiegley
2016-08-06 18:42     ` Alex Dunn [this message]
2016-07-20 14:03 ` Dmitry Gutov
2016-07-20 14:08   ` Lars Ingebrigtsen
2016-07-20 14:12     ` Dmitry Gutov
2016-07-20 14:23       ` Christian Kruse
2016-07-20 14:41         ` Dmitry Gutov
2016-07-20 14:30 ` Christian Kruse
2016-07-20 14:44   ` Lars Ingebrigtsen
2016-07-20 15:02     ` Clément Pit--Claudel
2016-07-20 15:07       ` Lars Ingebrigtsen
2016-07-20 15:31         ` Clément Pit--Claudel
2016-07-20 17:00 ` Stefan Monnier
2016-07-21 18:40   ` Phillip Lord
2016-07-21 19:30     ` Eli Zaretskii
2016-07-21 20:22       ` Stefan Monnier
2016-07-21 21:26         ` Christian Kruse
2016-07-21 22:04         ` Dmitry Gutov
2016-07-21 20:23       ` Phillip Lord
2016-07-21 20:50         ` joakim
2016-07-22  6:59         ` Eli Zaretskii
2016-07-22 10:46           ` Lars Ingebrigtsen
2016-07-22 11:48             ` Lars Ingebrigtsen
2016-07-22 13:00               ` Robert Weiner
2016-07-22 13:34                 ` Eli Zaretskii
2016-07-22 14:28                   ` Robert Weiner
2016-07-22 14:45             ` Ted Zlatanov
2016-07-22 13:35           ` Stefan Monnier
2016-07-22 14:38             ` Eli Zaretskii
2016-07-22 14:56               ` Stefan Monnier
2016-07-22 15:58                 ` Phillip Lord
2016-07-22 15:47           ` Phillip Lord

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=m2shuhlox3.fsf@snow.i-did-not-set--mail-host-address--so-tickle-me \
    --to=dunn.alex@gmail.com \
    --cc=clement.pit@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=jwiegley@gmail.com \
    /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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.