From: Eli Zaretskii <eliz@gnu.org>
To: Robert Cochran <robert-emacs@cochranmail.com>
Cc: clement.pit@gmail.com, emacs-devel@gnu.org
Subject: Re: Development suggestions from an ENSIME developer
Date: Sat, 23 Jul 2016 10:30:34 +0300 [thread overview]
Message-ID: <83mvl8x145.fsf@gnu.org> (raw)
In-Reply-To: <87oa5pnvam.fsf@cochranmail.com> (message from Robert Cochran on Fri, 22 Jul 2016 15:48:49 -0700)
> From: Robert Cochran <robert-emacs@cochranmail.com>
> Date: Fri, 22 Jul 2016 15:48:49 -0700
> Cc: emacs-devel@gnu.org
>
> I know that I'm a relative newcomer to the Emacs lists, and that my
> opinion isn't going to be as highly esteemed as some, but this issue is
> important to me and I feel like I need to make my voice heard.
It has been heard, thanks.
There was never any need to have a code of conduct on the Emacs lists,
and I don't see any need for that now. Telling people to be nice is
not useful: it has effect only on those who already are. Telling them
not to be assholes can in some quarters rightfully be interpreted as
an offense to their intelligence. Etc. etc. Frankly, having read the
proponents of such a code in the discussion that triggered this one, I
think at least some of them should look in the mirror before they
preach others.
The only conduct we don't tolerate here is extreme rudeness far beyond
any reasonably-civilized behavior. And even that needs to be repeated
several times, before some kind of "police action" will be taken.
There were very few, maybe two or three, of such cases here. In other
cases, people might be politely told to take some irrelevant
discussion elsewhere (and even that happens only if a small group is
interested in that topic).
And that's how it should be, IMO: we should not shut up discussions or
oust their originators just because we don't like the way they express
their opinions, or how they format their messages. A movement that
aspires to bring more freedom cannot IMO manage its forums in any
other way.
next prev parent reply other threads:[~2016-07-23 7:30 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 [this message]
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
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=83mvl8x145.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=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 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.