All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: "Claudio Fontana" <cfontana@suse.de>,
	"Juan Quintela" <quintela@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Fabiano Rosas" <farosas@suse.de>,
	"Steve Sistare" <steven.sistare@oracle.com>,
	qemu-devel@nongnu.org,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: migration maintenance, governance [Was: Re: [PATCH V4 0/2] migration file URI]
Date: Wed, 27 Sep 2023 15:36:16 +0100	[thread overview]
Message-ID: <ZRQ94J9vv83nLI4V@redhat.com> (raw)
In-Reply-To: <ZRQ0nOssnc0rdw6m@x1n>

On Wed, Sep 27, 2023 at 09:56:44AM -0400, Peter Xu wrote:
> Juan will be back next Monday.  Before he left, he told me that he's
> preparing the pull.
> 
> If next week there's still no pull from migration side then I suppose
> someone should start to pick up patches and send PR. I would volunteer
> myself already; I should have already perpared a pull a long time ago if I
> got ack from Juan.  If Fabiano would like to that'll also be nice.  I don't
> know how that works without delegation from the current (solo) maintainer,
> though, for either of us to become a maintainer.

Even if not actively sending a PR, a possible starting point that could
be done today, would be for someone to put up a gitlab.com branch that
contains all the outstanding patch series that are considered ready
to merge and validate a CI pipeline. That would both serve as a base for
further work, and might be useful to Juan in assembling the next pull
request.

> Before that, Fabiano can already propose a patch as at least a Reviewer
> without the need of any delegation from anyone, as he already did lots of
> work in that regard, assume he'll keep doing so to support the migration
> subsystem.

Yes, anyone is free to self-propose themselves as reviewers.

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



  reply	other threads:[~2023-09-27 14:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 14:25 [PATCH V4 0/2] migration file URI Steve Sistare
2023-06-30 14:25 ` [PATCH V4 1/2] migration: " Steve Sistare
2023-08-30 13:16   ` Daniel P. Berrangé
2023-08-30 14:15     ` Steven Sistare
2023-09-08 10:52       ` Daniel P. Berrangé
2023-09-08 14:23         ` Steven Sistare
2023-06-30 14:25 ` [PATCH V4 2/2] migration: file URI offset Steve Sistare
2023-07-13 21:26 ` [PATCH V4 0/2] migration file URI Michael Galaxy
2023-08-22 12:00 ` Claudio Fontana
2023-08-22 13:25   ` Philippe Mathieu-Daudé
2023-08-30 13:09     ` Claudio Fontana
2023-09-13 13:00       ` Claudio Fontana
2023-09-27 13:14         ` migration maintenance, governance [Was: Re: [PATCH V4 0/2] migration file URI] Claudio Fontana
2023-09-27 13:56           ` Peter Xu
2023-09-27 14:36             ` Daniel P. Berrangé [this message]
2023-09-27 15:15               ` Peter Xu
2023-09-27 14:31           ` 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=ZRQ94J9vv83nLI4V@redhat.com \
    --to=berrange@redhat.com \
    --cc=cfontana@suse.de \
    --cc=farosas@suse.de \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=steven.sistare@oracle.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.