On Tue, Jul 6, 2021 at 1:10 PM Dave Fisher <w...@apache.org> wrote: [SNIP] > Tell me why a split discussion is good for the community?
I feel like I didn't do a good enough job of responding to this point, so to clarify further: My answer is that it's *not*. However, that problem already exists with any issue tracker. Discussions happen on JIRA today, as well as on GitHub pull requests, or ReviewBoard, or Slack. We can moderate the notifications list to prevent additional discussions from occurring there, so this wouldn't create a new forum for discussions to be split across. That's a misunderstanding of what I'm proposing. The purpose of this change isn't to split up discussions further. Rather, it's intent is to make it easier to *find* discussions to participate in. One way it does this is by removing redundant spammy notifications if users are already being notified by GitHub directly because they have subscribed to the repo there. Reducing this spam on the dev@ list makes finding the remaining discussions on the list easier, because there's less noise to wade through. It also makes it easier to find discussions happening on GitHub, even if you aren't subscribed, because if you choose to subscribe to the second list to receive notifications that way, filtering your mail in your email client is much more reliably done with a "list-id:" header that is unique for each mailing list than it is with only pattern-matching on a "subject:" line. I hope that helps clarify the intent here. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
