Moving project infrastructure / services to GitLab

[Peter Krempa]

On Mon, Mar 02, 2020 at 11:01:55 +0000, Daniel Berrange wrote:
> We've discussed the idea of moving to a GitForge before, with the debate
> circling around the pros/cons of mailing list vs merge request workflows.
> 
> This mail is NOT focused on that particular debate, rather it is tackling the
> much broader issue of libvirt project infrastructure consolidation, such that
> we can eliminate time spent as OS sysadmins, while having long term sustainable
> infra which facilitates collaboration for project participants & integration
> between services.
> 
> Having said that, a move to a merge request workflow IS facilitated by this
> and IS one of the items proposed. A full consideration of this item would make
> this mail way to large. Thus I won't discuss it in any significant detail here,
> merely mention it as a bullet point. I'll send a separate mail for this topic
> later, as it isn't a pre-requisite for any of the other changes described in
> this mail.

In my opinion the very important part is that the libvirt.org
documentation links keep working regardless of how it's achieved.

Other things outlined here make sense mostly. I'd be partially wary of
replacing a single point of failure with another one and adding a lot of
moving parts (e.g. for the documentation/web sync). The benefits of not
having to maintain most of the infra is worth it though.

I'm just afraid that this will be a slippery slope towards web-review
workflow which I'm VERY firmly against.