From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [207.211.31.120])
 by mx.groups.io with SMTP id smtpd.web10.10083.1589535789800098574
 for <devel@edk2.groups.io>;
 Fri, 15 May 2020 02:43:10 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=arCACBr1;
 spf=pass (domain: redhat.com, ip: 207.211.31.120, mailfrom: lersek@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1589535788;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=w2qmnhrvOMhFV0RKRyNVEYQ4T8FwUYQuxYwBWaNOcZs=;
	b=arCACBr1YP9ej1Lzrd/AmYg6J6cpofApZoku630RRMKyVe5n0iByzU7S5AiTE9ro7YNlA7
	vTI090UDZd4CO7aGziEPCqJ0cHDhmmwnJmN+/9DhzYGn15WHwdNoTxcvJgyu9kpyai5o5K
	1pqV7D4xh7aImFu3gZZMwm/zb1XQQho=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id
 us-mta-161-rlCgD3jJOEW2MlB_uzuVXQ-1; Fri, 15 May 2020 05:43:05 -0400
X-MC-Unique: rlCgD3jJOEW2MlB_uzuVXQ-1
Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A1F698C9AD2;
	Fri, 15 May 2020 09:42:15 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-113-220.ams2.redhat.com [10.36.113.220])
	by smtp.corp.redhat.com (Postfix) with ESMTP id D45E7619F4;
	Fri, 15 May 2020 09:42:13 +0000 (UTC)
Subject: Re: [edk2-devel] Where to put the bhyve code in the edk2 repo: BhyvePkg, or under OvmfPkg?
To: Rebecca Cran <rebecca@bsdio.com>, devel@edk2.groups.io
Cc: michael.d.kinney@intel.com, Ard Biesheuvel <ard.biesheuvel@arm.com>,
 Andrew Fish <afish@apple.com>, Leif Lindholm <leif@nuviainc.com>,
 "Justen, Jordan L" <jordan.l.justen@intel.com>,
 Peter Grehan <grehan@freebsd.org>
References: <58b768dc-cad7-08e5-2fe6-ba3e81002097@redhat.com>
 <32735AC0-2354-4ADB-A4D5-A3D93DA00385@bsdio.com>
From: "Laszlo Ersek" <lersek@redhat.com>
Message-ID: <56efcbf5-2fe8-4620-a98c-7b2bb60f0ceb@redhat.com>
Date: Fri, 15 May 2020 11:42:12 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <32735AC0-2354-4ADB-A4D5-A3D93DA00385@bsdio.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Language: en-US
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 05/14/20 18:20, Rebecca Cran wrote:
> 
>> On May 14, 2020, at 4:24 AM, Laszlo Ersek <lersek@redhat.com> 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.

Thanks
Laszlo