This would require additional work to have jobs use tokens to reach the now-private repo, rather than having it be publicly accessible.
For some repos and some types of github actions, it might be more expensive to run from a private repo.
Not everyone agrees on whether we can legally switch from public to private based on licensing. Most agree that this particular repo would probably be ok.
Regarding this repo specifically, we are trying to move off of it more and more as we complete containerization work.
In general, it seems like public forks are the simplest way to go, and should be the solution unless there is compelling reason to do otherwise.
Do we want the edx/configuration repo to be private copy, rather than a public fork?
Arguments for:
Arguments against:
In general, it seems like public forks are the simplest way to go, and should be the solution unless there is compelling reason to do otherwise.