Strange panel name "NGContainers"

[Akihiro Motoki]

We have a panel named "NGContainers", but "NG" means AngularJS based implementation.
It is completely meaningless for dashboard users.
It should have more meaningful name.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/288948

[Richard Jones (r1chardj0n3s)]

The naming scheme is tricky, yes, but it is also a pattern we've used for other AngularJS panels. "NG" for Angular but also "Next Generation" in my mind. Do you have a suggestion for a better name?

We intend to replace the Containers panel with NGContainers when it is merged. This may happen for Mitaka, depending on review speed.

[Akihiro Motoki (amotoki)]

I know we are developing the Containers panel with AngularJS and now we have two Containers panel.
I think the name "NGContainers" is chosen so that developers can distinguish two panels easily.

My comment is from the point of view of regular users.
For regular users, "NGContainers" is completely meaningless. They cannot understand what "NGContainers" means.

If the new panel lands by Mitaka-RC1, can we ensure to replace "NGContainers" with "Containers"?
If it does not land, is "NGContainers" never visible to users?

We have started translations for Mitaka, so at least we should add a comment for translators so that they can know how "NGContainers" should be treated (perhaps no need to translate it because it is under development and never visible to users).

Thought?

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/289106

[Akihiro Motoki (amotoki)]

I am a bit surprised that you proposed a patch replacing the old containers panel with the new angular one.
What I would like to take care of this bug is the only one string visible to users ("NGContainers").
URL or other stuff does not need to be renamed.

Is the Angular version of the panel ready? I am okay with either direction.

[Richard Jones (r1chardj0n3s)]

Oh! Sorry, I was creating that patch while you were explaining and I didn't notice your follow-up! I'll address the simple problem you have, but I'm going to leave the more "complete" patch up for later discussion and merging :-)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/289124

[Richard Jones (r1chardj0n3s)]

Argh. Sorry.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Richard Jones (<email address hidden>) on branch: master
Review: https://review.openstack.org/289124

[Akihiro Motoki (amotoki)]

No problem. Thanks for you support anyway!

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/288948
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=b09f0e8c63feaabab96a0f96bc5b8f2782fc9d87
Submitter: Jenkins
Branch: master

commit b09f0e8c63feaabab96a0f96bc5b8f2782fc9d87
Author: Akihiro Motoki <email address hidden>
Date: Sun Mar 6 08:30:10 2016 +0900

    Rename a panel name "NGContainers" with "Containers"

    "NGContainers" is meaningless from dashboard users
    since "NG" means AngularJS based implementation.
    Users do not care what implementation is used and
    this kind of naming should be avoided.

    Change-Id: I240316403a1f448ffcdad7da6f3197531550613b
    Closes-Bug: #1553612

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/horizon 9.0.0.0rc1 release candidate.