From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wm1-f65.google.com (mail-wm1-f65.google.com [209.85.128.65]) by mx.groups.io with SMTP id smtpd.web11.15232.1589555022038507852 for ; Fri, 15 May 2020 08:03:42 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@nuviainc-com.20150623.gappssmtp.com header.s=20150623 header.b=zG5UebYA; spf=pass (domain: nuviainc.com, ip: 209.85.128.65, mailfrom: leif@nuviainc.com) Received: by mail-wm1-f65.google.com with SMTP id g12so3022914wmh.3 for ; Fri, 15 May 2020 08:03:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuviainc-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=/047Iq4F+zurHBGbEYxFG3aCJDu6y8H+Y8BAsoR81Dw=; b=zG5UebYAj5OMMU/T5SZMNAmo994UzURx9fKtOJCk3kH3+zTn3tpQ54OvtkldQp55N9 wgzYOMyJfKRPq5twt2tntvGw3RzR2VvggLcWhiKBVzDuTcTM2kqDbGKgiJ1/xQW8nP8O RiU7bJ8k0lMDSd6xBJ4il1D+2VXRDnhADfeviwRZeuf60ceb/20+Xu/dvNh5Xi+QqfqL I4YeIOUEgHUMyfhf1AgCTYARtH013SsobvD6qIH4ZcSFTdmyQzvz7jp2c264+TTIrU17 c8cqxYLVN66/1Iik7FIFI18XHX6pKVoFwlL1peFMGRyXxxzWQswtFvTbrCautYGf9uC4 XO2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=/047Iq4F+zurHBGbEYxFG3aCJDu6y8H+Y8BAsoR81Dw=; b=a99jwe0Hq9O2A76cWFqFRb+UZ+VhV9xacN9zUnwLRawaxMj2g6QvsB/bbE4UcSntFt m0hwP4TjqriIukfd9byy40k2IsZT1IYkANvuaLajFgrswQNFcpDMPDDbE+A84SDNVGOM H2s8LMBW/kHqNr2uG86NU5xc3KUKRMzX5Fi1Og6yCWoQ6eizjDs5p7Jl9Hu17lrlcYfd vyygE6agGpExbF5PSp36FxBQZ84ddS86Q7iGyWH6QyAXn6p1ctpAc/h0aScP87xL8wCh mPDAslooJSsP+1MMkH/wkyeD7Of2Hp6h9LO1mkl6iAHu3eiSUdGlaAgdlUseSUMGx8Rg wI4A== X-Gm-Message-State: AOAM532qjVLK8ItprP1DCVKGwKKoB4+Jf7qrPh6PzczuQcDlkcHJEqYK 21achbKerOWVO474N+TOh6g3tw== X-Google-Smtp-Source: ABdhPJw05u4rSzjoPEZczYyY6pb99M/Q+rkCfQddcOe50Kef3Gl45TP7u8x4utU6LwcO/qUHK1dKeg== X-Received: by 2002:a1c:a947:: with SMTP id s68mr4526190wme.25.1589555020625; Fri, 15 May 2020 08:03:40 -0700 (PDT) Return-Path: Received: from vanye ([2001:470:1f09:12f0:b26e:bfff:fea9:f1b8]) by smtp.gmail.com with ESMTPSA id z18sm3804071wmk.46.2020.05.15.08.03.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 15 May 2020 08:03:39 -0700 (PDT) Date: Fri, 15 May 2020 16:03:37 +0100 From: "Leif Lindholm" To: Laszlo Ersek Cc: Ard Biesheuvel , Rebecca Cran , devel@edk2.groups.io, michael.d.kinney@intel.com, Andrew Fish , "Justen, Jordan L" , Peter Grehan Subject: Re: [edk2-devel] Where to put the bhyve code in the edk2 repo: BhyvePkg, or under OvmfPkg? Message-ID: <20200515150337.GX21486@vanye> References: <58b768dc-cad7-08e5-2fe6-ba3e81002097@redhat.com> <32735AC0-2354-4ADB-A4D5-A3D93DA00385@bsdio.com> <56efcbf5-2fe8-4620-a98c-7b2bb60f0ceb@redhat.com> <4abae9ee-adfb-84e6-67d2-ce31898e0bc1@arm.com> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, May 15, 2020 at 14:51:28 +0200, Laszlo Ersek wrote: > On 05/15/20 11:47, Ard Biesheuvel wrote: > > On 5/15/20 11:42 AM, Laszlo Ersek wrote: > >> On 05/14/20 18:20, Rebecca Cran wrote: > >>> > >>>> On May 14, 2020, at 4:24 AM, Laszlo Ersek wrote: > >>>> > >>>> - The community not having any human resources permanently dedicated to > >>>> bhyve regressions (testing, review, and post factum fixing) is fine, as > >>>> long as the bhyve stakeholders can live with a matching frequency of > >>>> regressions. > >>> > >>> Yes, I believe that would be acceptable. > >>> Has there been a decision on the directory structure yet, or is that > >>> likely to be something that will need resolved at the next Stewards > >>> Meeting? > >> > >> Based on the discussion thus far, I'd suggest > >> "OvmfPkg/SecondClass/Bhyve". If you have the time, just go ahead and > >> submit the series like that, and wait for review. > >> > >> If you'd first like to be sure that everyone's OK with this pathname, > >> then please wait for more feedback in this thread. > >> > > > > Please no. SecondClass/ implies some kind of hall of shame, which is not > > a fair characterization. > > OK. I didn't mean to put bhyve in a "pillory" (I agree it would be > unfair), I just couldn't find better words for reflecting the separation > you asked for. > > > I think it would be better to simply host this code under OvmfPkg/Bhyve, > > OK! > > > and put some annotation in Maintainers.txt to document that regressions > > that only affect Bhyve are not treated with the same level of urgency as > > ones that affect OVMF for QEMU. > > How about "S: Odd Fixes"? From: > > S: Status, one of the following: > Supported: Someone is actually paid to look after this. > Maintained: Someone actually looks after it. > Odd Fixes: It has a maintainer but they don't have time to do > much other than throw the odd patch in. See below. > Orphan: No current maintainer [but maybe you could take the > role as you write your new code]. > Obsolete: Old code. Something tagged obsolete generally means > it has been replaced by a better system and you > should be using that. That looks like exactly what it's for. It *will* (since f355b986068a) mean GetMaintainer.py will print a warning. If that's an issue, we could discuss changing the level at which a warning is generated. / Leif