From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 59609@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#59609: 29.0.50; [PATCH] Better advertise (Non-)GNU ELPA in emacs manual
Date: Fri, 08 Sep 2023 14:56:34 +0300 [thread overview]
Message-ID: <831qf8yj2l.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmny5XWbg=jkEzQ3LPGCx5NU+XvTMXiNQYSVfxHmRfAQyw@mail.gmail.com> (message from Stefan Kangas on Fri, 8 Sep 2023 04:25:54 -0700)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Fri, 8 Sep 2023 04:25:54 -0700
> Cc: 59609@debbugs.gnu.org, monnier@iro.umontreal.ca
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > This sounds OK, but begs the question: what's short description of NonGNU
> > ELPA? Since we describe GNU ELPA, let's also describe the other one. The
> > purpose should IMO be to explain to the reader, or at least hint why we
> > maintain two separate archives.
>
> What do you think of the below?
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.
next prev parent reply other threads:[~2023-09-08 11:56 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 [this message]
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
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
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=831qf8yj2l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59609@debbugs.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 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).