From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [edk2-devel] Adding Bhyve support into upstream EDK2 To: Laszlo Ersek ,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: Mon, 09 Mar 2020 18:50:50 -0700 References: <620e6fb0-45ab-c8ed-8881-a907dc4cc030@redhat.com> In-Reply-To: <620e6fb0-45ab-c8ed-8881-a907dc4cc030@redhat.com> Message-ID: <1758.1583805050303399990@groups.io> Content-Type: multipart/alternative; boundary="In1EIH0rxJduxJVIDTny" --In1EIH0rxJduxJVIDTny Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Sorry let me clarify a little more.=C2=A0 I don't doubt that you spending t= he time to validate a patch using OVMF catches issues and regressions.=C2= =A0 I am very appreciative of that effort, my point is you could do that w= ithout being in the edk2 tree and in fact we need to enable and request tha= t more do that for their given platforms (Platform CI needs to make this po= ssible).=C2=A0 I also didn't mean to imply that you only wanted your platfo= rm in the tree.=C2=A0 My ask is that we evaluate a strategy where all platf= orms and all things not "core" get removed from edk2 proper.=C2=A0 =C2=A0Th= is means silicon specific modules move into silicon specific repos and pack= ages full of limited use modules get moved out too. At that point we can fo= cus edk2 on delivering a small, high quality core and focus the community o= n workflows that leverage multiple repos.=C2=A0 There are numerous ways to = keep multiple repos in sync that allow a user to root cause regressions.=C2= = =A0 Using submodules is one way to easily track the version of edk2 that w= as/is used in the platform repo and when issues are identified the commit h= istory can be bisected to find the problem.=C2=A0 One other great benefit o= f multiple repos is that the repo maintainers can define their own workflow= s and requirements. I am not as proficient as you at mailing list management.=C2=A0 Nor are th= e people I interact with given that we all often miss many things we would = like to comment on or change until post commit/integration.=C2=A0 I equate = much of this to the mailing list review process and the value to noise rati= o of the mailing list.=C2=A0 =C2=A0So although one package may not overwhel= m, it does continue to distract from the most critical of changes in the co= re. Thanks Sean --In1EIH0rxJduxJVIDTny Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Sorry let me clarify a little more.  I don't doubt that you spending t= he time to validate a patch using OVMF catches issues and regressions. = ; I am very appreciative of that effort, my point is you could do that with= out being in the edk2 tree and in fact we need to enable and request that m= ore do that for their given platforms (Platform CI needs to make this possi= ble).  I also didn't mean to imply that you only wanted your platform = in the tree.  My ask is that we evaluate a strategy where all platform= s and all things not "core" get removed from edk2 proper.   This = means silicon specific modules move into silicon specific repos and package= s full of limited use modules get moved out too. At that point we can focus= edk2 on delivering a small, high quality core and focus the community on w= orkflows that leverage multiple repos.  There are numerous ways to kee= p multiple repos in sync that allow a user to root cause regressions. = Using submodules is one way to easily track the version of edk2 that was/i= s used in the platform repo and when issues are identified the commit histo= ry can be bisected to find the problem.  One other great benefit of mu= ltiple repos is that the repo maintainers can define their own workflows an= d requirements.

I am not as proficient as you at mailing list ma= nagement.  Nor are the people I interact with given that we all often = miss many things we would like to comment on or change until post commit/in= tegration.  I equate much of this to the mailing list review process a= nd the value to noise ratio of the mailing list.   So although on= e package may not overwhelm, it does continue to distract from the most cri= tical of changes in the core. 

Thanks
Sean --In1EIH0rxJduxJVIDTny--