Comment 8 for bug 302897

Revision history for this message
Graham Binns (gmb) wrote : Re: [Bug 302897] Re: Private teams don't satisfy ValidPersonOrTeam, so can't set them as bug supervisor (or set private bugs for a project they registered)

2008/11/28 Guilherme Salgado <email address hidden>:
> AIUI, it is intentional that these teams can't be linked to most things.
> That is to prevent leaking of private memberships.
>
> Have you seen the "Team Visibility" section in doc/person.txt?

I've read that, but it didn't make the rationale behind the
implementation clear.

Private membership teams are just that: private membership; i.e. we
don't expose the membership list for the team. However, that the team
itself exists isn't a secret and any of them are easily navigable to
in the interface, hence my comment about hiding teams from the search
results, above.

AIUI we need to be able to set private teams as bug supervisors
(amongst other things). I assume that a workaround for that would be
to make the private team part of a public team and then set the public
team as bug supervisor.

Another problem is that private teams can't have bug subscriptions (LP
OOPSed when we tried setting things manually in the database). I don't
know whether the workaround I described above would work around this
problem, too.