From: "Sean" <spbrogan@outlook.com>
To: devel@edk2.groups.io, rebecca@bsdio.com, lersek@redhat.com
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>
Subject: Re: [edk2-devel] Where to put the bhyve code in the edk2 repo: BhyvePkg, or under OvmfPkg?
Date: Thu, 14 May 2020 10:48:47 -0700 [thread overview]
Message-ID: <BN8PR07MB69628EC8992C6C230213EB5BC8BC0@BN8PR07MB6962.namprd07.prod.outlook.com> (raw)
In-Reply-To: <32735AC0-2354-4ADB-A4D5-A3D93DA00385@bsdio.com>
I really don't agree with this direction.
Adding another platform to a core repository that might or might not
work at any given time is a burden to all core contributors and doesn't
bring value to the core project.
The direction I would like to see is a new repo created at
github.com/tianocore/Bhyve_Platform.git
Then this platform can use a submodule for edk2. It can stay stable
because the submodule will point to edk2 at the last time the bhyve
maintainers "integrated" edk2. If the maintainer wants to be very
active they can do this daily or at each commit or if they have other
priorities they can do it at each stable tag.
If we as a community get our stuff together then we can build out CI
infrastructure for Bhyve that could provide PR feedback to indicates if
the PR proposed change will break the bhyve platform. This feedback can
then be used by reviewers to decide to approve or request more PR changes.
The above workflow then scales nicely to other platforms and gives
control to the platform maintainers. This also makes it clear the
different steps that are needed to integrate an edk2 revision into a
platform and provides great insight into derivative projects. Finally,
this workflow allows a platform to scale up and down it's investment and
relevancy to the edk2 project without directly changing edk2 source.
I hope offering a different viewpoint isn't viewed as me "continuing to
stand on the sidelines shouting "YOU'RE DOING IT WRONG"."
:)
Thanks
Sean
On 5/14/2020 9:20 AM, 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?
>
> —
> Rebecca Cran
>
>
>
>
next prev parent reply other threads:[~2020-05-14 17:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 15:44 Where to put the bhyve code in the edk2 repo: BhyvePkg, or under OvmfPkg? Rebecca Cran
2020-05-11 15:55 ` Laszlo Ersek
2020-05-11 16:20 ` Ard Biesheuvel
2020-05-11 16:36 ` Michael D Kinney
2020-05-11 16:38 ` Andrew Fish
2020-05-11 16:41 ` [edk2-devel] " Michael D Kinney
2020-05-11 21:12 ` Laszlo Ersek
2020-05-11 21:22 ` Michael D Kinney
2020-05-11 21:58 ` [edk2-devel] " Rebecca Cran
2020-05-12 9:28 ` Laszlo Ersek
2020-05-12 9:52 ` Ard Biesheuvel
2020-05-12 15:09 ` Laszlo Ersek
2020-05-14 2:34 ` Rebecca Cran
2020-05-14 10:24 ` Laszlo Ersek
2020-05-14 16:20 ` Rebecca Cran
2020-05-14 17:48 ` Sean [this message]
2020-05-14 18:22 ` Rebecca Cran
2020-05-14 18:46 ` Sean
2020-05-14 18:54 ` Rebecca Cran
2020-05-15 9:39 ` Laszlo Ersek
2020-05-15 9:42 ` Laszlo Ersek
2020-05-15 9:47 ` Ard Biesheuvel
2020-05-15 12:51 ` Laszlo Ersek
2020-05-15 15:03 ` Leif Lindholm
2020-05-11 16:25 ` Michael D Kinney
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-list 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=BN8PR07MB69628EC8992C6C230213EB5BC8BC0@BN8PR07MB6962.namprd07.prod.outlook.com \
--to=devel@edk2.groups.io \
/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