Comment 1 for bug 405277

Hi Brad. Thanks to taking this issue.

I think Public <- Private is [N]. This is a painful rule because it will require some real teams to manage a public and a private launchpad teams so that they can work public and private projects.

I think private team owners will want to add their private team to a public (owner, driver, bug supervisor) team because those roles are needed to do some task. Presumably the admin of the public team is also a member of the private team, but we know the membership can change. Communication within the team will be awkward because a member of a private team is a "double-agent" who must guard everything he says and does to not revel he has a private interest. I think we want to avoid this conflict of interest (as we should have done when mailing lists were added to teams)

The official recipe will require a separate pubic team. I am sure there will be a duplication of membership at first. I believe the public team membership will naturally diverge from the private team because the interests of the two teams are not the same. That is to say, If were were to permit Public <- Private, users will get into trouble when they discover they need to create a separate pubic team to collaborate with other users. Let's avoid the situation.

If this division proves to be awkward, we can look at making team creation and membership management easier.