-
Notifications
You must be signed in to change notification settings - Fork 236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename knative-community to something else #69
Comments
LGTM |
-sandbox is currently winning: https://app.slack.com/client/T93ELUK42/CU9DGL4FM/thread/C93E33SN8-1582850486.042800 |
|
We voted in the Steering committee today, and decided on 'knative-sandbox'. We've renamed the org on GitHub as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Follow-up of #23
Because of knative/community, searching for knative-community comes up with only hits for the former and not the latter. I think a unique naming would be better and since it is so-far unused, now is the time if people agree.
Kubernetes has:
Given we don't have SIGs, closest is working groups, I think one of the following would be a better naming and all have no or sufficiently-low hits on search:
(Rejected -extension, -unofficial, & -contrib because of other search hits)
People who mentioned the name in the last issue:
@rgregg
@maximilien
@evankanderson
@mchmarny
The text was updated successfully, but these errors were encountered: