Getting rid of ~bzr-core ... take 2

[John Meinel]

I'm pretty sure we okayed this back when you proposed it. I have far worse
issues with other groups I'm part of. (If a group only has an owner but not
an explicit bug contact, there isn't/wasn't a way to unsubscribe from the
bug mail)

John
=:->
On Apr 9, 2012 2:02 AM, "Max Bowsher" <_ at maxb.eu> wrote:

> Way back in June last year, I initiated a discussion about getting rid
> of the ~bzr-core team, because its purpose is somewhat confusing.
>
> We established back then that the entire existence of the team was for
> people who shied away from the volume of bugmail for plugins that ~bzr
> was subscribed to.
>
> There was a slight tone of assent for getting rid of ~bzr-core, but a
> final resolution wasn't reached, and I dropped the ball on herding to
> discussion to a useful conclusion.
>
> I'd like to pick this up and finish it off.
>
> Concrete proposal:
>
> 1) Unsubscribe the following teams (which are all subteams of ~bzr) from
> all their current bugmail subscriptions:
>
>        ~bzr-gtk
>        ~bzr-hg
>        ~bzr-upload-devs
>        ~qbzr-bugs
>
>  [This can only be done by an administrator of the teams in question]
>
> 2) Merge the ~bzr-core team into ~bzr
>
>
> I'll suffix that by mentioning that this no longer has any significant
> effect on me personally, as I've now gone through and clicked all the
> relevant places in Launchpad to individually mute my participation in
> current structural subscriptions via ~bzr - but, I think this is still
> worth doing, for the convenience of future members, and to remove the
> ~bzr / ~bzr-core ambiguity once and for all.
>
> Max.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/bazaar/attachments/20120410/ec806893/attachment.html>