From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Richard Stallman <rms@gnu.org>
Cc: ane@iki.fi, Jean Louis <bugs@gnu.support>, emacs-devel@gnu.org
Subject: Re: NonGNU ELPA and release frequency
Date: Sun, 25 Oct 2020 09:50:21 -0400 [thread overview]
Message-ID: <jwvlffus9kz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1kWX13-0006kY-DX@fencepost.gnu.org> (Richard Stallman's message of "Sat, 24 Oct 2020 23:48:21 -0400")
> One of the inconveniences with GNU ELPA is that it is a single repo.
> Everyone who maintains a package in GNU ELPA needs write-access to the
> whole repo.
The way I plan to make NonGNU ELPA (if someone beats me to it) is to
make it work *internally* like GNU ELPA: each package would have
a corresponding branch in the nongnu.git repository.
The difference is that these branches would just be mirrors from the
corresponding upstream branch which can be kept "anywhere else", and
there'd be some automation to *pull* automatically from those
repositories (where in GNU ELPA we require maintainers to *push* to the
central repository) so the maintainers don't need write access to the
whole repository (they technically wouldn't even need to know that their
package is on nongnu.git).
Stefan
next prev parent reply other threads:[~2020-10-25 13:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 11:59 NonGNU ELPA and release frequency Antoine Kalmbach
2020-10-23 12:24 ` 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 [this message]
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=jwvlffus9kz.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=ane@iki.fi \
--cc=bugs@gnu.support \
--cc=emacs-devel@gnu.org \
--cc=rms@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).