Comment 4 for bug 1603481

"It's better to have some names that we're not in love with at first, than to have a namespace that is impossible to use soon."

This I completely agree with. There are solutions to this problem like you mention, aliasing is what I am currently doing. My goal is to make documentation re-consumable, but rabbitmq.ctl and keystone.manage would not achieve that goal due to different binary names.

I hope this doesn't come across as complaining, but rather I just want to make sure it is known that this is an area I believe there could be some improvement in as I feel it is an important issue. The sooner a conversation is had, the easier any solution that comes up can be implemented.