- ๐ฉ๐ชGermany FeyP
quietone, smustgrave, andy-blum, dww, cilefen and I discussed an older policy issue about self-RTBCing core issues in Slack. During the discussion, it was suggested that we might use a bot to help with issue triage. Such a bot could make suggestions when a new issue is created, updated or stalling. This could range from information on how to get more eyes on an issue, e.g. an auto comment for issues tagged 'Needs usability review' that states that there is a regular usability review meeting, to potentially other triage tasks based on issue metadata that could easily be automated. cilefen mentioned GitLab's https://gitlab.com/gitlab-org/ruby/gems/gitlab-triage bot, which could be used to implement this. It could also be used for one-off issue updates or to post introductions to new features as suggested in the IS. More might be possible through plugins. Examples for the policies in use at gitlab.com can be found here: https://gitlab.com/gitlab-org/quality/triage-ops/-/tree/master/policies Just for reference, quietone posted a good summary of the discussion in #2706483-45: [policy, no patch] Policy to help less interested Patch move forward. โ .
- ๐ฉ๐ชGermany FeyP
Adding ๐ฑ Categorize contributions that could be considered 'gaming the credit system' and propose solutions (policy, automation, etc) Active as a related issue.