| 2011-11-11 07:47:13 |
Michael Nelson |
description |
Last night David requested to see the reporting dashboard for myapps, so I checked the code and configs and couldn't see a Launchpad group openid mapping for the stakeholders Django group.
So currently people have to be added in the django admin interface to give them access (or given the correct permission in the admin interface), where as we should instead have a Launchpad group from which people can be updated (consistent with the other privileges).
For ref, here is the irc conversation: https://pastebin.canonical.com/55571/
Note: there is also one other place where we should make this update - the add_exhibit permission (originally we didn't use a group for this permission as it was only going to be 1 person - mpt - but it was later mentioned that we should make all privs correspond to LP groups for consistency). |
Last night David requested to see the reporting dashboard for myapps, so I checked the code and configs and couldn't see a Launchpad group openid mapping for the stakeholders Django group.
So currently people have to be added in the django admin interface to give them access (or given the correct permission in the admin interface), where as we should instead have a Launchpad group from which people can be updated (consistent with the other privileges).
For ref, here is the irc conversation: https://pastebin.canonical.com/55571/
Note: The arb-reviewers django group is also not linked to a launchpad group. |
|
