launchpad-dev team mailing list archive

[Aaron Bentley <aaron@xxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Collins wrote:
> Rather I'm proposing it because I believe the current
> partitioning of bugs is harmful to our team responsibility - it drives
> the need to do things like action groups to work on tasks, because tasks
> are not globally visible to the whole team by default.

I already get email about all launchpad bugs, via a mailing list that I
was subscribed to when I joined.  It is way too much.  So I filter it
into a "code team" folder and an "everything else" folder.  And I never,
ever look at the "everything else" folder.  Yesterday, it saved me from
having to read 95 emails about bugs that aren't part of my team's scope.

The partitioning is there for good reasons.  I don't know what I'd do if
I couldn't filter out the bugs I care about from those I don't.  Maybe
I'd unsubscribe from all of them.  In any case, it would not be a
positive outcome.

> Launchpad-project has 5800 bugs, and ~30 developers, or about 19 bugs
> per developer. bzr (core, not plugins) has 1800 bugs, and <10 developers
> developers, or about 18 bugs per developer. bzr hasn't split its bug
> database and the developers manage to get things done quite
> successfully :)

The Bazaar project *has* split its bug database.  ~bzr-core exists so
that people who are interested in bzr proper but not its ecosystem can
avoid getting spammed about every plugin associated with the bazaar
project group.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAksPBmkACgkQ0F+nu1YWqI3wEwCeLD7hn2QErDImn2qGjnZ/TIl/
eakAniqTwHItyF+g00xKlpDUCvoczIqu
=dn5A
-----END PGP SIGNATURE-----