From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59609@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>
Subject: bug#59609: 29.0.50; [PATCH] Better advertise (Non-)GNU ELPA in emacs manual
Date: Fri, 08 Sep 2023 12:43:15 -0400 [thread overview]
Message-ID: <jwvv8ckhb8c.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <831qf8yj2l.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 08 Sep 2023 14:56:34 +0300")
> It's a good starting point, but the copyright assignment issue is not
> the only issue (not even the main one, from my POV). The main issue
> with NonGNU ELPA, IMO, is that packages there don't necessarily adhere
> to the Emacs coding conventions, are not supervised by the Emacs
> maintainers, and do not have to coordinate their development decisions
> with the Emacs team. So their integration into Emacs could be less
> seamless than that of packages from GNU ELPA.
FWIW, GNU ELPA packages don't necessarily "adhere to the Emacs coding
conventions" either and neither are they all "supervised by the Emacs
maintainers" or "have to coordinate their development decisions with the
Emacs team". Some do, but not all of them by a long shot.
In practice the real deciding factor *is* the copyright assignment
(which often ends up selecting for a kind of "philosophical agreement"
about the primacy of ethical goals over technical ones).
Stefan
next prev parent reply other threads:[~2023-09-08 16:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 13:44 bug#59609: 29.0.50; [PATCH] Better advertise (Non-)GNU ELPA in emacs manual Stefan Kangas
2022-11-26 14:20 ` Eli Zaretskii
2023-09-08 11:25 ` Stefan Kangas
2023-09-08 11:56 ` Eli Zaretskii
2023-09-08 15:04 ` Stefan Kangas
2023-09-11 0:40 ` Richard Stallman
2023-09-11 2:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 15:47 ` Drew Adams
2023-09-08 16:43 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-08 18:29 ` Eli Zaretskii
2023-09-08 18:47 ` Michael Albinus
2023-09-08 20:10 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11 0:40 ` Richard Stallman
2022-11-27 22:54 ` Richard Stallman
2022-11-30 23:54 ` Richard Stallman
2022-12-01 3:49 ` Stefan Kangas
2022-12-03 23:40 ` Richard Stallman
2022-12-04 0:00 ` Stefan Kangas
2022-12-14 22:20 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvv8ckhb8c.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=59609@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.