Re: non-gnu elpa issue tracking

[Michael Albinus]

Tim Cross <theophilusx@gmail.com> writes:

Hi,

> Many people have selected Github for hosting simply because it was the
> best known solution. With a little encouragement, they would probably
> be willing to move to at least GitLab, which offers many of the
> similar convenience features of Github.  Being able to host your
> package in non-GNU ELPA might be that encouragement.

We might also consider to give package maintainers an incentive to host
on GitLab. We run already a GitLab instance on emba.gnu.org. This
provides automatic regression tests for all Emacs branches, triggered by
any commit to Emacs git repository.

Currently, I'm thinking about to extend this for GNU ELPA packages. That
is, if a given package provides an ERT test file, we could trigger its
run for every commit in the package repository. Maybe even for different
Emacs versions in parallel, based on what the package says in its
Package-Requires: header.

All of this is in the very early stage of brainstorming, 'tho. I don't
know what would be the implications for GNU ELPA compared with NonGNU
ELPA packages. And this does not cover the problem of issue tracking
yet.

Best regards, Michael.