Get rid of the ~bzr-core team?

[Max Bowsher]

On 14/06/11 10:07, Alexander Belchenko wrote:
> Max Bowsher пишет:
>> The ~bzr-core team is a fairly confusing entity. Its name invokes an
>> impression of a higher privilege level than ~bzr, whereas the reverse is
>> actually true, since ~bzr is a member of ~bzr-core.
>>
>> As far as I know, ~bzr-core only exists to provide a common team to
>> which people who would otherwise be in ~bzr, but are unwilling to
>> tolerate the torrent of bugmail that currently implies, can be added.
> 
> I think that's true, but only that. Recently ~bzr has been made a
> subteam of Olive-gtk project team, and therefore it gets bugmails and
> codereview mails for Olive.

That change was subsequently reverted.

>> Having completed the removal of code review email to ~bzr, this seems
>> like a good time to review the bugmail situation:
>>
>>
>> ~bzr is subscribed to ~bzr-core which is subscribed to:
>>   * bzr
>>   * ubuntu/bzr
>>
>> ~bzr is directly subscribed to:
>>   * bzr-website
>>   * bzr-usertest
>>   * bzr-hg
>>   * bzr-email
>>   * bzr-git
>>
>> ~bzr is subscribed via other team memberships to:
>>   * bzr-gtk
>>   * ubuntu/bzr-gtk
>>   * bzr-upload
>>   * qbzr
>>   * ubuntu/bzr-hg
> 
> also Olive.

Not anymore.

>> This is a fairly eclectic set of bug subscriptions. I do not see any
>> particular rationale for which Bazaar-related projects are included or
>> excluded from it.
>>
>> I would like to propose that we unsubscribe ~bzr from all of this.
>>
>> People who wish to receive core bzr bugmail can explicitly subscribe to
>> 'bzr' and 'ubuntu/bzr' (or just 'bzr'). Unlike the situation with code
>> review, where individual subscriptions to each series branch were
>> required, Launchpad already models subscribing to a whole project or
>> distribution source package for bugmail just fine.
>>
>> People who wish to receive additional bugmail for Bazaar related
>> projects can subscribe to the ones that they are interested in, rather
>> than relying on ~bzr's arbitrary selection.
>>
>> Having rationalized our bugmail subscriptions in this way, the original
>> need for the ~bzr-core team will have disappeared (IIRC), and we can
>> merge ~bzr-core into ~bzr.
>>
>> Completing this will require liasing with the owners of ~bzr-gtk,
>> ~bzr-upload-devs and ~qbzr-bugs, from which ~bzr currently inherits
>> bugmail subscriptions - but I think it's worth taking the time to do so
>> to improve the current situation.
> 
> I don't like to have mails about Olive and maybe even bzr-gtk, it's
> already more than enough for me to maintain qbzr and bzr-explorer. As I
> understand it, ~bzr wants to know about popular bzr plugins and tools to
> be able provide an expertise on their bugs. Many of such plugins/tools
> are de-facto maintained by bzr team. So I've moved my participation from
> ~bzr to ~bzr-core just to reduce the number of notifications those I'm
> unable to handle anyway.
> 
> I'm not quite sure how it should be according to your proposal.

According to my proposal, ~bzr shouldn't be getting any bugmail at all,
and you should be free to subscribe to what they actually want.

Regards,
Max.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/bazaar/attachments/20110614/e35466e4/attachment.pgp>