Hi all, I've noticed that some other Apache projects have a separate mailing list for JIRA notifications (Spark, for example, has iss...@spark.apache.org). The result is that the dev@ mailing list is focused on actual discussions threads (like this!), votes, and other official business. Would we be interested in doing the same?
In my opinion, the status quo is not great. The dev@ archives ( https://lists.apache.org/list.html?dev@arrow.apache.org) aren't that readable/browseable to me, and if I want to see what's going on in JIRA, I go to JIRA. In fact, the first thing I/we recommend to people signing up for the mailing list is to set up email filters to exclude the JIRA noise. Having a separate mailing list will make it easier for people to manage their own informations streams better. The counterargument is that moving JIRA traffic to a separate mailing list, requiring an additional subscribe action, might mean that developers miss out on things like new issues being created. I'm not personally worried about this because I suspect that many of us already aren't using the mailing list to stay on top of JIRA issues, and that those who want the JIRA stream in their email can easily opt-in (subscribe). But I'm interested in the community's opinions on this. Thoughts? Neal
