Hi Wes,
I understand that you want to be up to date with regards to all issues
in Arrow. I think for a lot of people that won't be the case. They'd
rather opt-in in or watch individual issues.
However, it looks like there is no other way to get notified of newly
created issues; unless you're an admin of the project. So the existing
setting seems to be fine.
Good point on the governance aspect of informing everyone on the dev
list. Frankly, I'm not sure this is an effective way of getting more
people to maintain JIRA issues.
-Max
On 21.11.18 13:07, Wes McKinney wrote:
Only new issue notifications are being sent to the mailing list. issues@
receives all comments / changes so is at least 10x higher traffic. I get
issues@ in my inbox personally because it helps me stay on top of what's
going on in all aspects of the project.
I think new issues are relevant to general Arrow development. Developers
need to see bug reports, feature requests, etc so they can actively
participate in the project's governance. Otherwise the work will fall even
more disproportionately on the few of us that actively maintain and
prioritize the issues than it already does.
Of course, people with no interest in the the project issues can filter out
issues with "[jira]" in the title into a separate place in their e-mail.
Wes
On Wed, Nov 21, 2018, 5:58 AM Maximilian Michels <m...@apache.org wrote:
Hi!
Do you think it would make sense to send JIRA notifications to a
separate mailing list? Some people just want to casually follow the
mailing list and it requires a filter to delete all the JIRA spam.
I see there is already an "issues" mailing list which receives the JIRA
notifications: https://mail-archives.apache.org/mod_mbox/arrow-issues/
What do you think?
Thanks,
Max
