qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Connor Kuehl <ckuehl@redhat.com>
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
	Brijesh Singh <brijesh.singh@amd.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
	qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] Add Connor Kuehl as reviewer for AMD SEV
Date: Tue, 8 Jun 2021 21:45:09 +0100	[thread overview]
Message-ID: <YL/W1QqMPjZLvq+F@redhat.com> (raw)
In-Reply-To: <d01cae3a-eee4-1488-6f74-6b0beef38c6c@redhat.com>

On Tue, Jun 08, 2021 at 03:32:54PM -0500, Connor Kuehl wrote:
> On 6/8/21 3:10 PM, Daniel P. Berrangé wrote:
> > On Tue, Jun 08, 2021 at 02:25:37PM -0500, Connor Kuehl wrote:
> >> It may not be appropriate for me to take over as a maintainer at this time,
> >> but I would consider myself familiar with AMD SEV and what this code is
> >> meant to be doing as part of a VMM for launching SEV-protected guests.
> >>
> >> To that end, I would be happy to volunteer as a reviewer for SEV-related
> >> changes so that I am CC'd on them and can help share the review burden with
> >> whoever does maintain this code.
> >>
> >> Signed-off-by: Connor Kuehl <ckuehl@redhat.com>
> >> ---
> >> Note: because there's no maintainer entry, when running
> >> ./scripts/get_maintainers.pl on target/i386/sev.c, my name and the qemu
> >> mailing list is the only thing that shows up... it doesn't even show
> >> previous committers (as it would before applying this patch). Which is
> >> probably not great considering I do not make pull requests to QEMU.
> >>
> >> Is the way forward to get someone to sign up as a maintainer before
> >> applying a patch like this?
> > 
> > There's no requirement to have a maintainer before having a reviewer.
> > If any of the existing committers shown do send pull requests, it is
> > probably co-incidental since they're not listed as official maintainers,
> > and being listed as Reviewer doesn't commit you to doing pull requests.
> > 
> > That said if you're the only nominated reviewer and actually do useful
> > reviews, you will probably quickly find yourself the defacto maintainer
> > in 12 months time and end up doing pull requests... 
> 
> Right, I am just worried that if I am the only person that shows up in
> the get_maintainer.pl output, the submitter will have to know some other
> way who a relevant maintainer is that can take the patches otherwise
> they won't be CC'd. Or we'll have to hope a relevant maintainer sees
> them on the list. Or I'll have to chase down a maintainer myself
> assuming the reviews all check out. :-)

Well there's no real guarantee that any of the previous committers will
take the patch even if they are listed by get_maintainer. This is typical
with anything lacking a maintainer assigned. We typically hope that
whoever runs the "misc" queue sees the patch and picks it up, but often
it requires pings to remind someone to pick it up.

The only real right answer here is to actually get someone as the
nominated maintainer. Every other scenario is a just a band aid and
is not a good experiance for contributors. A nominated reviewer is
usually hoped to be a stepping stone to someone becoming maintainer
in future, so in that sense the fact that only you will be cc'd is
sort of intentional :-)

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 :|



  reply	other threads:[~2021-06-08 20:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 19:25 [PATCH] Add Connor Kuehl as reviewer for AMD SEV Connor Kuehl
2021-06-08 19:28 ` Connor Kuehl
2021-06-08 19:34 ` Dr. David Alan Gilbert
2021-06-08 20:46   ` Connor Kuehl
2021-06-08 20:10 ` Daniel P. Berrangé
2021-06-08 20:32   ` Connor Kuehl
2021-06-08 20:45     ` Daniel P. Berrangé [this message]
2021-06-08 20:50       ` Connor Kuehl

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=YL/W1QqMPjZLvq+F@redhat.com \
    --to=berrange@redhat.com \
    --cc=brijesh.singh@amd.com \
    --cc=ckuehl@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thomas.lendacky@amd.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).