1

I’m on a bot kick recently!

In the same vein of Meetingology needing to be made, there used to be a bot in the Ubuntu Development channel in Matrix that tracked patch pilots, altering the topic, etc.

However, that bot seems to have died and gone away. SO, I wrote one.

Introducing @patchpilotsbot:darkchaos.dev for the Ubuntu Development channel.

(Disclaimer: darkchaos.dev is one of the domains I use to run my development and stuff on, that homeserver is controlled by me not a third party)

Wait, what’s a patch pilot?

A patch pilot is a developer or member who is helping to pilot getting patches, merge requests, etc. against packages in Ubuntu actively and is around to help with that process as well if you need them and their assistance. Okay, I gave a meh description, just read here: Ubuntu Patch Pilots

So, why track them?

So people can see they’re on or offline!

Okay, enough side queries.

The bot is made on the same basic nio-bot framework that I’m using for Meetingology. But without the heavy duty DB integration for meeting tracking.

The bot has three outward-facing commands:

  • @pilot [action] where action is either “in” or “out”. This way the patch pilots can show themselves as around or remove themselves from the active list.
  • @pilots will list the current list of patch pilots ‘in’.

And… that’s really it. Not much more for a patch pilots bot. I’m working on making sure it can’t be spammed and misused, and restricting it to known Matrix IDs for Ubuntu Members and other subgroups which recursively inherit the Ubuntu Members group, but it’s a slow going API query process. Which isn’t in the production bot at the moment.

3 Likes