Automate notifications for normative changes

[karwa]

With #238 we now have 5 bugs to file for normative changes, across 5 different issue trackers, and that still does not cover all interested parties. For example, I would also like to be informed of normative changes to the URL Standard, but my pokey little URL library isn't as big or important as large projects like Node.js or Deno, so it doesn't seem reasonable to ask contributors to file 6+ bugs.

It would be great if this could be automated in some way, so even smaller interested parties could be notified without imposing too high a burden on contributors.

[MattiasBuelens]

Most WHATWG standards have an associated Twitter account that automatically tweets each standard change. For example, you can follow https://twitter.com/urlstandard to keep up-to-date with changes to the URL standard.

[annevk]

I have thought about this before, but it seems somewhat challenging:

• Need to handle authentication for multiple separate systems. (GitHub issues might be easier to file I suppose, given that we already have a bot, but I haven't looked into it.)
• Need to handle authentication for the tool. (I suppose if it's automated it can always be done by the editors or perhaps even by participate.whatwg.org, so that reduces this problem somewhat.)
• I usually end up filing relatively custom bug reports to reduce the overload of having to sort out what needs to be done on the receiving end. I guess we'd have to give up on this.
• Needs to have the ability to not send notifications to projects that are not affected by a change (e.g., because they already pass the tests).

If someone wants to work on this I'd be supportive though.

[domenic]

I'd strongly prefer to continue filing manually in order to tailor the bug reports to each project. I think a "pull-based" solution for other projects, e.g. based on web hooks or the Twitter account, is probably the best for such long-tail consumers.