yellow team mailing list archive

[Gary Poster <gary.poster@xxxxxxxxxxxxx>]

On May 12, 2011, at 2:20 AM, Brad Crittenden wrote:

> 
> 
> On May 11, 2011, at 16:39, Gary Poster <gary.poster@xxxxxxxxxxxxx> wrote:
> 
>> Hey Brad.  I took a look at the notes on http://summit.ubuntu.com/uds-o/meeting/other-o-launchpad-better-bug-subscriptions/ .  It looks like only a very few attendees, if the bottom of the page is any indication.  How did it go?
> 
> No, it was actually very well attended and we got good feedback.  Jeremy F., Brian M., and Kate S. were all there, participated, and were excited about the new features. Francis, Jono, and Ian also came and helped field questions. 

Awesome!

> 
>> 
>> Two answers and a question about the Q&A, btw:
>> 
>> Q: Have we decoupled being the bug supervisor of a project from getting all of the bug mail for a project?  Specifically, when you unsubscribe from the subscription you get when you are a bug supervisor, do you remain the bug supervisor?
>> A: This is not something our squad has worked on, so maybe gmb could confirm, but I believe the answer is yes.
> 
> It was shown that the team remains the bug supervisor. I think the question is whether the subscription is really unsubscribed. If the bug supervisor really gets a subscription (I.e. It isn't special cased) then I suspect it works as expected. 

Yeah, I understood.  I just looked at the code, and I'm pretty sure I'm right (I think lp.bugs.model.bug.get_also_notified_subscribers is the pertinent place to look).  The only special cases are assignees and the owners of bugtask pillars for which the bug supervisor is not set.

So, yes, they are decoupled.  The only connection is that setting a bug supervisor creates a subscription, which can be separately managed (including deletion) after the fact.

> 
>> 
>> Q. If you have multiple matching subscriptions, which x-launchpad-subscription headers do you get.
>> A: All of them.
> 
> One header for each?

Yes.  (I verified in lib/lp/bugs/mail/tests/test_bugnotificationbuilder.py.)

> 
> 
>> 
>> Q: Why do teams with a contact address appear when viewing +subscriptions?
>> A: [I don't understand the question]
>> 
> 
> If a team has a contact address (a mailing list for example, like ~launnchpad did) then all team email goes to that address, not to the individual recipients. In that situation it does not make sense to let individuals mute or unsubscribe because those actions will not affect the mailing list and the email will still be delivered. Check with Brian for further explanation as he raised the point. 

Ah, yes.  

I disagree that it should not appear: we want +subscriptions to explain what's going on, even if we can't offer a "fix" for it.  

I also disagree that we should not let individuals mute.  For myself, my mail rules handle list emails differently than personal emails.  I'd like the ability to mute my individually-sent emails. However, I agree that we need a warning of some sort.

I also agree that the listing should not let people opt out of the subscription.  This is "must fix" bug https://bugs.launchpad.net/launchpad/+bug/777786 .

Thank you, Brad!

Gary