Comment 5 for bug 861058
Revision history for this message
| Martin Pool (mbp) wrote Re: [Bug 861058] Re: can't make membership of one team conditional on membership of another | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
On 30 September 2011 08:24, Robert Collins <email address hidden> wrote:
> So the specific case given is easily addressed: make ~canonical a
> member of the *list*, and individuals can *subscribe* - this is how
> its intended to work.
One specific case. The thing that actually brought it to mind was
seeing people who left Canonical months ago being belatedly removed
from staff-only teams.
> There are other cases, such as bug management and internally
> restricted disclosure which this doesn't help with - but for those
> simply saying 'must be in the organisation' is also not sufficient
> (because that would allow anyone to escalate their privileges
> trivially). So, the symptom is accurate, but permitting it isn't
> necessarily the right way to address the underlying needs.
If Launchpad supported "must be in $other_team" then you could within
that say that the team was either open (eg ~canonical-tech) or
moderated or restricted (eg internally need-to-know teams.) But
perhaps another better approach is possible.