Re: MAINTAINERS: macOS host support (was: MAINTAINERS: take edk2)

From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: "Cameron Esfahani" <dirty@apple.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Beraldo Leal" <bleal@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel@nongnu.org,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Philippe Mathieu-Daudé" <philippe.mathieu.daude@gmail.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Akihiko Odaki" <akihiko.odaki@gmail.com>,
	"Ani Sinha" <ani@anisinha.ca>,
	"Igor Mammedov" <imammedo@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Joelle van Dyne" <j@getutm.app>
Subject: Re: MAINTAINERS: macOS host support (was: MAINTAINERS: take edk2)
Date: Wed, 9 Mar 2022 11:44:16 +0000	[thread overview]
Message-ID: <YiiTEAAqRIdRAlEf@redhat.com> (raw)
In-Reply-To: <2263450.oHEczLTUl7@silver>

On Wed, Mar 09, 2022 at 11:40:42AM +0100, Christian Schoenebeck wrote:
> On Mittwoch, 9. März 2022 11:05:02 CET Philippe Mathieu-Daudé wrote:
> > Not sure what you have in mind. I'm totally new to the macOS/Darwin
> > world, and have no choice but to use it as primary workstation and
> > for CI builds, so I can help with overall testing / maintenance.
> > 
> > Peter, since you take some macOS patches, would you like to maintain
> > this officially? Since I doubt you want to take yet another
> > responsibility, what about having a co-maintained section, including
> > technical expertise from Akihiko / Joelle / Christian? (Cc'ed)
> > 
> > Regards,
> 
> Also CCing Cameron on this, just in case someone at Apple could spend some 
> slices on QEMU macOS patches in general as well.
> 
> As for my part: I try to help out more on the macOS front. As there's now 
> macOS host support for 9p I have to start QEMU testing on macOS locally 
> anyway. Too bad that macOS CI tests on Github are no longer available BTW.

Note QEMU gets macOS CI coverage in GitLab. We use a clever trick by
which we use 'cirrus-run' from the GitLab job to trigger a build in
Cirrus CI's macOS builders, and pull the results back when its done.

Any contributor can get this working on their QEMU fork too, if they
configure the needed Cirrus CI API token. See the docs in

   .gitlab-ci.d/cirrus/README.rst

This is enough for build + automated tests.

Obviously of limited use for testing UI functionality or general host
OS integration like audio, which pretty much requires access to a real
machine for a maintainer to use interactively.

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