Launchpad itself

Access privileges for Launchpad projects/users?

Asked by Mike Stoddart

Now that Launchpad is open sourced, I'm investigating it to see if we could use it at work. But I can't find any details on user privileges. Does Launchpad support:

1) per project access privileges, e.g.
   - Joe can create bugs on ProjectA but can't view any code
   - Fred can create bugs on ProjectA and can view code / changesets
   - Jim can create bugs on ProjectA and can view and submit code / changesets
   - Neil can't create/read bugs on ProjectA and he can't view or submit code / changesets

   - Neil can create bugs on ProjectZZZ and can view and submit code / changesets
   - Joe can create bugs on ProjectZZZ but can't view any code

etc..

Thanks

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Curtis Hovey
Solved:
Last query:
Last reply:
Revision history for this message
Best Curtis Hovey (sinzui) said : 		#1

Launchpad uses the Zope security infrastructure.

The ZCML files defines the access permission for objects and attributes. The definitions of each kind of permission is in lib/canonical/launchpad/security.py.

Launchpad Privacy is s secondary set of permissions where a only subscribers or members can see the bug, branch, or team. That happens in the model (the privacy attribute) and there are formatters that hide the object if it is shown in the wrong location. The mechanism is still build on the zope.security mechanism, the models and formatters work to prevent the object from being shown because a forbidden error will be raised of the object is exposed.

Revision history for this message
Mike Stoddart (stodge) said : 		#2

Thanks - guess I need to read about Zope.