As @Harsh4902 is leading the effort described in #97, I think that one important part (at least in terms of marketing 😉 ) is to find a new name!
The GitHub repository will remind microcks-cli because it is self-explanatory, but reusing it directly is a bit long and cumbersome.
As of today, I see 3 options:
mksctl as @JulienBreux starts initializing it
- Pros: like
kubectl and others in the same spirit
- Cons: who is actually typing
kubectl? Most of people I know are aliasing it to kc, kube or simply k 😉
mks as a mksctl short version
- Pros: short! 3 letters like
npm, mvn, ...
- Cons: maybe hard to figure that
mks is the microcks contraction... We could have chose mck or others...
microcks simply put
- Pros: shorter than
microcks-cli, easy to figure out (like the argocd CLI)
- Cons: not really Microcks as its a way of controlling it but if we add commands like
microcks start it really makes sense!
My current preference goes to simply microcks but I'd like to open the discussion here!
Let me know what you think!
As @Harsh4902 is leading the effort described in #97, I think that one important part (at least in terms of marketing 😉 ) is to find a new name!
The GitHub repository will remind
microcks-clibecause it is self-explanatory, but reusing it directly is a bit long and cumbersome.As of today, I see 3 options:
mksctlas @JulienBreux starts initializing itkubectland others in the same spiritkubectl? Most of people I know are aliasing it tokc,kubeor simplyk😉mksas amksctlshort versionnpm,mvn, ...mksis themicrockscontraction... We could have chosemckor others...microckssimply putmicrocks-cli, easy to figure out (like theargocdCLI)microcks startit really makes sense!My current preference goes to simply
microcksbut I'd like to open the discussion here!Let me know what you think!