cannot register contact address for a team to another list in launchpad

[Robert Collins]

I have a team in launchpad that controls commit access to a project -
https://edge.launchpad.net/~libcpuinfo-developers, and another that is a
list for anyone discussing the project -
https://edge.launchpad.net/~libcpuinfo-dev.

I'd like to set the mailing list as the contact address for the
-developers team, which the team form says is possible. But I get an
error:

"<email address hidden> is already registered in Launchpad
and is associated with libcpuinfo-developers".

 affects launchpad

--

[Curtis Hovey (sinzui)]

We do not want email addresses shred between team. We do need to allow teams to give up email addresses so that they can be reused.

[Robert Collins (lifeless)]

Why not? I can understand wanting people to have unique contact addresses, but not why that limitation should apply to teams.

[Curtis Hovey (sinzui)]

If I invalidate the address for one team, that other teams loose their email address.
If I want to contact the members of a team, I will also be contacting the members of other teams.

[Robert Collins (lifeless)]

On Wed, 2009-11-25 at 20:46 +0000, Curtis Hovey wrote:
> If I invalidate the address for one team, that other teams loose their email address.

I don't understand why that would happen.

> If I want to contact the members of a team, I will also be contacting the members of other teams.

And that would be fine for the use case I presented.

-Rob

[Barry Warsaw (barry)]

We could and probably should warn when an email address associated with multiple teams is invalidated, but I agree that it's probably not enough of a reason to prevent multiple teams from having the same contact address. Robert's original use case is a valid one if we're serious about distinguishing teams for communication and teams for permission. OTOH, if promoting mailing lists to first class objects obviates the need for the former, then maybe we're back to the status quo.

[Curtis Hovey (sinzui)]

I am accepting this bug because users are using offsite tools to route emails to accomplish this scenario. I think this scenario is hack to deal with the fact that Launchpad does a poor job of dispatching mail and choosing who to send it to. I think permitting shared email addresses would make the situation worse.

To implement this someone must first fix the many things that are fundamentally wrong with Launchpad and teams (accounts + email addresses + teams + ACL + mailing lists). The minimum work is:
1. Separate team email addresses from account email addresses.
2. Give teams full access to, and management of, their current and past email addresses.
3. Separate mailing lists from teams

[Robert Collins (lifeless)]

On Wed, 2009-11-25 at 22:32 +0000, Curtis Hovey wrote:
> To implement this someone must first fix the many things that are fundamentally wrong with Launchpad and teams (accounts + email addresses + teams + ACL + mailing lists). The minimum work is:
> 1. Separate team email addresses from account email addresses.
> 2. Give teams full access to, and management of, their current and past email addresses.
> 3. Separate mailing lists from teams

I think you're describing a more comprehensive solution than I was
asking for, but thats ok :)

-Rob

[Barry Warsaw (barry)]

Curtis, I fully agree with you that we should not make things worse and that we really need a re-thinking and overhaul as you describe.