From: John Wiegley <jwiegley@gmail.com>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Development suggestions from an ENSIME developer
Date: Tue, 02 Aug 2016 23:05:24 -0700 [thread overview]
Message-ID: <m2popqgzff.fsf@newartisans.com> (raw)
In-Reply-To: <46f603db-cf91-495d-d330-87b3538b7872@gmail.com> ("Clément Pit--Claudel"'s message of "Wed, 20 Jul 2016 10:02:03 -0400")
[-- Attachment #1: Type: text/plain, Size: 1700 bytes --]
>>>>> "CP" == Clément Pit--Claudel <clement.pit@gmail.com> writes:
CP> I for one would welcome a code of conduct :) These things tend to send an
PC> explicit positive message, and there are virtually no downsides to having
PC> one. LibrePlanet, Mailman, and GNU Health already seem to have one.
Hi Clément,
I appreciate the desire for a code of conduct, which is that we should all be
courteous and respectful of one another, united in our common effort to build
the future of Emacs.
If I thought having a code of conduct would make any difference, we would have
one. However, its mere existence does not stop anyone from saying whatever
they want; and its absence does not stop me from withdrawing their right to
post if I feel their contributions are inappropriate (and this list _is_
moderated, though no one has ever been filtered yet).
When people become abrasive or discouraging to others, I say something about
it. But even if a code of conduct existed, and said the same thing, I would
still need to repeat it here. The published document does not save me the
effort, since the problem exists _here_.
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. If we think this is what we've been missing to win new users,
that's certainly something to consider; but the fact is, everyone IS welcome,
abuse of any kind is NOT tolerated, and I think the people contributing here
already know that.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 629 bytes --]
next prev parent reply other threads:[~2016-08-03 6:05 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2popqgzff.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=clement.pit@gmail.com \
--cc=emacs-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/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.