following on from the discussion, I'd like to outline the proposal to bring a vote on two topics. I'm not sure what level of contribution defines bindingness (committer?)
Proposal #1: create [email protected]<mailto:[email protected]> for notifications. Machine-generated emails would go here: 1. JIRA edit/update notifications, 2. git/svn commits Issue 1a? Jenkins: do we want jenkins broke/fixed emails to still go to dev@? Especially on the state change events? That is, if jenkins is still broken, don't send updates, but if someone dies just break it, let everyone know. Issue 1b? JIRA completions: the hadoop dev lists are set up so that when JIRAs are completed they are announced on the dev@ list. This means that even if you don't care about ongoing work, you do get to keep an eye on what has just finished. Proposal #2: create [email protected]<mailto:[email protected]> for general usage emails I think we could do a vote on this while still resolving/tweaking issues 1a and 1b; that's a matter of tuning the email settings in those builds & JIRA projects until we are happy. -Steve
