Great discussion, everybody! Here's some thoughts in response to some of the questions/concerns raised:
People should *not* have to subscribe to the other list in order to participate in discussions. It should just be for automated notices. The best practice is, like commits@, have it moderated and automatically reject anything not from "apache.org" to virtually eliminate any moderation effort. If you need to discuss, the best practice is to reply to it on the dev@ list to start a new discussion thread there. The reason not to use commits@ directly is because it's nice to have actual commit activity, for archival purposes, in its own dedicated list. Many projects have a jira@, notifications@, or issues@ list for automated notices from their issue tracker. That's all I'm suggesting here. I noticed that COMDEV JIRA notifications are also going to dev@. If you want to use the same notifications@ list for the COMDEV JIRA, I'd be in favor of that as well, but that's a separate issue that I wasn't intending to raise here. It has its own pros and cons. To configure that, it's not done in .asf.yaml, it's done at https://issues.apache.org/jira/plugins/servlet/project-config/COMDEV/notifications or by submitting a JIRA ticket to INFRA. Therefore, it's outside the scope of my PR to address the GitHub notifications. I also understand the concern raised about the difficulty of having discussions on dev@ because of GitHub's ease-of-use. However, I don't think forcing redundant notifications on GitHub users is the right solution, as it will discourage GitHub users from participating in the mailing lists... which is the opposite of what you want. The reason for GitHub users to participate in the mailing lists will be because they get value out of the mailing lists other than what they get from using GitHub directly. As for the comment regarding whether or not a destination should be set for `issues:`, GitHub considers pull requests to be a type of issue, so its important to set this value, even if you have issues disabled on GitHub, because (I believe) commenting on a pull request triggers the same notification as commenting on an issue. I believe `pullrequests:` is triggered for newly created PRs, but `issues:` is still used for notifications of any comments or code reviews on a pull request, as though it were any other issue. On Tue, Jul 6, 2021 at 1:16 PM Joe Brockmeier <j...@apache.org> wrote: > > First, I feel like I have to respond given the Truman State University sig. > It's rare I run into other Truman grads in the wild, though we wouldn't > have crossed paths on campus... (1998 grad here...) > > If the PRs appear here on this list, it makes it slightly easier to have a > discussion on list about the PRs. It also doesn't require people to go > upstream to subscribe to github or a second list. > > I wouldn't go so far as to say it's "unreasonable" to have a second list, I > just am not convinced it's desirable. > > As to the suggestion to discussing the PRs on the other list - then we have > to ask people to subscribe to both or miss some of the conversations about > the site development. Creating a filter for the GitBox notices + > subscribing to a new list are both about the same amount of work. If you > filter by sender or something like that you still can see discussions here > if anybody decides to go deeper on a specific commit. If you have to track > both lists, then that means a subset of the community is not going to see > those discussions either. (Either by omission or they just filter > everything and then see something six months later... ask me how I know...) > > Best, > > jzb > > On Tue, Jul 6, 2021 at 12:37 PM Brian Thompson <br...@hashvault.io> wrote: > > > I don't think asking for a new mailing list for GitHub notifications is > > unreasonable. In fact, I would go as far to say that having a GitHub > > notifications mailing list makes more sense than having those > > notifications being sent to the "dev" mailing list. Shouldn't the dev > > mailing list be used for discussion about the development rather than > > individual PRs? Those discussions can still be had on the other > > mailining list, if so desired. > > > > -- > > Best regards, > > > > Brian T > > B.S. Computer Science 2014 (Truman State University) > > Minor Stasitics > > Minor Chemistry > > Minor Mathematics > > > > > -- > Joe Brockmeier > Vice President Marketing & Publicity > j...@apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
