Ubuntu Bugzilla to Malone (Launchpad) migration complete

[Matthew Paul Thomas]

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

On 19 Jan, 2006, at 4:05 AM, Ian Jackson wrote:
>
> Matthew Paul Thomas writes ("Re: Ubuntu Bugzilla to Malone (Launchpad)  
> ...
>> You can easily edit the bug URL to go to a different bug. Your  
>> context might be one where the other bug isn't filed, but you can  
>> still read it and click on the links etc.
>
> Oh, so I can.  Thanks.  I'd assumed from looking at the URL that that
> wouldn't work.

Okay, I've redesigned the URLs so they're less consistent with the rest  
of Launchpad, but more obviously hackable.  
<https://wiki.launchpad.canonical.com/BugWorkflow#head 
- -9619367deed3945609d3478d798434a8501b54e5> What do you think?

>> <https://launchpad.net/products/launchpad/+bug/929>
>> (In your example, the problem happens only in Gecko, but other  
>> examples
>> happen regardless of browser.)
>
> I can't easily see dates on these comments (why not?),

Because they're in a dark grey box with a black outline, directly  
underneath a uselessly redundant subject line.

> ...
>> There is no standard terminology for this part of what Malone does,
>> which is asking for the bug to be fixed in multiple places (e.g. in
>> packages of multiple distributions). Suggestions for more obvious
>> wording would be useful, though.
>
> `Asking for the bug to be fixed in multiple places' is meaningless to
> me.  The reason question is, who would I by asking and how would I be
> asking them ?

You would be asking whoever wants to fix the bug (often the maintainer  
of the product or package), and you'd be doing it by clicking a button  
in Malone.

For example, if I found a bug in Firefox in Ubuntu, I'd report it on  
Ubuntu's Firefox package, which would probably mean it was dealt with  
by you. You might find that the bug also existed upstream, so you'd  
request the fix upstream, and that would be dealt with by any of dozens  
of people because Firefox is such a componentized product.

> Furthermore, when I file a bug I'm not `requesting a fix'.  I'm
> `notifying the developers'.  For many bug reports I already have a
> local fix or workaround; the usual purpose of reporting the bug is to
> improve the software, not to allow me to get my work done.
>
> Filing bugs is not an abstract action directed at software.  It's a
> social action directed at people.
> ...

That's not how Bugzilla works. When Ubuntu was using Bugzilla, were it  
not for the hack to deal with Ubuntu's large number of component names,  
you wouldn't have known who a bug was assigned to until after you  
reported it. And in bugzilla.mozilla.org, many components are like  
Malone in that a bug isn't assigned to anyone human even after it's  
reported. If I wanted to perform a social action directed at  
developers, I'd get on the phone to them instead. :-)

- -- 
Matthew Paul Thomas
http://mpt.net.nz/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFDzr/m6PUxNfU6ecoRAi+1AJ9RDjLjMrllzK9ftnO44AV23TbApwCfWCUu
kQJlWgkvqZOFGCuyKPSyn/Y=
=ejwT
-----END PGP SIGNATURE-----