From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Re: Proposal for an emacs-humanities mailing list
Date: Tue, 01 Dec 2020 22:41:05 -0800 [thread overview]
Message-ID: <87zh2wlnge.fsf@ericabrahamsen.net> (raw)
In-Reply-To: E1kkJlq-00077D-77@fencepost.gnu.org
Richard Stallman <rms@gnu.org> writes:
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> > The kinds of tips and
> > information that academics will find useful might lend themselves well
> > to a "knowledgebase" sort of presentation, and emacswiki could be ideal
> > for that. We could have a separate area on the wiki, and at the top note
> > that if you want to discuss any of the information in that section,
> > write to emacs-help with such-and-such a prefix.
>
> It might be useful, but it might backfire at a deeper level.
>
> Correct me if I'm wrong, but my understanding is that the people
> who set up emacswiki do not have a connection to the GNU Project,
> and do not see a problem in advising people to use nonfree software.
> More generally, they present nonfree software as acceptable
> and not as something we should all shun.
>
> If that is so, directing people to emacswiki exacerbates the promotion
> of that point of view. That would be a reason for us to make some
> other choice. When we ask people to write material about using Emacs,
> we would be more effective if we ask people to publish it via gnu.org.
I wasn't aware of these issues with emacswiki, thank you for bringing
that up.
It wasn't so much that it had to be emacswiki, but that I think this
effort might be best served by a semi-static knowledgebase, with a
mailing list being a supplement to that.
next prev parent reply other threads:[~2020-12-02 6:41 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
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 [this message]
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=87zh2wlnge.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=emacs-devel@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).