Fully agree, Usually, we have a dedicated mailing list like commits or github.
Regards JB On Mon, May 30, 2022 at 3:42 AM Yuan Wang <[email protected]> wrote: > > Hi, > > Yes, i think it is a good idea to separate automatic notification from > general discussions, > I receive two notifications of the same topic. > > And i think it is noisy for people who are only interested in our new > changes or big progress. > > Best, > Yuan Wang > > tison <[email protected]> 于2022年5月30日周一 08:54写道： > > > Hi rockers, > > > > Do you notice that GitHub activities overwhelm the dev@ mailing list? I > > invited several potential participant to subscribe the dev@ list and they > > all feedback that GH activities noisy. > > > > Although it's fair that any subscriber can create filters on their mailbox, > > __we may require dedicated mailing lists for issues(issues@) and > > commits(commits@)__. For example, Flink[1] has notification settings as > > below: > > > > notifications: > > commits: [email protected] > > issues: [email protected] > > pullrequests: [email protected] > > > > Logging all development activities on mailing list is a requirement of the > > Apache way[2], but we can separate automatic notification from general > > discussions. Also, ppl used to receive notification by watching GH repos > > can keep their way. > > > > What do you think? > > > > Best, > > tison. > > > > [1] > > > > https://github.com/apache/flink/blob/e7834d8b56a7b4b1c2674ab399032e21e76d9e63/.asf.yaml > > [2] Open Communications https://www.apache.org/theapacheway/index.html > >
