-----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