Decide of a new name for `microcks-cli`

[lbroudoux]

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!

[alikhere]

I like 'microcks' with 'mks' as a short version—it combines clarity with brevity, making it both intuitive and efficient. Open to more thoughts!

[yada]

I vote for microcks: more effortless to be identified using brew search... man page and usage info will avoid any confusion, IMHO.

[divyansh-prks]

I vote for mks :)

[Harsh4902]

I think microcks is better and much self-explanatory.

[hguerrero]

microcks would be my choice, as @yada mentioned, easy to find in repos. No need to think about what was the short version. Everyone can use their own short for the alias.

[karanngi]

I also vote for microcks for the simplicity.

[lbroudoux]

Thanks for contributing on this poll! I think we can go with simply microcks and let people define aliases (like mks) if they want to. microcks is the more obvious and straightforward choice! 🚀