CoreOS team stopped using and maintaining Triagebot and we need to find a way to maintain it, unless we want to stop using it too and use plain Jira for stuff like timeouts on needinfo.

Currently we don't know how many people are using the bot, but even if we move the repo the existing images should stay and will just stop being updated.  If there are others using it we could let someone else maintain the repo and move it under "openshift" org in GitHub. We could also move it to GitLab.

The maintenance burden should not be too high due to the repo being mostly inactive, there is no vendoring and versions are not pinned to any version in requirements.txt.

Currently the bot is deployed in MP+ from personal Quay instance which is not optimal, for details see our wiki page [1]. 

We should also consider image builds as we need them stored somewhere so the deployment on MP+ can access them. Currently the images are stored on Quay [2].

For communicating with CoreOS team we can use their Slack channel '#forum-rhel-coreos' and tag '@coreos-leads' if needed since there is no assigned maintainer at this point.

Things that should be done:
1) try asking around (aos-devel mailing list?) and try to find some other volunteer or team willing to maintain the repo of possible
2) plan how to build and store images
3) migrate the repository

[1] https://gitlab.cee.redhat.com/devel/ocp-storage-devel/-/wikis/Triagebot-guide
[2] https://quay.io/repository/coreos/triagebot?tab=tags&tag=latest