qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: "qemu@sfconservancy.org" <qemu@sfconservancy.org>
Subject: Should we apply for GitLab's open source program?
Date: Fri, 04 Sep 2020 16:35:34 +0100	[thread overview]
Message-ID: <878sdp4ks9.fsf@linaro.org> (raw)


Hi,

Given our growing reliance on GitLab and the recent announcement about
free tier minutes:

  https://about.gitlab.com/pricing/faq-consumption-cicd/

is it time we officially apply for GitLab's Open Source Program:

  https://about.gitlab.com/solutions/open-source/program/

?

From what I can see the QEMU project will easily qualify - the only
minor inconvenience is needing to reapply every year. So far it seems as
a public project their are no usage limits anyway. We are currently
listed as 0 of 50,000 minutes:

  https://gitlab.com/groups/qemu-project/-/usage_quotas#pipelines-quota-tab

So we are in no pressing hurry to do this for the minutes but I suspect
there may be other things that are made easier by having access to all
the toys GitLab provides. Daniel has already posted to the forum
requesting details about how this might affect our workflow so maybe we
should just wait for feedback until pressing on?

  https://forum.gitlab.com/t/ci-cd-minutes-for-free-tier/40241/33

-- 
Alex Bennée


             reply	other threads:[~2020-09-04 15:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04 15:35 Alex Bennée [this message]
2020-09-04 16:08 ` Should we apply for GitLab's open source program? Daniel P. Berrangé
2020-09-21 14:03   ` Daniel P. Berrangé
2020-09-21 14:39     ` Paolo Bonzini
2020-09-08 14:17 ` Stefan Hajnoczi
2020-09-16 23:39   ` Bradley M. Kuhn
2020-09-17  7:21     ` Paolo Bonzini
2020-09-17  8:32       ` Alex Bennée
2020-09-17  9:19         ` Daniel P. Berrangé
2022-02-17 11:42 ` Daniel P. Berrangé

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=878sdp4ks9.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu@sfconservancy.org \
    /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).