From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [edk2-devel] Adding Bhyve support into upstream EDK2 To: Ard Biesheuvel ,devel@edk2.groups.io From: "Sean" X-Originating-Location: Redmond, Washington, US (50.35.74.15) X-Originating-Platform: Windows Chrome 82 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Sun, 08 Mar 2020 23:08:54 -0700 References: In-Reply-To: Message-ID: <20173.1583734134875404839@groups.io> Content-Type: multipart/alternative; boundary="Sikc51reTblfQgiPmo7e" --Sikc51reTblfQgiPmo7e Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Ard/Lazlo, I find your position on=C2=A0OvmfPkg, ArmVirtPkg,and edk2-platforms in edk= 2 to be detrimental to the overall success of the edk2 project.=C2=A0 The m= ajority of edk2 consumers already have to deal with their platform not bein= g part of the edk2 git repo and the fact that changes to edk2 may not work = or cause conflict on their platforms.=C2=A0 This is the reality of working = with edk2 and building a large diverse set of products.=C2=A0 In fact, beca= use OVMF's preferential treatment and presence in the edk2 tree, others in = the community are burdened by those changes (mailing list noise, git histor= y/commits, git repo size, etc).=C2=A0 =C2=A0From someone who has developed = and maintained platforms with edk2 for the last decade +, I can tell you th= at having OVMF in edk2 hasn't kept the tree free from regressions. I also d= on=E2=80=99t use it as a source for integration requirements because it is = vastly different than physical platforms and has very little resemblance to= my projects. I share your concerns about regressions, ease of development, etc. I want = to see tianocore develop workflows and processes that work for the full com= munity.=C2=A0 That means we must take into account the needs of those that = have platforms outside the edk2 repo.=C2=A0 We must build tools that make m= anaging all platforms dependencies tenable.=C2=A0 We must create CI that ca= n leverage a vast number of platforms as an indicator of breaking changes, = yet not be gated on their success. We must have a process that lets all int= erested platforms efficiently interact with and be part of.=C2=A0 The tiano= core community is in need of the larger UEFI ecosystem engagement and we mu= st remove the barriers to get them involved. As always I appreciate the discussion. Thanks Sean --Sikc51reTblfQgiPmo7e Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Ard/Lazlo,

I find your position on=C2=A0OvmfPkg, Arm= VirtPkg,and edk2-platforms in edk2 to be detrimental to the overall success= of the edk2 project.=C2=A0 The majority of edk2 consumers already have to = deal with their platform not being part of the edk2 git repo and the fact t= hat changes to edk2 may not work or cause conflict on their platforms.=C2= =A0 This is the reality of working with edk2 and building a large diverse = set of products.=C2=A0 In fact, because OVMF's preferential treatment a= nd presence in the edk2 tree, others in the community are burdened by those= changes (mailing list noise, git history/commits, git repo size, etc).=C2= =A0 =C2=A0From someone who has developed and maintained platforms with edk= 2 for the last decade +, I can tell you that having OVMF in edk2 hasn't= kept the tree free from regressions.=C2=A0=C2=A0 I also don=E2=80=99t use it as a source for integration re= quirements because it is vastly different than physical platforms and has v= ery little resemblance to my projects.= =C2=A0

I share your concerns about regressions, ease of d= evelopment, etc. I want to see tianocore develop workflows and processes th= at work for the full community.=C2=A0 That means we must take into account = the needs of those that have platforms outside the edk2 repo.=C2=A0 We must= build tools that make managing all platforms dependencies tenable.=C2=A0 W= e must create CI that can leverage a vast number of platforms as an indicat= or of breaking changes, yet not be gated on their success.=C2=A0 We must have a process that lets all intere= sted platforms efficiently interact with and be part of.=C2=A0 The tianocor= e community is in need of the larger UEFI ecosystem engagement and we must = remove the barriers to get them involved.=C2=A0 =C2=A0

As always I= appreciate the discussion.=C2=A0

Thanks
Sean

--Sikc51reTblfQgiPmo7e--