Re: Gnus interface to Bugzilla?

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Wes Hardaker <wes@hardakers.net> writes:

> I actually had every bug appear as an article, and the entire article
> would contain all the items...  Functionally the article would be
> continually evolving.  I never really liked the zillions-of-groups
> method of doing stuff.

Zillion-groups has its problems, but I think it would fit the way I
work, at least.  At my day job, we use Bugzilla quite actively to
discuss, well, bugs and stuff.  Knowing that somebody has written
something new about a bug that I'm interested in would most naturally
be displayed in the group buffer along with the rest of the
work-related stuff, I think.

Of course, a totally different approach would also be possible.  That
is, write an nntp server that talks directly with the Bugzilla
database and run it on the Bugzilla server.  Then it could output
stuff like how many responses there are to each bug report, which
would make response snappy, and it could maintain bug response/article
number mapping, thereby making it possible to have all the bug reports
in one group.

However, that requires a) that someone writes that, and b) you're able
to convince the Bugzilla admin that it's a good idea.

Perhaps something like that could be a part of the Bugzilla
distribution.  nntp.cgi.  :-)

Hm...  the more I think about this, the more I think that's the
correct approach to take.  That way all news readers (not just Gnus)
could use it...

On the other hand.  Hm.  Not sure.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen