Re: Why are so many great packages not trying to get included in GNU Emacs?

[Stefan Monnier]

> I think it could be even simpler than that: ELPA is built every 24 hours
> right now. If we just registered external repos with ELPA, part of the
> build process could be pulling from those repos automatically, once per
> day. Package authors already have a mechanism for manually triggering a
> release: incrementing the package version number. There's no harm in
> ELPA bringing in new commits from the externals, if the author is still
> in control of when a new version is released.

I think it's important that we don't "pull" from "random" places like
Github repositories.  More specifically, the "push to elpa.git" serves
as a confirmation that someone thinks this code is appropriate for
elpa.git (typically the concern being copyright).

For a pure "distribution only", we already have MELPA.

But yes, like "ndame" suggests, we could pull from some other
repositories kept under the gnu.org domain and then give write access
more liberally (or differently) to those repositories.  I think
currently creating new repositories with different access rights on
savannah is administrively too heavy to have a separate "savannah
project" per GNU ELPA package.  My hope is that the "new forge"
(Gitea/Pagure/SourceHut?) will solve this problem, but I don't know when
it will be available.


        Stefan