Last modified: 2014-05-05 07:31:13 UTC
Petr Bena wrote: > That means anyone should be able to create a custom irc feed for > bugzilla and use it in any wikimedia related irc channel you want (for > example, right now we have a bugzilla feed in #wikimedia-labs that > reports only labs related bugs). You can generate RSS feed in > bugzilla, just by creating a new search, then you can click link > "Feed" which is on bottom of each search results page. This sounds neat. :-) I didn't realize Bugzilla had RSS feed support. Currently wikibugs (the Bugzilla --> IRC bot in #mediawiki) parses mailing list messages (sent to wikibugs -l). If there's a machine-readable format that can be used, that would be awfully nice. --- This should be investigated at some point. The mailing list parsing is decent, but still has bugs that would easily be resolved by using a proper input/output system.
Another disadvantage of relying on wikibugs-l@ is that currently it is NOT subscribed to ALL components/products. I've filed bug 40973 about that.
@Andre, if you want I can enable these components on wm-bot so that you get feed even for these as an experiment. There are several things that can't be parsed from RSS right now, for example the person who did the change to bug. As you can see from rss feed there is only several items to watch, right now it's: $author (person who created a ticket) $title $bugzilla_assignee $bugzilla_component $bugzilla_creation $bugzilla_priority $bugzilla_product $bugzilla_reporter $bugzilla_resolution $bugzilla_severity $bugzilla_milestone
Peter: Thanks for the offer, but I think I rather fix bug 40973 soon by adding wikibugs-l@ everywhere where it is currently missing so we can get a complete picture. :)
Reedy suggested <https://wiki.mozilla.org/Bugzilla:Addons#IRC_Bots>.
wikibugs has been superseded by pywikibugs ( https://github.com/valhallasw/pywikibugs ) - is this still a problem with pywikibugs?
The new pywikibugs is still based on email notification. A tools address is subscribed to wikibugs-l@lists.wikimedia.org and emails are forwarded to redis. That is a bit more robust than the wikibugs hook in exim but still based on emails :-] The idea behind this bug is to have a machine readable stream of events in the bug system. Maybe we can look at what Phabricator offers on this front and then close this bug entirely if Phabricator fulfills the need.
