team A members are notified when team A becomes a member of another team

Bug #194003 reported by Barry Warsaw
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Recently we hit a situation that ended up spamming lots of users with team membership changes. We have the mailing-list-beta-testers team to which other teams must join in order to gain access to the mailing list feature. Some team erroneously request that mlbt be joined to their team (instead of the other way around), and this happened with the coriander team.

Normally, we just reject the invitation and admins get the rejection notice. However, in this case we accidentally accepted the invitation and this membership change ended up spamming everyone who is an indirect member of mlbt, which is a lot of people because many teams are mlbt members.

Another data point: at the time of this accident, mlbt did not have a contact address. The hypothesis is that membership changes are sent to all members, or the contact address, when really membership changes should only be sent to the team's admins. mlbt now has a contact address.

There's also the case that mlbt's membership in coriander expired, and everyone got spammed with those too.

See also bug 113705 and bug 44795

See also:

http://paste.ubuntu-nl.org/56837/
http://paste.ubuntu-nl.org/56838/

Revision history for this message
Barry Warsaw (barry) wrote :
Revision history for this message
Barry Warsaw (barry) wrote :
Revision history for this message
Barry Warsaw (barry) wrote :

Some irc discussion indicates that there may be use cases where individual members might want to know about membership changes. Perhaps this should be an option when the invitation is accepted. If so, you definitely want to know how many people will be notified of the change.

Options might be to 1) only email direct team admins; 2) only email direct members (give count); 3) email all direct and indirect members (definitely give count)

Other possibility includes "hide the fact that you're doing this change from everybody?" check box.

You get the idea.

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Are there any cases, other than accidents, where team members should not be notified that their team has become a member of another team?

If there are use cases for this, a checkbox would be a good idea (though I think it should be positive, i.e. "Notify all members of A that they're joining B", rather than negative, i.e. "Hide this change").

But the accident case wouldn't be fixed by any option. It could be fixed by giving the team admin 5 minutes to change their mind about the membership before the notification is sent out.

Changed in launchpad:
status: New → Confirmed
Revision history for this message
Christian Reis (kiko) wrote :

I find the use case for wanting to notify all team members kind of weak. We don't do that for mailing list subscribers when the subscriber list changes. Notifying bug subscribers that a bugs CC list has changed is one of the things Bugzilla does that I find appalling. We get this right in most cases; I don't see why we should spam in this instance.

Curtis Hovey (sinzui)
Changed in launchpad-registry:
importance: Undecided → Wishlist
status: Confirmed → Triaged
summary: - only team admins should be emailed about team membership changes
+ team A members are notified when team A becomes a member of another team
tags: added: notifications
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.