From: Drew Adams <drew.adams@oracle.com>
To: Karl Fogel <kfogel@red-bean.com>, Eli Zaretskii <eliz@gnu.org>
Cc: pwr@skeletons.cc, emacs-devel@gnu.org
Subject: RE: Proposal for an emacs-humanities mailing list
Date: Mon, 30 Nov 2020 15:17:23 -0800 (PST) [thread overview]
Message-ID: <2a314856-5655-4479-9bc4-d8f60cb14af3@default> (raw)
In-Reply-To: <87eekao7qq.fsf@red-bean.com>
Chiming in here, but not with a strong opinion...
> The cost if the experiment fails is a dead list sitting on a server.
> That cost doesn't seem very high to me in any case
... but there's also the possible cost of others who
might be interested or able to help missing some info
or questions that they might be able to help with.
emacs-tangents is hardly used. It's essentially
a catch-all.
help-emacs-window isn't used a lot. But it's pretty
precisely targeted. "Humanities" is not (IMO).
An alternative might be to start by inviting potential
"humanities" participants to use help-gnu-emacs (or
emacs-tangents?), but with a particular prefix in the
Subject line. If volume becomes reasonably high then
a new mailing list could be spun off to handle it (but
with the attendant lack of visibility to some that I
mentioned above).
The same approach could be adopted for any other
potential "subgroup" of an Emacs list. And it makes
it pretty easy for people to filter, sort, etc.,
whether or not they're interesting in topics of the
subgroup.
Just a thought. The basic idea is to try something
out, to see how much traffic/interest there is,
before sending people off to a new list.
next prev parent reply other threads:[~2020-11-30 23:17 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 6:57 Proposal for an emacs-humanities mailing list Paul W. Rankin via Emacs development discussions.
2020-11-30 1:24 ` Karl Fogel
2020-11-30 3:16 ` Bob Newell
2020-12-01 5:20 ` Richard Stallman
2020-12-01 10:59 ` 황병희
2020-11-30 3:31 ` Eli Zaretskii
2020-11-30 3:55 ` Paul W. Rankin via Emacs development discussions.
2020-11-30 4:40 ` Karl Fogel
2020-11-30 5:41 ` Eli Zaretskii
2020-11-30 6:03 ` Paul W. Rankin via Emacs development discussions.
2020-11-30 16:02 ` Eli Zaretskii
2020-12-02 14:54 ` Eli Zaretskii
2020-12-03 8:30 ` Paul W. Rankin via Emacs development discussions.
2020-12-03 9:15 ` Protesilaos Stavrou
2020-12-03 10:35 ` Paul W. Rankin via Emacs development discussions.
2020-12-12 12:38 ` Eli Zaretskii
2020-12-14 22:28 ` Karl Fogel
2020-12-03 9:43 ` Jean Louis
2020-12-03 10:34 ` Paul W. Rankin via Emacs development discussions.
2020-12-03 10:16 ` Joost Kremers
2020-12-04 5:55 ` Richard Stallman
2020-12-03 20:10 ` Arthur Miller
2020-12-03 20:48 ` Stefan Monnier
2020-12-03 21:07 ` Arthur Miller
2020-12-03 23:22 ` Stefan Monnier
2020-12-03 23:41 ` Arthur Miller
2020-11-30 13:39 ` Leo Vivier
2020-11-30 17:23 ` Eric Abrahamsen
2020-11-30 21:27 ` Karl Fogel
2020-11-30 23:17 ` Drew Adams [this message]
2020-11-30 23:29 ` Gregory Heytings via Emacs development discussions.
2020-11-30 23:31 ` Karl Fogel
2020-12-01 8:57 ` tomas
2020-12-01 11:43 ` Jean Louis
2020-12-01 16:46 ` Drew Adams
2020-12-01 20:55 ` tomas
2020-12-01 17:42 ` Eric Abrahamsen
2020-12-02 4:29 ` Richard Stallman
2020-12-02 6:41 ` Eric Abrahamsen
2020-12-01 9:17 ` tomas
2020-12-01 11:40 ` Jean Louis
2020-11-30 9:36 ` Michael Albinus
2020-11-30 16:12 ` Eli Zaretskii
2020-11-30 16:19 ` Corwin Brust
2020-11-30 19:33 ` Jean Louis
2020-11-30 3:53 ` Zhu Zihao
2020-11-30 4:46 ` Richard Stallman
2020-11-30 9:13 ` Lars Ingebrigtsen
2020-11-30 12:03 ` Gregory Heytings via Emacs development discussions.
2020-11-30 13:29 ` Pankaj Jangid
2020-11-30 16:33 ` Eli Zaretskii
2020-11-30 14:36 ` Jean Louis
2020-11-30 16:13 ` Corwin Brust
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=2a314856-5655-4479-9bc4-d8f60cb14af3@default \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.com \
--cc=pwr@skeletons.cc \
/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).