Where are these "rules we've written over the years for wikibugs (what bug updates go to which channels)" currently stored / can be seen?

If we decide this is the way to go: https://github.com/wikimedia/labs-tools-pywikibugs/blob/master/channels.py

The notifications are handled by PhabricatorBotFeedNotificationHandler:

https://secure.phabricator.com/diffusion/P/browse/master/src/infrastructure/daemon/bot/handler/PhabricatorBotFeedNotificationHandler.php

I think it would make more sense to configure this directly in phabricator:

We could add a custom field to projects called "irc channel" which would be used to associate a project with a channel.
Then any updates to tickets in a given project would get posted into the relevant irc channel automatically.

In addition to this it would be nice if we had a way to specify the types of notifications that get filtered, on a channel-by-channel basis, but for starters a simple project filter would suffice.

Would this approach also help fixing T763: Phabricator far too spammy and off-topic to continue posting to wikibugs-l?

Testing to see if this comment goes into the right channel!

Well, that didn't work. https://github.com/legoktm/phabricator/commit/7b93dd1bb9eae1a350e52d691a2ddfbaddc44dac is how far I got.

I'm not really sure if it's a good idea to hack on the code directly or if there's a preferred way to extend it.

The IRC bot code is 'work in progress' according to the Phab team, so I presume they would be happy to accept patches that improve the bot output (as long as it's configurable).

In T324#10861, @valhallasw wrote:

Naming of tags will be: (from T43#5660)

Bugzilla product	Bugzilla component	Phabricator project
MediaWiki	Change tagging	MediaWiki-Change_tagging
MediaWiki‑Vagrant	labs-vagrant	MediaWiki_Vagrant-labs_vagrant
Wikimedia	Git/Gerrit	Wikimedia-Git_and_Gerrit
Wiki Loves Monuments	Unused images	Wiki_Loves_Monuments-Unused_images

I'm confused by this comment. Are tag names relevant here? Programmatic access should happen via IDs, I thought.

@Legoktm one way to approach this would be to fork the message handler class ( or subclass/extend it ), that way our changes are mostly isolated to a separate file and hopefully don't cause too much maintenance headaches if we have to maintain our own custom handler outside of the upstream.

See

https://github.com/legoktm/wikibugs2/blob/master/channels.yaml

for the format, although those do not seem to be the current rules. In any case, the actual rules should be in git before Day 1.