On Sat, Feb 02, 2008 at 07:03:58PM -0000, Christian Reis wrote:
> If the team is managed in a Launchpad mailing list, I think we actually
> get this right, though. So maybe that's an easy way of solving Scott's
> problem.
I'm not sure we are, and I'm also not sure we are on an agreement what
'getting it right' means.
> One additional thing we could do, Bjorn, is exclude a subscriber's
> direct notification if he is already a member of a team getting
> notified. That wouldn't be very easy to do with the current code but
> would be possible. More generally, what we'd do is take into account
> team participation when uniqing the emails. Reason I don't know that's a
> good idea is there's a problem: people might be expecting to receive the
> direct email (for instance, if they are members of the team but not
> subscribed to the team's mailing list) will stop.
I'd say we can't do that. What we could do when we have a LP hosted
mailing list, is to only send a direct notification, and not send one
via the mailing list to that. If we wouldn't send a direct notification
at all, we'd break the workflow for many people. I, for one, subscribe
to quite a lot of Launchpad bugs, even though I'm subscribed to the
launchpad-bugs mailing list. If I wouldn't get a notification sent
directly to me, subscribing to a bugs would be useless for me, and it
would be harder for me to manage my bugs. For example, I probably
wouldn't participate in this discussion if I would get the
notifications via launchpad-bugs.
BTW, there is no right or wrong here. Some people prefer getting two
notifications, some don't. The only way we could solve this, keeping
everyone happy, is to add a preference, so the user can choose for
himself.
On Sat, Feb 02, 2008 at 07:03:58PM -0000, Christian Reis wrote:
> If the team is managed in a Launchpad mailing list, I think we actually
> get this right, though. So maybe that's an easy way of solving Scott's
> problem.
I'm not sure we are, and I'm also not sure we are on an agreement what
'getting it right' means.
> One additional thing we could do, Bjorn, is exclude a subscriber's
> direct notification if he is already a member of a team getting
> notified. That wouldn't be very easy to do with the current code but
> would be possible. More generally, what we'd do is take into account
> team participation when uniqing the emails. Reason I don't know that's a
> good idea is there's a problem: people might be expecting to receive the
> direct email (for instance, if they are members of the team but not
> subscribed to the team's mailing list) will stop.
I'd say we can't do that. What we could do when we have a LP hosted
mailing list, is to only send a direct notification, and not send one
via the mailing list to that. If we wouldn't send a direct notification
at all, we'd break the workflow for many people. I, for one, subscribe
to quite a lot of Launchpad bugs, even though I'm subscribed to the
launchpad-bugs mailing list. If I wouldn't get a notification sent
directly to me, subscribing to a bugs would be useless for me, and it
would be harder for me to manage my bugs. For example, I probably
wouldn't participate in this discussion if I would get the
notifications via launchpad-bugs.
BTW, there is no right or wrong here. Some people prefer getting two
notifications, some don't. The only way we could solve this, keeping
everyone happy, is to add a preference, so the user can choose for
himself.