Description
We will need our own fork of OpenUSD to test branches (ie, for upcoming cmake branch), test CI, and likely other things as well.
Not sure if this should be private or public... ideal might be to have both?
Per Pixar's request, repo should be PRIVATE
As an implementation detail:
a public repo can/should be made via github's normal "forking" mechanism- github doesn't allow forking a private repo from a public one - so if we want a public one, it will just have to be set up as a new, empty repo with an appropriate name (OpenUSD-Private?), and we are given push access
Example use case:
- I wanted to share a preview merged branch of all the CMake PRs put forth by this body.
- However, since it's not yet ready for public consumption, it must be on a PRIVATE repo.
- Because there is no AOUSD managed OpenUSD private repo:
- anyone who even wanted to see / push / pull from another private repo would have to be MANUALLY added, one by one
- This would be a pain, and a significant impediment to communication / visibility
- ie, witness the struggles we had/have getting everyone access to THIS repo...
- If there WERE an OpenUSD repo controlled by the AOUSD:
- then we could make use of an organizational groups or permissions to automatically give rights to that repo
- ie, anyone who can see this repo would also be able to see that one
Description
We will need our own fork of OpenUSD to test branches (ie, for upcoming cmake branch), test CI, and likely other things as well.
Not sure if this should be private or public... ideal might be to have both?Per Pixar's request, repo should be PRIVATE
As an implementation detail:
a public repo can/should be made via github's normal "forking" mechanismExample use case: