-
Notifications
You must be signed in to change notification settings - Fork 114
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
Pick a name? #30
Comments
I demo'd this to SIG-apps today and someone messaged me afterwards to point out that "Kubernetes" is copyrighted so we probably have to change the name at some point. Let's start thinking about this again. @Shopify/cloudplatform |
@KnVerey I like this name tho, is pretty descriptive we can probably talk to the k8s people and see what they need to let us keep it? |
What about |
This trademarks list includes "kubernetes" and not "k8s"... not sure how to check conclusively what is ok though. https://www.linuxfoundation.org/trademark-usage |
Or |
I vote |
@benlangfeld Thanks for the offer! We haven't picked a name yet, is there one you like? |
My favourite name of the ones that have come up over the years is "KAP". It's a reference to the capistrano deployment tool + the word "captain", in keeping with Kubernetes's nautical theme. We can say it stands for "K8s App Provisioner" or something like that. I also like that it offers a short base name for the executable: |
The problem with |
Taken: https://github.com/vmware/purser What about |
hrm as long as we also use |
That's pretty good! It'd have to be
I'm not super worried about this personally. |
I like |
@KnVerey What sort of approval is necessary for the name selection? |
We held a discussion and vote among the current maintainers, and |
Excellent. Once #424 and #421 get merged and #256 (comment) has an answer I'll prep a PR for that. |
@benlangfeld Have you started on this work? If you haven't we may add it to our next sprint, but we don't want to duplicate work. |
I haven’t yet, I apologise. I got pulled off to work on other things. I’m not sure when I might get time to come back to this. |
No need to apologize! We'll update here once we start working on it. |
We've picked a name and will tracking the work in #256 |
When I extracted the script from shipit-engine, I named the repo as the snippet was named in Shipit. However this isn't a great name for the project because all Shipit snippets are named in a very straightforward manner:
These are great names for a bash snippet in
bin/
, but not for a individual project.My point here is that we didn't call it "sysv-resource-limiter", we called it "Semian".
I think this project would benefit from an expressive name.
thoughts? @sirupsen @KnVerey
The text was updated successfully, but these errors were encountered: