Some Launchpad developers should have admin privileges on staging

Stuart, can you take care of this? It would save a lot of time to check some pages in staging instead of running a launchpad instance locally.

According to today's meeting we should allow some selected members (the QA guy) of the launchpad team to access staging as an admin.

<SteveA> okay. i'm fine with launchpad admins plus matsubara having admin
access on staging

I have recently been accepted into Launchpad beta testing and I have _some_ experience in programming and coding. I would like to get more experience. With this in mind, I would like to work on this if possible.

Depending on what skills and level of expertise is required for fixing this, I would be willing to work on this, especially if I got someone to mentor me on this to assist me if I ever get stuck on it.

I do not know if this is an appropriate place to post this; if so, can it please be deleted? If not, please contact me and we can work the details out, if possible.

I do not agree with this bug. When I test fixes, I need to have the permission of the case I am testing. I should only have the power of an admin when I am testing the behaviour of an admin. This need is rare and there is always a losa available to make me an admin.

Agreed: contractual obligations make the idea of having some devs be admins on staging a leeetle frightning, and its simply not needed: it would interfere with those devs doing QA. We might in future do something to allow better, temporary, privilege switching for developers on staging.