all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "John Wiegley" <johnw@newartisans.com>
To: John Yates <john@yates-sheets.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Taming some chaos
Date: Sat, 17 Oct 2015 22:30:46 -0700	[thread overview]
Message-ID: <m2lhb04ubd.fsf@newartisans.com> (raw)
In-Reply-To: <CAJnXXoiAxCY6bR76JN8XR6kcgvdj6EX4cHpDpYUHou9R-GWx+A@mail.gmail.com> (John Yates's message of "Sat, 17 Oct 2015 11:16:02 -0400")

>>>>> John Yates <john@yates-sheets.org> writes:

> The Emacs community has long felt like a collection of bright, polite coders
> pursuing individual visions and scratching personal itches. In your postings
> to the ML it seemed you were interested in stepping forward to provide the
> leadership needed to get us to rally to vision of an enticing Emacs future.
> Articulating such a vision inherently involves contrasting it with the
> current state of affairs. I had hoped that my note would be taken as a
> contribution to a discussion about things could be improved.

Hi John!

I apologize for apparently having misread your intent completely. Reading this
last message, I couldn't agree with you more, both in sentiment and approach.
I think we want almost exactly the same things.

Please allow me take back any criticism of your ideas as being too wild, and
encourage you to rephrase them with an eye to "maintaining existing value".
Can we correct past decisions in the light of new advances, in a way that
carries forward the merits of that past?

I find myself in the strange position of wanting change -- even radical change
-- while equally wanting to respect the tremendous value and experience we've
built up over the decades. Striking this balance at the right points is key.

John



      reply	other threads:[~2015-10-18  5:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 11:47 Taming some chaos John Yates
2015-10-16 15:36 ` Dmitry Gutov
2015-10-16 23:20 ` John Wiegley
2015-10-17 15:16   ` John Yates
2015-10-18  5:30     ` John Wiegley [this message]

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=m2lhb04ubd.fsf@newartisans.com \
    --to=johnw@newartisans.com \
    --cc=emacs-devel@gnu.org \
    --cc=john@yates-sheets.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.