Comment 7 for bug 1394299

This is being fixed as part of the Community Images implementation. In order to introduce 'community' visibility, we finally had to tackle making image visibility semantics coherent.

This is documented in the spec [0] (see, in particular, 'other end user impact'). It is also discussed at great length in the patch that updated the spec [1] (the update concerned what the default value for visibility should be).

There has also been extensive discussion on the openstack-dev ML about the propriety of the change necessary to address this bug. It's been discussed with the API-WG (3 times [2,3,4], plus appearances in the API-WG newsletter), and with operators (we took a survey [5]), and the general community (see, e.g., [6]).

[0] http://specs.openstack.org/openstack/glance-specs/specs/newton/approved/glance/community_visibility.html
[1] https://review.openstack.org/#/c/396919/
[2] http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-06-09-15.59.log.html#l-84
[3] http://eavesdrop.openstack.org/meetings/api_wg/2017/api_wg.2017-01-05-16.00.log.html#l-19
[4] http://eavesdrop.openstack.org/meetings/api_wg/2017/api_wg.2017-01-12-16.00.log.html#l-103
[5] http://lists.openstack.org/pipermail/openstack-operators/2016-November/012107.html
[6] http://lists.openstack.org/pipermail/openstack-dev/2016-November/107349.html