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
We'd like to see if we can create and use a new github org k8s-internal for maintaining forks. We used to use k/k's third_party directory and k8s.io/utils/ so far, but we are reaching the limits of what we can do with those. We specifically want the k8s.io/internal to ensure that only kubernetes projects are able to use code from this github org and discourage anyone else from doing the same.
To start with if someone does a go get k8s.io/internal/distribution they should end up pulling code from https://github.com/k8s-internal/distribution We would like to run this experiment to see if it is feasible, if it works well with go tools and ide(s) we would then form a policy in sig-arch and provide guidance in code-organization to use this pattern from then on.
thanks!
The text was updated successfully, but these errors were encountered:
Context : please see kubernetes/utils#231 (comment)
We'd like to see if we can create and use a new github org
k8s-internal
for maintaining forks. We used to use k/k's third_party directory and k8s.io/utils/ so far, but we are reaching the limits of what we can do with those. We specifically want thek8s.io/internal
to ensure that only kubernetes projects are able to use code from this github org and discourage anyone else from doing the same.To start with if someone does a
go get k8s.io/internal/distribution
they should end up pulling code from https://github.com/k8s-internal/distribution We would like to run this experiment to see if it is feasible, if it works well with go tools and ide(s) we would then form a policy in sig-arch and provide guidance in code-organization to use this pattern from then on.thanks!
The text was updated successfully, but these errors were encountered: