Mail notifications sent to team admins on joins / leaves to open teams

Bug #815623 reported by Robert Collins
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Robert Collins

Bug Description

Open teams are teams where the admins have explicitly decided they do not want to vet or control the membership. Notifying admins in this case is arguably pointless: there is no action they can take on a join (other than making the team moderated or restricted), and likewise on leaves.

Some users may use membership changes as a proxy for interest in their project / mailing list, but I don't think this is the common case: these mails are fundamentally spam. See for instance bug 285414 asking for an option to control these notifications, and bug 507515 asking for subscription facilities on team metadata.

Tags: email qa-ok teams

Related branches

Revision history for this message
Chuck Frain (chuckfrain-deactivatedaccount) wrote :

The value of these emails is to help track the churn of the group, particularly around events that the group might hold. Also it allows the admin to send out a personal welcome to new members or a goodbye email to those leaving.

I'd say if they are annoying most admins of these open groups can configure a suitable email filter to trash them as they arrive..

If a change is deemed necessary by this 'bug' please make it a checkbox option for the admin. Just because you view it as useless spam, others consider it a valuable tool.

Revision history for this message
Flemming Christensen (laoshi) wrote :

For the Danish LoCo team the checkbox option would be perfect. For our team these mails are low volume, but they are a good means to keeping an eye on the membership flow.
Like Chuck Frain we think that a checkbox option to turn those mails on/off would be fine.

Revision history for this message
Alan Bell (alanbell) wrote :

I find them useful, and not annoying for the ubuntu-uk team updates.

Revision history for this message
Martin Owens (doctormo) wrote :

I find the emails to be useful, but a little repetitive. It would be more useful for me to have a monthly report showing all the users who have changed status (joined, removed, left, expired, renewed) and then I can take any external action based on that.

It also gives me a better churn overview than single emails. If this idea is good, I will make a separate bug report.

Revision history for this message
Bret Fledderjohn (bret-fledderjohn) wrote :

I don't mind the emails, however I can definitely see the benefit of a checkbox option to turn the notifications off/on... I like Martin's idea as well.

Revision history for this message
Robert Collins (lifeless) wrote :

With regard to having folk setup mail filters, its a poor user experience if upon becoming a developer in (say) drizzle, you immediately need to add several list filters to turn off unwanted email.

We intended the LP API to provide good facilities for reporting and analysis, and I think it can be used to do daily/weekly/monthly reporting for community management.

Regardless of whether we have a checkbox or not, the key question for me is what is the sane default: should we mail people about things they cannot control and which have no functional impact by default, or not?

(LP has a strong culture against options-for-everything - we want to figure out the best behaviour, and use that, and only add options as a last result). I don't think we've tried nearly hard enough here, yet :).

Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 815623] Re: Mail notifications sent to team admins on joins / leaves to open teams

@doctormo
> It also gives me a better churn overview than single emails. If this
> idea is good, I will make a separate bug report.

Please do, I think thats a good report to have.

-Rob

Revision history for this message
Robert Collins (lifeless) wrote :

I've now discussed this with Curtis, who has spent a great deal of time talking to other users and looking at how our mailing list / team management features hang together.

He pointed me at bug 285414, which was filed because of the same behaviour - its a feature request asking for a way to turn the notifications off - essentially asking for a checkbox. That bug needs a wider change to be addressed than this bug because folk may want to opt out (or in) to changes in moderated/restricted/private teams as well.

He also pointed me at bug 507515 which asks for the ability to subscribe to changes in a team - so that non-admins can send welcome emails, have a feel for activity around the team, and so forth.

So, big picture, what we want to do is:
 - allow subscriptions to team metadata changes of various sorts, including membership
 - still send notifications when an action needs to be taken [e.g. approving a moderated join request]
 - stop sending notifications to folk who are not subscribed
 - default admins for non-open teams to have a subscription.

The question then, is can we reasonably make the change to address this bug before implementing subscriptions to team metadata? The consensus we have in #launchpad-dev is that we can: we have a bug going back to 2008 asking for less mail about this sort of thing.

So, I'm going to land my branch for this; if anyone wants to work on bug 507515 I'm positive we can get some mentoring for you.

description: updated
Curtis Hovey (sinzui)
tags: added: email teams
Revision history for this message
Michael Kotsarinis (mk73628) wrote :

I am in favor of a checkbox for the notifications. DoctorMo's idea is also very nice.

Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
Changed in launchpad:
assignee: nobody → Robert Collins (lifeless)
tags: added: qa-needstesting
Changed in launchpad:
status: Triaged → Fix Committed
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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