unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
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, 8 Sep 2023 08:04:53 -0700	[thread overview]
Message-ID: <CADwFkm=tPS8tBUnk4+tPksgLg+eXK3G5eBFSO_uxcYkKESZFvA@mail.gmail.com> (raw)
In-Reply-To: <831qf8yj2l.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

> 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.

Thanks, based on that I ended up with this:

modified   doc/emacs/package.texi
@@ -35,10 +35,20 @@ Packages
 name of a package, and displays a help buffer describing the
 attributes of the package and the features that it implements.

-  By default, Emacs downloads packages from a package archive
-maintained by the Emacs developers and hosted by the GNU project.
-Optionally, you can also download packages from archives maintained by
-third parties.  @xref{Package Installation}.
+  By default, Emacs downloads packages from GNU ELPA
+(@url{https://elpa.gnu.org/}) and NonGNU ELPA
+(@url{https://elpa.nongnu.org/}), two package archives maintained by
+the Emacs developers and hosted by the GNU project.  @dfn{GNU ELPA}
+contains packages that are available for use with Emacs, but are
+distributed separately from Emacs itself.  @dfn{NonGNU ELPA} contains
+a selection of third-party packages that are not supervised by the
+Emacs maintainers, do not necessarily adhere to the Emacs coding
+conventions, and do not coordinate their development decisions with
+the Emacs team.  They have been selected to be useful to many people,
+but their integration into Emacs could be less seamless than that of
+packages from GNU ELPA.  Optionally, you can also download packages
+from archives maintained by third parties.  @xref{Package
+Installation}.





  reply	other threads:[~2023-09-08 15:04 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 [this message]
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='CADwFkm=tPS8tBUnk4+tPksgLg+eXK3G5eBFSO_uxcYkKESZFvA@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=59609@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).