Before September 1,
#github channel has been tracking commits, bug tracker activity, and occasional PRs and comments on commits. When we enabled PRs, new events started to appear: opening and closing of PRs, review submits, and comment on reviews. It feels like amount of notifications on that already fast-paced channel doubled.
I’ve been triaging old Clang bugs for the past 4 months. A part of this effort is to keep an eye on other activity in old bugs to make sure it’s done correctly and to the full extent (e.g. reproducible old bug is labeled as
confirmed, otherwise it’s hard to tell triaged and untriaged bugs apart in the haystack of bugzilla bugs).
I’ve been leveraging
#github channel for this purpose to avoid flooding my inbox, and it’s been working pretty fine for me. But now I’m barely keeping up with it. It’s rather important, because we continue to see new people triaging old bugs, like @DavidSpickett did today for lldb bugs, which I try to offer guidance to.
I consider this use case important enough, so I’m trying my best to keep up with existing
There are different options here:
- The minimal solution is to split off PR-related notifications into
#github-prs. This brings previous status quo back.
- Having separate
#github-prswould be a notable improvement over previous status quo for me.
- @EugeneZelenko suggested having dedicated channel for
- Eugene also suggested having a dedicated channel for reopened issues and closed issues as requiring more attention than usual. Maybe opened issues require belong here as well.
I’d prefer option 2, and postpone 3 and 4 until Eugene gets onto our Discord server and see for himself whether those channels are useful for him when compared to mail filters.