From: "Alex Bennée" <alex.bennee@linaro.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: Signing QEMU up for GitLab for Open Source?
Date: Mon, 25 Apr 2022 13:53:28 +0100 [thread overview]
Message-ID: <8735i17278.fsf@linaro.org> (raw)
In-Reply-To: <YmZ8WpmZfdX5CsA/@stefanha-x1.localdomain>
Stefan Hajnoczi <stefanha@redhat.com> writes:
> [[PGP Signed Part:Undecided]]
> Hi,
> QEMU needs to enroll in GitLab for Open Source before July 1st to
> receive 50,000 CI/CD pipeline minutes and GitLab Ultimate features:
>
> https://about.gitlab.com/blog/2022/02/04/ultimate-perks-for-open-source-projects/
> https://about.gitlab.com/solutions/open-source/
>
> CI/CD minutes also become available to personal forks for open source
> repos so contributors can run CI pipelines without hitting CI limits as
> easily.
>
> Alex, Paolo, Peter, and I are qemu-project owners on GitLab. Has anyone
> already submitted an application?
No but if we are happy with the terms we should go ahead. I don't recall
SFLC having any major objections and GitLab seem to be pretty engaged in
ensuring open source projects are well treated.
>
> Stefan
>
> [[End of PGP Signed Part]]
--
Alex Bennée
next prev parent reply other threads:[~2022-04-25 12:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 10:47 Signing QEMU up for GitLab for Open Source? Stefan Hajnoczi
2022-04-25 12:53 ` Alex Bennée [this message]
2022-04-25 14:22 ` Daniel P. Berrangé
2022-04-27 11:02 ` Alex Bennée
2022-04-28 9:26 ` Stefan Hajnoczi
2022-05-09 8:39 ` Philippe Mathieu-Daudé
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=8735i17278.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.