From: Paolo Bonzini <pbonzini@redhat.com>
To: "Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: [RFC] Using gitlab for upstream qemu repo?
Date: Thu, 22 Oct 2020 18:47:55 +0200 [thread overview]
Message-ID: <672b8aa0-2128-23e1-b778-01a4d96b209d@redhat.com> (raw)
Hi all,
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.
There are four reasons for this:
- this would be a step towards ensuring that all commits go through the
CI process, and it would also provide a way to run the deployment of the
web site via .gitlab-ci.yml.
- right now Gitlab pulls from upstream repos and qemu.org pulls from
gitlab, but this is not true for the qemu, qemu-web and openbios
repositories where Gitlab pulls from qemu.org and qemu.org is the main
repository. With this switch, all the main repositories would be on
Gitlab and then mirrored to both qemu.org and GitHub. Having a
homogeneous configuration makes it easier to document what's going on.
- it would limit the number of people with access to qemu.org, since
committers would no longer need an account on the machine.
- by treating gitlab as authoritative, we could include it in the
.gitmodules file and remove load on the qemu.org server
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.
Of course this is just starting a discussion, so I'm not even proposing
a date for the switch.
Paolo
next reply other threads:[~2020-10-22 16:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 16:47 Paolo Bonzini [this message]
2020-10-22 17:24 ` [RFC] Using gitlab for upstream qemu repo? Eric Blake
2020-10-23 7:37 ` Gerd Hoffmann
2020-10-23 8:51 ` Daniel P. Berrangé
2020-10-23 13:41 ` Stefan Hajnoczi
2020-10-23 9:37 ` Paolo Bonzini
2020-10-23 8:44 ` Daniel P. Berrangé
2020-10-23 13:41 ` Stefan Hajnoczi
2020-10-26 11:04 ` Peter Maydell
2020-10-27 13:14 ` Michael Roth
2020-10-27 18:48 ` Paolo Bonzini
2020-10-27 14:08 ` Stefan Hajnoczi
2020-10-27 14:20 ` Daniel P. Berrangé
2020-10-27 14:32 ` Peter Maydell
2021-01-05 14:12 ` Peter Maydell
2021-01-11 9:57 ` Stefan Hajnoczi
2021-01-11 11:02 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=672b8aa0-2128-23e1-b778-01a4d96b209d@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=edgar.iglesias@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).