[openstack-dev] [murano] [dashboard] public package visibility in Package Definitions UX concern

Nikolay Starodubtsev nstarodubtsev at mirantis.com
Fri Aug 28 08:43:21 UTC 2015


My vote is for #1. If I remember the problem right it's the best solution.



Nikolay Starodubtsev

Software Engineer

Mirantis Inc.


Skype: dark_harlequine1

2015-08-20 13:16 GMT+03:00 Kirill Zaitsev <kzaitsev at mirantis.com>:

> On our latest irc meeting I raised a concern about public package
> visibility. Here’s the commit that caused my concerns
> https://review.openstack.org/#/c/213682/
>
> We currently have «catalog» and «package definitions» pages in our
> dashboard. The former contains packages that the user can add in his
> environment, and the latter contains packages the user can edit. This
> means, that admin user sees all the packages on package definitions page,
> while simple user can only see packages from his tenant.
> Lately we’ve added a filter, similar to the one «Images» dashboard has,
> that separates packages into «project» «public» and «other» groups, to ease
> selection, but this unfortunately introduced some negative UX, cause
> non-admin users now see the filter and expect all the public packages to be
> there.
>
> This can be solved in a couple of ways.
> 1) Remove the filter for non-admin user, thus removing any concerns about
> public-packages. User can still sort the table by pressing on the public
> header.
> 2) Renaming the filter to something like «my public» for non-admin
> 3) Allowing user to see public packages from other tenants, but making all
> the edit options grey, although I’m not sure if it’s possible to do so for
> bulk operation checkboxes.
> 4) Leave everything as is (ostrich algorithm), as we believe, that this is
> expected behaviour
>
> Personally I like #1 as it makes more sense to me and feels more
> consistent than other options.
>
> Ideas/opinions would be appreciated.
>
> --
> Kirill Zaitsev
> Murano team
> Software Engineer
> Mirantis, Inc
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150828/25ad8070/attachment.html>


More information about the OpenStack-dev mailing list