Not saying that I like all the mails to dev, but those mails do contain the only discussions we have nowadays (Issues at github and comments on Pull Requests). So I also do see some value in the current way. Is there a way to filter out those mails and keep them coming to dev@?
For this reason for me a -0. We should not forget that the primary way of communication (and decision making and archiving) is the mailinglist [1]. Arguably, 'notifications' is also a mailing list, but I'm not sure if we do right to the community with that... [1]: http://theapacheway.com/on-list/ Op wo 29 apr. 2020 om 21:11 schreef Pepijn Noltes <[email protected]>: > Hi Roy, > > Sounds good, +1. > > On Wed, Apr 29, 2020 at 6:58 PM Roy Lenferink <[email protected]> > wrote: > > > > Hi all, > > > > Currently all GitHub activity is sent to our dev@ list. I'd like to > propose to change this to a new > > [email protected] list. > > > > This way Celix contributors/watchers on our dev list won't be 'spammed' > with all the ongoing GitHub > > traffic and for the people who still want to receive the GitHub > notifications it is opt-in to a separate > > mailing list. It will also be easier to find actual (development > related) discussions when browsing > > through the [email protected] messages on lists.apache.org [1]. Also, when > already watching the GitHub > > repository notifications will be sent twice: once from GitHub, once from > the dev list. > > > > Lazy consensus will apply: no objections within the next 72 hours and > I'll request the mailing list. > > Changing the notification scheme is self-serve via the .asf.yaml [2] > > > > Best regards, > > Roy > > > > [1] https://lists.apache.org/[email protected] > > [2] https://s.apache.org/asfyaml-notify > -- Met vriendelijke groet, Alexander Broekhuis
