launchpad-dev team mailing list archive

[Matthew Paul Thomas <mpt@xxxxxxxxxxxxx>]

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

Tom Berger wrote on 02/12/09 15:25:
> 
> 2009/12/2 Jonathan Lange <jml@xxxxxxxxxxxxx>:
>...
>> there is any real sense in which, malone say, is a separate *project*
>> from registry. It grates on me that we model it that way in Launchpad.
>> Ideally, we'd have one project (launchpad) and many teams, and work
>> could be coordinated through teams. Would you agree with this?
> 
> Not quite. For users to be able to effectively file bugs without
> creating a lot more work triaging, they need to be able to tell us
> which component of Launchpad the bug is in. We then take this
> information and feed it to the team responsible for that component for
> triaging and resolution.
>...

I know I'm a month late on this, but one point that wasn't mentioned in
this thread: When I was doing QA, I noticed that a majority of our
duplicate bug reports had been reported *because* we were using multiple
projects. People would report a bug at
<https://bugs.launchpad.net/launchpad> and not get any duplicate
suggestions, because the originals had already been moved to other
Launchpad projects. So, using multiple projects has a QA cost.

The kneejerk answer is to make duplicate detection optionally work
across projects in a project group <http://launchpad.net/bugs/174443>.
But that would benefit only projects in tightly related project groups.
Beefing up up tags so that Launchpad itself can use them instead of
projects (tag autocompletion, tag subscriptions, "tag:" search operator,
etc.) would be more work, but it would benefit many more projects.

- --
Matthew Paul Thomas
http://mpt.net.nz/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAktExnAACgkQ6PUxNfU6ecqUNACeL/UOhSqxnVzHJ5lz2RhmBgOT
GdsAn0LYM2x2NL53+ndkXEcwMx0cLtMZ
=EfKH
-----END PGP SIGNATURE-----