Re: NonGNU ELPA and release frequency

[Stefan Monnier]

> 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