Comment 7 for bug 1490484

Okay, lots to think about! Thanks for bringing this to the table.

1. Project name instead of service names - in all fairness, this convention pre-dates my involvement in the project. And admittedly, I too found this very confusing when I first started contributing. A move to change this would be a *very* heavy lifting exercise, but I do believe that this is worth a discussion. But I don't think it is up to the 4 of us to make that decision here. I am happy to start a discussion on the docs mailing list if this is all something we could see as a change? Thoughts?

2. I like your proposed solution. As Kato said though, some of the OSC command objects provider a few services for better user experience. But this does point out that we are potentially running ahead too fast to change to the 'openstack' command without realising the consequences, especially for new users.

So, my question to you - is how to you propose we begin these changes? This would be a long term solution, so it will not happen overnight and I can't imagine everyone will be thrilled.

My recommendation is we bring up these issues in the doc mailing list (for the project/service names) and the other issue we bring up in the dev mailing list (CC doc). This needs to be a bigger discussion.

Lana - how about we also have this discussion in the docs meeting? Kostiantyn would you be able to attend our meeting to discuss this with the group? Here is the information: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Documentation_team_meeting

We will discuss a potential need for a blueprint/spec after there has been a full discussion. I would like to keep this bug open as a reference point.