Decide on llvm-bugs@lists.llvm.org fate

[asl]

Currently it seems there is no automatic way to collect all issues notifications from a repo. We need to decide whether we need this mailing list and what to do with it.

Tagging @tstellar @kbeyls

[kbeyls]

I hope there won't be a need to forward issue notifications to llvm-bugs@lists.llvm.org anymore.
Anyone who wants to see bug/issue updates can now use the github notification system.
I've set up the following filter in gmail to try and filter bug/issue notifications that I'm not explicitly mentioned on to the same llvm-bugs label that I put on emails coming from llvm-bugs@lists.llvm.org:

from:(notifications@github.com) subject:("Issue \#" "[llvm/llvm-project]") cc:subscribed@noreply.github.com

I've created the filter based on the suggestions in https://gist.github.com/ldez/bd6e6401ad0855e6c0de6da19a8c50b5.
I hope I'll get a feel in the coming week(s) for how well the above filter works.

It'd be interesting to hear if anyone has a use case for llvm-bugs@lists.llvm.org that cannot be served by github notifications with an email filter.
I'm not aware of any such use case at the moment.

[nikic]

Currently it seems there is no automatic way to collect all issues notifications from a repo. We need to decide whether we need this mailing list and what to do with it.

FWIW it's pretty easy to do this via a webhook on the issues and issue_comment events. I assume that's how the llvm-commits mailing list is implemented right now, so the necessary infrastructure should already be in place. (For reference, this is how the webhook looks like for PHP: https://github.com/php/web-master/blob/dec8e6052477c456cc805097ec67ed6e82a5df3d/public/github-webhook.php#L337)

@kbeyls I don't use the llvm-bugs list myself, but I expect a problem would be that you usually only enable email for "participating" while web is used for "watching". I don't think there's a way to configure notification preferences per-repository.

[AaronBallman]

FWIW, I'm also hoping we can have better granularity than "per repo" -- I'd prefer not to have to watch every bug that's targeting Clang, but I would love to get automatically subscribed to any bug with a particular label associated with it. e.g., if someone marks a bug as being a "Clang attribute" bug, I'd like to know. Similar for keywords appearing in a comment or summary, such as "SemaDeclAttr.cpp" (etc) so I can be alerted to crash dump in my domain, etc.

[fhahn]

I hope there won't be a need to forward issue notifications to llvm-bugs@lists.llvm.org anymore.
Anyone who wants to see bug/issue updates can now use the github notification system.

IMO the main advantage of keeping llvm-bugs@ alive is to make the transition smoother for volunteers who use it to triage issues. I think even before the GH transition we were struggling with triaging and fixing a lot of the reported issues, so keeping the disruption to existing triagers as small as possible seems valuable.

[pogo59]

I would definitely like an llvm-bugs-like system for notification on issue creation only.
This lets me decide which issues I should add myself to. I don't want to see every comment, just the initial post for new issues.
Does the github notification system permit that? (I am notoriously bad at navigating complex web UIs, if someone has a recipe I can follow that would be great.)

[pogo59]

Also, the Cluster-fuzz issues still go to llvm-bugs.

[asl]

@pogo59 Apparently, there is no such functionality on github. So we'd need to invent something..

[pogo59]

Is there a way to write a github action that triggers on new issues only? And have that action send the issue as email to llvm-bugs?

[asl]

Is there a way to write a github action that triggers on new issues only?

Yes

And have that action send the issue as email to llvm-bugs?

In theory yes, but surprisingly enough, there is no ready action for this...

[asl]

Status update: I do have a proof-of-concept script that sends emails on new issues. Need to tune it a bit

[asl]

Implemented in 764f96c