I have rather hard as a mentor in the Incubator now that all new projects use GitHub. Much development discussion is driven away from dev@project mailing lists and occurs in issues(if enabled) and PRs.
comdev-site: https://github.com/apache/comdev-site/blob/master/.asf.yaml notifications: commits: [email protected] issues: [email protected] pullrequests: [email protected] One - issues have not been enabled so that setting is meaningless to comdev-site. Why add notifications@ when commits@ exists? .asf.yaml allows: # Send new/closed PR notifications to dev@ pullrequests_status: [email protected] # Send individual PR comments/reviews to issues@ pullrequests_comment: [email protected] So PRs could be split, but we are already having a split discussion of https://github.com/apache/comdev-site/pull/64 Tell me why a split discussion is good for the community? All The Best, Dave > On Jul 6, 2021, at 9:37 AM, Brian Thompson <[email protected]> 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
