From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: QEMU Summit Minutes
Date: Thu, 27 Oct 2022 14:13:35 +0100 [thread overview]
Message-ID: <Y1qD//rEJ9vAFedm@redhat.com> (raw)
In-Reply-To: <CAFEAcA-7oY=988uLFEDgdSS8CjSSmyeZOYKsq9Vm-9vKXLms8A@mail.gmail.com>
On Thu, Oct 27, 2022 at 01:50:37PM +0100, Peter Maydell wrote:
> Infrastructure
> ==============
snip
> Alex Bennee has successfully signed the QEMU project up for the GitLab
> Open Source Program, which grants Ultimate tier features. This includes
> 50,000 CI minutes per month, 500 GB of transfer per month, and 250 GB of
> storage. I have not seen confirmation yet that personal forks of
> qemu.git share the CI minutes but Daniel Berrangé, Alex Bennée, and I
> believe this should be the case.
NB, in case anymore missed discussion since the summit, this
is *NOT* the case for forks.
Standard user accounts or group namespaces on gitlab.com get 400
CI minutes and cost factor of 1.0 by default. NB some users / groups
might be grandfathered into a 2000 CI minute quota, but its not
clear if that's going to remain so.
With joining the OSP, QEMU gets its quota increased to 50,000 CI
minutes, and the cost factor reduced to 0.5
Forks of QEMU still consume from the user's own CI quota, but
they benefit from a reduced cost factor of 0.008.
For further details see here:
https://lists.gnu.org/archive/html/qemu-devel/2022-10/msg00244.html
> Bug Tracking System
> ===================
>
> We discussed the state of our bug tracker now we've had time
> to see how the migration from Launchpad to Gitlab has gone.
>
> At point of conversion we had about ~450 bugs; we're up to
> ~650 open bugs now. Gitlab doesn't have the same kind of
> automated close-stale-bugs machinery that Launchpad did, so
> we probably have more stale bugs than we did. There was
> no consensus about whether we should be more active/automated
> about closing old bugs.
>
>
> It was noted that it's now harder to CC somebody on a bug
> because you can't just cc them on a reply on the mailing list.
> We agreed that we should have some way (probably in MAINTAINERS)
> for developers to note their gitlab user ID, so it's easier to
> find out the right ID to @ to get somebody's attention on a bug.
I would like to see at minimum, *all* people acting as subsystem
MAINTAINERS (ie 'Status == Supported/Maintained) having a gitlab.com
account, and be added to the /qemu-project membership list. It is
pretty unhelpful to have maintainers of subsystems be uncontactable
via / ignoring the project's official bug tracker, as that puts a
bigger burden on people doing bug triage and will lead to growing
backlog.
We've got 44 people as members in gitlab.com/qemu-project right
now.
We have 167 distinct maintainer email addrs in MAINTAINERS.
We have 192 subsystems listed as 'maintained' and 96 as 'supported',
81 'odd fixes' and '12' orphan.
This suggests there is a big gap in our gitlab.com membership wrt
supported /maintained subsystems.
With 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 :|
next prev parent reply other threads:[~2022-10-27 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 12:50 QEMU Summit Minutes Peter Maydell
2022-10-27 13:13 ` Daniel P. Berrangé [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-25 14:34 Peter Maydell
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=Y1qD//rEJ9vAFedm@redhat.com \
--to=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).