all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eshel Yaron <me@eshelyaron.com>, emacs-devel@gnu.org
Subject: Re: Blog post
Date: Wed, 10 Jan 2024 15:14:34 -0800	[thread overview]
Message-ID: <CADwFkm=FP2xw968RssUoOYSxhDG1mjGzpuXFjhW8dSP4vZgeXQ@mail.gmail.com> (raw)
In-Reply-To: <m15y11tg4s.fsf@dazzs-mbp.home>

Hi Eshel,

[Emacs co-maintainer here, but I'm only speaking for myself.  I meant to
send this in December, but never did.  So this comes a bit late.  Sorry
if it's a bit long.]

I can't speak for the people that were attacked in that post, but I can
say that it made me concerned.  In particular, it seemed far removed
from the type of culture that we want to promote in Emacs development.

I thought about its purpose, and had a few guesses for what it might all
be about.  One option I considered was that it was simply someone making
a mistake due to not considering in advance the impact that words might
have.  It seems like this was indeed the case here, and that's good.

Emacs is a small church, and we need to always keep our shared goal in
mind.  I think everyone fundamentally agrees that sowing distrust cannot
help further our goals.  It's when the going gets rough, and the
technical disagreements are extra sharp, that we need to pay particular
attention to how we communicate and treat each other.

Let's be sensitive to and respect that some people might still be hurt
and upset by the incident.  That said, I believe that everyone deserves
a second chance.  So for my part at least, the matter is settled with
the above apology.

In addition to your apology, I also note that your original blog post
has been replaced with a simple notice of its retraction.  In my book,
that also goes a long way.

Hopefully, your apology will have made this episode somewhat less taxing
for Thierry and Eli.  Let's hope that both of them will carry on their
outstanding work for Emacs.  I also very much hope to see you continuing
to contribute to Emacs going forward, of course.

A month has now passed, and soon that will be a year.  Patches and
technical discussions will make that time go by faster, and we have
important work to do.  So let's get to it.



  parent reply	other threads:[~2024-01-10 23:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14  7:09 Blog post Eshel Yaron
2023-12-14  7:56 ` Christopher Dimech
2023-12-14  8:30   ` Dr. Arne Babenhauserheide
2023-12-14  9:22     ` Christopher Dimech
2023-12-14  9:29       ` Dr. Arne Babenhauserheide
2023-12-14 12:16         ` Christopher Dimech via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2023-12-14 12:46           ` Dr. Arne Babenhauserheide via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2023-12-14 13:11             ` Emanuel Berg
2023-12-14 16:20             ` Christopher Dimech via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2023-12-14 17:01               ` Eli Zaretskii
2023-12-14 18:57                 ` Christopher Dimech via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2023-12-14  9:33       ` Eli Zaretskii
2024-01-10 23:14 ` Stefan Kangas [this message]
2024-01-11  9:26   ` Eshel Yaron

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='CADwFkm=FP2xw968RssUoOYSxhDG1mjGzpuXFjhW8dSP4vZgeXQ@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=me@eshelyaron.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.