Re: [edk2-rfc] [RFC] Request for new git repository for EdkRepo

["Michael D Kinney" <michael.d.kinney@intel.com>]

Hi Nate,

I have created the following Tianocore repositories:

* edk2-edkrepo
* edk2-edkrepo-manifest

I have added you and Ashley to the EDK II Tools Maintainers team with write access to both of these new repositories.

The EDK II Maintainers team has also been grated write access to the edk2-edkrepo-manifest repo.

Best regards,

Mike


> -----Original Message-----
> From: rfc@edk2.groups.io <rfc@edk2.groups.io> On Behalf Of Nate DeSimone
> Sent: Friday, November 13, 2020 3:18 PM
> To: Bjorge, Erik C <erik.c.bjorge@intel.com>; devel@edk2.groups.io; rfc@edk2.groups.io
> Cc: Desimone, Ashley E <ashley.e.desimone@intel.com>
> Subject: Re: [edk2-rfc] [RFC] Request for new git repository for EdkRepo
> 
> Hi Everyone,
> 
> This RFC has been sitting for a while and it seems like we have reached a conclusion. I would like to make a request to
> the TianoCore stewards to create 2 new git repositories in the project:
> 
> 1. edkrepo
> 2. edkrepo-manifest
> 
> Based on the current Maintainers.txt content, the following individuals should initially be given write access to these
> repositories:
> 
> Nate DeSimone <nathaniel.l.desimone@intel.com>
> Ashley DeSimone <ashley.e.desimone@intel.com>
> 
> I have taken a poll between myself and the other maintainer, and given that the project is currently in transition to
> using GitHub pull requests we both prefer to start out using the pull request method of code review for these new
> repositories. If there is any setup needed to enable pull request code review please do so.
> 
> Let me know if the stewards need any more information to complete this request.
> 
> Thanks!
> Nate
> 
> -----Original Message-----
> From: Desimone, Nathaniel L
> Sent: Wednesday, September 30, 2020 4:21 PM
> To: Bjorge, Erik C <erik.c.bjorge@intel.com>; devel@edk2.groups.io; rfc@edk2.groups.io
> Cc: Desimone, Ashley E <ashley.e.desimone@intel.com>
> Subject: RE: [RFC] Request for new git repository for EdkRepo
> 
> Hi Erik,
> 
> A separate manifest repository would probably be a good idea. The manifest repo is used for a lot of EdkRepo's operations
> so having a smaller repo dedicated repo could be beneficial from a performance standpoint.
> 
> Thanks,
> Nate
> 
> -----Original Message-----
> From: Bjorge, Erik C <erik.c.bjorge@intel.com>
> Sent: Wednesday, September 30, 2020 3:29 PM
> To: Desimone, Nathaniel L <nathaniel.l.desimone@intel.com>; devel@edk2.groups.io; rfc@edk2.groups.io
> Cc: Desimone, Ashley E <ashley.e.desimone@intel.com>
> Subject: RE: [RFC] Request for new git repository for EdkRepo
> 
> I am fine with a new repo.  This also supports a good workflow to get a tool that then lets you pull full platforms.  In
> theory you would only ever really need to clone a single repo manually (assuming reasonable manifest support).
> 
> Are you also looking at creating a separate manifest repo as well or just creating a manifest branch in the new EdkRepo
> repository?
> 
> Thanks,
> -Erik
> 
> -----Original Message-----
> From: Desimone, Nathaniel L <nathaniel.l.desimone@intel.com>
> Sent: Wednesday, September 30, 2020 2:56 PM
> To: devel@edk2.groups.io; rfc@edk2.groups.io
> Cc: Desimone, Ashley E <ashley.e.desimone@intel.com>; Bjorge, Erik C <erik.c.bjorge@intel.com>
> Subject: [RFC] Request for new git repository for EdkRepo
> 
> Hi Everyone,
> 
> Given that EdkRepo has existed in the project for over a year now (in edk2-staging) I think it is time to get out of
> staging. I have considered multiple possible landing zones:
> 
> 1. edk2
> 2. edk2-pytool-library
> 3. A new repository
> 
> Edk2 does not seem like a good location as EdkRepo isn't strictly necessary to build EDK II, and I think all of us would
> prefer that edk2 not become a dumping ground. I have talked with the other maintainers of edk2-pytool-library and they
> would prefer that EdkRepo not enter that repository because EdkRepo does not have a robust set of unit tests yet and they
> don't want their test coverage metrics to decline. Therefore, the best choice seems to be a new repository. As always if
> anyone has comments they are welcome!
> 
> Thanks,
> Nate
> 
> 
> 
>