From: Philippe Vaucher <philippe.vaucher@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Richard Stallman <rms@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Presentation of the Emacs community outside emacs-devel
Date: Fri, 8 May 2020 18:49:08 +0200 [thread overview]
Message-ID: <CAGK7Mr6UFoiaEXNrauQRbr5JKogPq8g4HWBzR0CTz3rEpQVryQ@mail.gmail.com> (raw)
In-Reply-To: <83h7wqip9x.fsf@gnu.org>
> > With this email my goal is for the "emacs-devel" ecosystem to realise
> > a bit that a lot is happening outside, and that these people usually
> > know about you but sometimes it looks like it's not the case the other
> > way around. I hope I am mistaken and that many of you already know
> > about these people/libraries and amazing work done out there.
>
> FTR, I knew about all of the people you mentioned (and then some) and
> their contributions/projects, and I think we are fortunate to have
> them working on "Emacs at large".
Great! As I said in my introduction this was mainly for Richard.
Maybe my message will turn out to be useless, but I sometimes get the
impression there's a disconnect between emacs-devel and the Emacs
users community so I tried to show that what happens "outside" (sorry
cannot find a better term) is huge in terms of investment.
Philippe
next prev parent reply other threads:[~2020-05-08 16:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 12:03 Presentation of the Emacs community outside emacs-devel Philippe Vaucher
2020-05-08 12:28 ` Eli Zaretskii
2020-05-08 13:15 ` Stefan Kangas
2020-05-08 13:58 ` Eli Zaretskii
2020-05-09 11:38 ` Arthur Miller
2020-05-09 12:16 ` Eli Zaretskii
2020-05-11 13:36 ` Arthur Miller
2020-05-11 15:25 ` Eli Zaretskii
2020-05-11 16:32 ` andres.ramirez
2020-05-08 16:49 ` Philippe Vaucher [this message]
2020-05-08 13:06 ` Dmitry Gutov
2020-05-08 13:56 ` Philippe Vaucher
2020-05-08 14:02 ` Dmitry Gutov
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=CAGK7Mr6UFoiaEXNrauQRbr5JKogPq8g4HWBzR0CTz3rEpQVryQ@mail.gmail.com \
--to=philippe.vaucher@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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 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).