Re: Gnus interface to Bugzilla?

[Sebastian Freundt <hroptatyr@sxemacs.org>]

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

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Steve Youngs <steve@sxemacs.org> writes:
>
>> `/ s' solves that for one-group-per-product.
>
> But surely you wouldn't display all the responses to all the bugs in
> the product normally?  `C-u g' on a product would pull in an awfully
> large number of messages...
>
>>   > And if you're not interested in a bug, you just kill the group.
>>   > Etc.
>>
>> one-group-per-product would just use scoring here.
>
> True, but you have the latency issue.  Selecting the messages is one
> extra call to show_bugs.cgi.
>
>> BTW, suppose I was a Mozilla developer... your one-group-per-bug means
>> I could have anywhere up to 300000 groups in my Gnus!!  That's just
>> insane.
>
> No, you'd kill them off as you go along.  nnslashdot uses a
> one-group-per-item approach, and that seems to work well.

Hm, the problems with the one-group-per-bug approach I see is that I can
hardly imagine anything when I read bugzilla_mozilla_org.firefox.bug498
Adding a description is no option either, it'll be a flood of weird stuff
in my Group buffer.

> There's also the dreaded "numbering issue".  You have to map bugzilla
> comments to article numbers, and using a several-bugs-in-one-group is
> a nightmare.  You'd have to keep such a mapping up to date locally,
> which is brittle.  With one-group-one-bug, you just use the natural
> numbering of the bug report.

You do not need to use the natural ordering of numbers, just use 
article# = bug# * 1000 + n, with n=0 for the original post and the n-th
comment otherwise.

How about making it customisable whether to use <site>.<product> groups or
<site>.<product>.<bug>?

Sebastian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEPmcblMmhrILJOQ4RAu2ZAJ9RuzU7Jyw99Z4hfqeXq0oQ5vGbnQCfRAJT
AUI4kAhEdVV8mhPQYjgIWec=
=YQhB
-----END PGP SIGNATURE-----