On Tue, 2010-09-21 at 11:58 -0400, Curtis Hovey wrote: ... > Projects and Distributions and Teams > .................................... > > For projects and distributions, the private primary structure rule means > that series, milestones, releases, downloads, and announcements are private. > They cannot be made public and users cannot be subscribed to these items > to gain access. > > For teams, archives, mailing-lists, and polls are private. This is true now. > When teams are used in project or team roles (owner, driver, members, mirror > admins), the team must be restricted to ensure a user cannot gain access > though team membership.
bac: Which team must be restricted? The private team or the team the private team joins? I suspect the former but it is unclear. sinzui: both! a private team is already restricted. So I am saying that any team that owns it, or joins it must also be restricted. I am still not sure if we can let a private team join another team. The common argument for nested private teams is bug access. We will ensure that bug supervisor is not the way to access private bugs. -- __Curtis C. Hovey_________ http://launchpad.net/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
