Thanks Curtis. This is exactly what we did and I realized this a couple of minutes after sending the comment.
We have now created two teams for each project, one Foo Team (foo) and one Foo Core Team (foo-core). The first team is open and owns the mailing list. The second is restricted and owns the code. Furthermore, we've made foo-core a subteam of foo.
This seems like a good solution and does not require much work to set up. Is there some Launchpad guide or best practices for how to best make use of Launchpad to organize a project? I might not have looked carefully enough.
Thanks Curtis. This is exactly what we did and I realized this a couple of minutes after sending the comment.
We have now created two teams for each project, one Foo Team (foo) and one Foo Core Team (foo-core). The first team is open and owns the mailing list. The second is restricted and owns the code. Furthermore, we've made foo-core a subteam of foo.
This seems like a good solution and does not require much work to set up. Is there some Launchpad guide or best practices for how to best make use of Launchpad to organize a project? I might not have looked carefully enough.