From: Antoine Kalmbach <ane@iki.fi>
To: emacs-devel@gnu.org
Subject: NonGNU ELPA and release frequency
Date: Fri, 23 Oct 2020 14:59:07 +0300 [thread overview]
Message-ID: <8lm0yhtuul6tmc.fsf@iki.fi> (raw)
Given that the details of NonGNU ELPA are still being fleshed out, has
there been any discussion on how often NonGNU ELPA packages are
released into the package repository?
Suppose I am a package author upstream on a package that isn't in GNU
ELPA. This package is maintained in an external repository somewhere on
the net. I release a new version, pushing the commit into the
repository. Now the following things are unclear:
1. If I want my changes to appear in NonGNU ELPA, should I:
a. Send a patch with the changes to the appropriate mailing lists
(emacs-devel or bug-gnu-emacs?)
b. Send a request to pull the changes to ibid.
c. Push changes to some reference
d. Email a mailing list announcing the changes and wait for someone
to update the package
2. How often would NonGNU packages be updated? Will it be up to each
individual package, or would there be recurring (e.g. monthly)
"distributions" of the whole package set, so that a package and all
its dependents would effectively be "frozen" until a regular
update?
3. Would NonGNU ELPA have some sort of automated build system for
checking that packages meet some sort of quality checks, for
instance, checking that packages can be byte compiled without
errors, checking documentation using checkdoc, and verifying the
license is appropriate, etc.
Do any of those questions make sense? Lately on several forums there has
been much discussion about MELPA and other third-party repositories, and
the nature of those discussions strongly indicates that NonGNU ELPA is
necessary and requires attention.
--
Antoine Kalmbach
next reply other threads:[~2020-10-23 11:59 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 11:59 Antoine Kalmbach [this message]
2020-10-23 12:24 ` NonGNU ELPA and release frequency Stefan Kangas
2020-10-23 18:25 ` Antoine Kalmbach
2020-10-24 3:45 ` Richard Stallman
2020-10-24 13:51 ` Antoine Kalmbach
2020-10-26 9:56 ` Philip K.
2020-10-27 3:41 ` Richard Stallman
2020-10-24 3:50 ` Richard Stallman
2020-10-24 7:08 ` Jean Louis
2020-10-24 8:41 ` Eli Zaretskii
2020-10-24 12:06 ` Jean Louis
2020-10-24 12:54 ` Eli Zaretskii
2020-10-24 14:12 ` Jean Louis
2020-10-24 14:16 ` Eli Zaretskii
2020-10-24 14:21 ` NonGNU ELPA Jean Louis
2020-10-24 14:50 ` Eli Zaretskii
2020-10-24 14:25 ` NonGNU ELPA and release frequency Antoine Kalmbach
2020-10-24 14:29 ` NonGNU ELPA Jean Louis
2020-10-24 14:40 ` Antoine Kalmbach
2020-10-24 16:37 ` Michael Albinus
2020-10-24 17:05 ` Stefan Kangas
2020-10-24 18:00 ` Antoine Kalmbach
2020-10-24 19:12 ` Michael Albinus
2020-10-25 11:40 ` Michael Albinus
2020-10-25 12:20 ` Antoine Kalmbach
2020-10-25 3:48 ` NonGNU ELPA and release frequency Richard Stallman
2020-10-25 10:29 ` Dmitry Gutov
2020-10-25 13:50 ` Stefan Monnier
2020-10-25 14:54 ` Ivan Yonchovski
2020-10-25 15:15 ` Antoine Kalmbach
2020-10-26 4:10 ` Richard Stallman
2020-10-26 10:35 ` NonGNU ELPA Jean Louis
2020-10-27 3:47 ` Richard Stallman
2020-10-26 17:37 ` NonGNU ELPA and release frequency Dmitry Gutov
2020-10-27 3:45 ` Richard Stallman
2020-10-25 3:48 ` Richard Stallman
2020-10-24 18:47 ` Stefan Monnier
2020-10-26 4:10 ` 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=8lm0yhtuul6tmc.fsf@iki.fi \
--to=ane@iki.fi \
--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).