unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: Robert Cochran <robert-emacs@cochranmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Development suggestions from an ENSIME developer
Date: Sat, 23 Jul 2016 09:50:01 -0400	[thread overview]
Message-ID: <4fabc97e-b5db-06ba-347b-72bbfa47ed8b@gmail.com> (raw)
In-Reply-To: <87oa5pnvam.fsf@cochranmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1322 bytes --]

On 2016-07-22 18:48, Robert Cochran wrote:
>>> I for one would welcome a code of conduct :) These things tend to
>>> send an explicit positive message, and there are virtually no
>>> downsides to having one.
> 
> I disagree.
> 
> When I think 'Code of Conduct', I inevitably think of the Social
> Justice Warriors. I think very lowly of the SJWs

Thanks for sharing your opinion.  If this is the only downside, I still stand by "virtually no downsides".

We have two groups of people: one that feels unsafe in some online communities, and which we might make more comfortable by explicitly stating that contributors should behave nicely to each other (which, as has been pointed out, is not asking much: this mailing list is rather civil already).  Another one that feels upset about such a document, based on vaguely accusatory inferences about who might have suggested the introduction of said document — although it doesn't affect them personally in any way.

> and I'm always set on edge, at least a little, when I see that a
> project has adopted a CoC. That tends to be an indicator that the
> SJWs have infected a project.

Conversely, I'm set on the edge when I see someone refer to "Social Justice Warriors", especially in the context of adopting a Code of Conduct :)

Cheers,
Clément.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2016-07-23 13:50 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=4fabc97e-b5db-06ba-347b-72bbfa47ed8b@gmail.com \
    --to=clement.pit@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=robert-emacs@cochranmail.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).