unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Paul W. Rankin" <pwr@skeletons.cc>
Cc: kfogel@red-bean.com, emacs-devel@gnu.org
Subject: Re: Proposal for an emacs-humanities mailing list
Date: Mon, 30 Nov 2020 18:02:48 +0200	[thread overview]
Message-ID: <83y2iikf2v.fsf@gnu.org> (raw)
In-Reply-To: <0cb78b67cf068450753d2de1457eca4a@skeletons.cc> (pwr@skeletons.cc)

> Date: Mon, 30 Nov 2020 16:03:50 +1000
> From: "Paul W. Rankin" <pwr@skeletons.cc>
> Cc: Karl Fogel <kfogel@red-bean.com>, emacs-devel@gnu.org
> 
> On 2020-11-30 15:41, Eli Zaretskii wrote:
> > Do you really think this will work?  I don't, FWIW.  How can a group
> > of people not involved with development answer non-trivial questions,
> > suggest reporting useful bugs and feature requests etc.?  Even
> > help-gnu-emacs would not be the same without several developers
> > dwelling there.  Posting to emacs-devel is a slippery path to making
> > this new list a branch of the existing ones, something that this
> > initiative wants explicitly to avoid.  I'm probably missing something
> > here.
> 
> There's no cause to worry. The three things you list -- non-trivial 
> questions, bugs, and feature requests -- are already covered by the 
> other lists, where diligent Emacs developers remain on guard. There 
> exists a discussion scope outside of that scope.

Then I think this different scope should be somehow mentioned in the
list description.  Could you give some examples of what you envision
as good topics to discuss on this new list, and how they differ from
discussions on help-gnu-emacs or emacs-devel?  With such examples in
hand, we could try coming up with a better description, because what
you proposed is too similar to help-gnu-emacs.

One other thing is that the list will need a moderator, to handle the
small number of valid posts by those who aren't subscribers.  Would
you like to be the moderator, and if so, would you like the moderation
requests to arrive at the email address you used in this discussion?
If not, what other moderator address should I use?

Once we have these two aspects figured out, I will create the list.

Thanks.



  reply	other threads:[~2020-11-30 16:02 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 [this message]
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
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=83y2iikf2v.fsf@gnu.org \
    --to=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).