Re: [RFC] Using gitlab for upstream qemu repo?

[Daniel P . Berrangé]

On Tue, Oct 27, 2020 at 02:08:18PM +0000, Stefan Hajnoczi wrote:
> On Mon, Oct 26, 2020 at 11:04:06AM +0000, Peter Maydell wrote:
> > On Thu, 22 Oct 2020 at 17:48, Paolo Bonzini <pbonzini@redhat.com> wrote:
> > > now that Gitlab is the primary CI infrastructure for QEMU, and that all
> > > QEMU git repositories (including mirrors) are available on Gitlab, I
> > > would like to propose that committers use Gitlab when merging commits to
> > > QEMU repositories.
> > 
> > > Nothing would change for developers, who would still have access to all
> > > three sets of repositories (git.qemu.org, gitlab.com and github.com).
> > > Committers however would need to have an account on the
> > > https://gitlab.com/qemu-project organization with access to the
> > > repositories they care about.  They would also lose write access to
> > > /srv/git on qemu.org.
> > 
> > Yes, this makes sense. Who in practice does it actually affect?
> > For the main qemu.git repo, my guess is just me, Michael Roth
> > for the stable branches, plus Richard H and Stefan H who both
> > volunteered to do a turn on the merge-handling rota once we
> > eventually get it set up to not depend on my ad-hoc CI setup.
> > 
> > I have a gitlab account so I'm set for this. Michael, do you
> > have an account there and are you OK with switching to doing
> > git pushes to the repo on gitlab rather than direct to qemu.org ?
> 
> Here are the users with commit access to qemu.org repos:
> 
> berkeley-softfloat-3 - pmaydell,mdroth,stefanha
> berkeley-testfloat-3 - pmaydell,mdroth,stefanha
> capstone - pmaydell,mdroth,stefanha
> dtc - pmaydell,mdroth,stefanha
> edk2 - pmaydell,mdroth,stefanha
> ipxe - kraxel,lprosek
> keycodemapdb - pmaydell,mdroth,stefanha

Mirroring this on gitlab is a little silly when the primary upstream
is already on gitlab :-)

   https://gitlab.com/keycodemap/keycodemapdb

> libslirp - pmaydell,mdroth,stefanha
> meson - pmaydell,mdroth,stefanha
> openbios - pmaydell,mdroth,stefanha
> openhackware - pmaydell,mdroth,stefanha
> opensbi - <none>
> qboot - pmaydell,mdroth,stefanha
> qemu - pmaydell,mdroth,stefanha
> qemu-jeos - pmaydell,mdroth,stefanha
> QemuMacDrivers - pmaydell,mdroth,stefanha
> qemu-palcode - pmaydell,mdroth,stefanha


> qemu-stable-0.10 - jforbes,afaerber,mdroth
> qemu-stable-0.14 - jforbes,afaerber,mdroth
> qemu-stable-0.15 - jforbes,afaerber,mdroth
> qemu-stable-1.0 - jforbes,afaerber,mdroth
> qemu-stable-1.1 - jforbes,afaerber,mdroth
> qemu-stable-1.2 - jforbes,afaerber,mdroth
> qemu-stable-1.3 - jforbes,afaerber,mdroth
> qemu-stable-1.4 - jforbes,afaerber,mdroth

IIUC, the content from these is present in the main qemu.git.

Should we mark them "archived" in gitlab, so they're not listed
by default as active repos.

> qemu-web - paolo,jcody,pmaydell,mdroth,thuth
> s390-tools - pmaydell,mdroth,stefanha
> seabios - pmaydell,mdroth,stefanha
> seabios-hppa - pmaydell,mdroth,stefanha
> sgabios - paolo
> skiboot - pmaydell,mdroth,stefanha
> SLOF - pmaydell,mdroth,stefanha
> u-boot - pmaydell,mdroth,stefanha
> u-boot-sam460ex - pmaydell,mdroth,stefanha
> vbootrom - pmaydell,mdroth,stefanha
> vgabios - pmaydell,mdroth,stefanha
> 
> Quite a few of those repos are mirrors and actually don't need human
> push access.
> 
> The people who need push access are:
>  * bonzini - qemu-web
>  * mdroth - qemu-stable
>  * pmaydell - qemu
>  * rth - qemu
>  * stefanha - qemu
>  * thuth - qemu-web
> 
> Does this sound good?

Doesn't  mdrooth need  'qemu-web' access for updating the list of
releases ?

We probably ought to have more than one person with push to qemu-stable,
even if mdroth normally does it all, just to improve a bus factor.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|