This sounds good to me! The "issues" in the yaml are the GitHub issues, which are disabled in github right?
Any opinions on moving JIRA notifications from j...@apache.org to issues@ as well? That's what I would expect! I guess this would make little difference to me in practice since I would subscribe to both, but it would make it a lot easier to browse and link to the dev@ mailing list on the web! All my best, Ryan On Wed, May 6, 2020 at 1:15 AM Andy Le <anhl...@gmail.com> wrote: > > Hi Ismaël, > > Yep, I think it's a little bit noisy for our mailing list with such > notifications. But it's fun to see what other people are working on. > > IMHO, in addition to a new mailing list, we should have a better label > mechanism for easily routing/filtering messages. > > Thank you. > > On 2020/05/05 22:59:59, Ismaël Mejía <ieme...@gmail.com> wrote: > > Hello, > > > > Some of you have probably noticed that we are receiving a LOT of extra > > notifications that were not active in the past. This is happening because > > Apache INFRA installed a new way to map notifications into mailing lists > > for its > > projects and the default configuration right now is sending all the github > > notifications to dev@ > > > > https://gitbox.apache.org/schemes.cgi?avro > > > > So I would like to propose that we create a new mailing list called maybe > > iss...@avro.apache.org To send all the git individual PR comments/reviews > > there > > and only the new/close PRs here. > > > > I suppose that issues@ could be a list of interest for some people and it > > will > > help us have a more readable dev@ mailing list. > > > > Technically all we need to do is create the new ML on selfserve and a new > > .asf.yaml file following this format. > > > > https://s.apache.org/asfyaml-notify > > > > WDYT? Other preferences or other name for the mailing list github@ maybe? > > More configuration ideas? > > > > You can see a WIP of the proposed changes here: > > https://github.com/apache/avro/pull/873 > >
