You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do we want the edx/configuration repo to be private copy, rather than a public fork?
Arguments for:
The repo contains 2U-specific configuration. Anything that is business-private, but not a secret, needs extra work to make it a secret.
This occurred one-time so far, when setting our edx-platform-private github URL: edx/configuration@a6eaeb9
Arguments against:
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: