[pacman-dev] Planning the move to the Arch Linux Gitlab instance

Allan McRae allan at archlinux.org
Tue May 5 06:09:50 UTC 2020

On 5/5/20 12:55 pm, Eli Schwartz wrote:
>> Mailing list:
>> New patches would no longer appear here.  I don't know how much we can
>> get gitlab to report to the mailing list, or if we even want to.  The
>> mailing list would still serve as a good place to discuss feature
>> implementation in a more public way.
> I know that you're supposed to be able to email patches to a gitlab
> address and have it generate a merge request. Not sure how notifications
> the other way work, if at all. I'd quite like to have, at a minimum, a
> post-receive notification to the mailing list like we currently have...
> If we don't allow absolutely anyone to create an account on our gitlab
> instance, then they cannot report bugs, or submit patches (even by
> email, it's a private email address tied to your account). IIRC devops
> were not eager to enable public account creation for various reasons.

On the Arch Linux DevOps channel, I was told that at least for now
accounts would be restricted, so no merge requests from those apart from
the main contributors.  We don't want bug reports to be created without
accounts, so that would stop us using this as a bug tracker.

This means we would need keep mailing lists for patch submissions (and
thus patchwork) and a separate bug tracker.  We would have to not use
the gitlab instance bug tracker at all, or else we would end with

Given the restrictions of this set-up, I don't think we should move
there for pacman development.

I will set up gitlab to pull from our current git so we get CI, but that
will be all for now.


More information about the pacman-dev mailing list