Digging a little deeper into this, it turns out that we actually
already *have* a commits@ [1] *and* an issues@ [2] mailing list. I'm
assuming dev@ is signed up to issues@; at least, that's what appears
in the Reply-To: for me.
After Dies' and Andrew G's comments, my proposal would thus be to:
1) Create a notifications@ mailing list (or rename issues@ if that is
possible, to preserve the history)
2) Request for commits@ to be deleted and notifications@ to be signed
up for ASF Git commit alerts in its place
3) Use notifications@ in place of dev@ for all JIRA, ASF Git, GitHub,
BuildHive and DEV@cloud alerts
4) Leave it up to individual developers to sign up for notifications@,
i.e. *not* to subscribe dev@ to that list by default
Assuming nobody has any concerns/objections about this, I'd plan to
start creating the appropriate INFRA issues on Fri 6th Sep. Hopefully
that will give everyone enough time to comment.
@mentors: is this kind of "just a discussion thread" approach
appropriate here, or would something like this better be handled by a
formal [VOTE]..?
Regards
ap
[1] http://mail-archives.apache.org/mod_mbox/jclouds-commits/
[2] http://mail-archives.apache.org/mod_mbox/jclouds-issues/
