From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Eduardo Habkost" <ehabkost@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] qapi/misc.json is too big, let's bite off a few chunks
Date: Fri, 7 Jun 2019 10:59:30 +0100 [thread overview]
Message-ID: <20190607095930.GA28838@redhat.com> (raw)
In-Reply-To: <875zphg9t8.fsf@dusky.pond.sub.org>
On Fri, Jun 07, 2019 at 08:59:31AM +0200, Markus Armbruster wrote:
> Paolo Bonzini <pbonzini@redhat.com> writes:
>
> > On 27/05/19 10:00, Markus Armbruster wrote:
> >> As long as we don't have an active QOM maintainer[*], the benefit is
> >> low.
> >>
> >>
> >> [*] We need one. I'm not volunteering.
> >
> > I think Daniel, Eduardo and I could count as de facto maintainer. I
> > guess I could maintain it if I get two partners in crime as reviewers.
>
> Alright, we need two volunteers for the reviewer role, and one patch to
> MAINTAINERS.
>
> A mention in MAINTAINERS is the traditional punishment for good work, so
> let's see who's been doing the work. Aha:
>
> Eduardo Habkost
> Marc-André Lureau
> Markus Armbruster
> Eric Blake
> Philippe Mathieu-Daudé
>
> Details appended.
>
> QOM is not a particularly active subsystem now: 51 commits in two years.
>
> We obviously need maintainers to review and merge patches. The nominal
> maintainer hasn't been doing that since 2015. Git shows the following
> top committers taking on / getting sucked into QOM:
>
> Markus Armbruster <armbru@redhat.com>
> Eduardo Habkost <ehabkost@redhat.com>
> Paolo Bonzini <pbonzini@redhat.com>
> Marc-André Lureau <marcandre.lureau@redhat.com>
> Eric Blake <eblake@redhat.com>
>
> We really need nominal maintainer(s) again.
>
> Of course, *active* maintainers would be even better: I consider QOM
> stuck in an unhappy place where much of its potential is still
> potential.
>
> But let's start small. Volunteers for the reviewer role, please step
> forward :)
I'm happy to be a reviewer since I understand the code fairly well.
I don't want to volunteer to be maintainer as I can't promise to
be timely at dealing with yet another patch queue.
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 :|
prev parent reply other threads:[~2019-06-07 11:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 16:14 [Qemu-devel] qapi/misc.json is too big, let's bite off a few chunks Markus Armbruster
2019-05-24 18:31 ` Paolo Bonzini
2019-06-07 8:25 ` Markus Armbruster
2019-06-07 11:35 ` Paolo Bonzini
2019-06-07 12:45 ` Markus Armbruster
2019-06-11 21:20 ` Eduardo Habkost
2019-05-24 18:53 ` Eduardo Habkost
2019-05-27 8:00 ` Markus Armbruster
2019-05-27 10:03 ` Paolo Bonzini
2019-05-28 19:37 ` Eduardo Habkost
2019-06-07 6:59 ` Markus Armbruster
2019-06-07 8:33 ` Philippe Mathieu-Daudé
2019-06-07 12:25 ` Markus Armbruster
2019-06-07 9:59 ` Daniel P. Berrangé [this message]
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=20190607095930.GA28838@redhat.com \
--to=berrange@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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.