From: Yuchen Pei <hi@ypei.me>
To: Emacs Devel <emacs-devel@gnu.org>
Subject: NonGNU ELPA rules regarding nonfree software
Date: Thu, 12 Aug 2021 23:25:49 +1000 [thread overview]
Message-ID: <87eeayyeua.fsf@ypei.me> (raw)
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
Hello,
I notice that org-mac-link.el in org-contrib[1] interacts with
many nonfree programs. There is also a bullet point in the NonGNU
ELPA readme[2], saying:
> The package must deliver its full functionality and convenience
> on a
> completely free platform based on the GNU operating system (in
> practice, GNU/Linux), working exclusively with other free
> software.
> Otherwise, it would act as an inducement to install nonfree
> systems
> or other nonfree software, and that would work against our
> cause.
>
> However, as an exception it is ok for a package to provide, on
> some
> non-GNU operating systems, features that the rest of Emacs (plus
> GNU
> ELPA and NonGNU ELPA) already supports on GNU.
>
> This is a moral issue. See https://www.gnu.org/prep/standards/,
> node System Portability. The reason for this rule is that at no
> time, in no way, should a NonGNU ELPA package put users who
> defend
> their freedom at a disadvantage compared with those who
> surrender
> their freedom.
[1]
https://git.sr.ht/~bzg/org-contrib/tree/master/item/lisp/org-mac-link.el
[2]
https://git.savannah.gnu.org/cgit/emacs/nongnu.git/plain/README.org
If wonder if there is a contradiction here.
--
Best,
Yuchen
PGP Key: 47F9 D050 1E11 8879 9040 4941 2126 7E93 EF86 DFD0
<https://ypei.me/assets/ypei-pubkey.txt>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 243 bytes --]
next reply other threads:[~2021-08-12 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 13:25 Yuchen Pei [this message]
2021-08-13 3:11 ` NonGNU ELPA rules regarding nonfree software Richard Stallman
2021-08-16 5:41 ` Yuchen Pei
2021-08-16 5:43 ` Yuchen Pei
2021-08-18 3:20 ` Richard Stallman
2021-08-18 12:37 ` Yuchen Pei
2021-08-19 2:35 ` Richard Stallman
2021-08-16 12:15 ` Eli Zaretskii
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=87eeayyeua.fsf@ypei.me \
--to=hi@ypei.me \
--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).