The original thread I posted this in got hi-jacked with other discussions, so I’m making a new thread for this.
People have expressed interest in having more information flow to the dev@ list about major features/decisions, so that those who don’t follow commits@ or JIRA can still keep up with big things that are going on. I don’t think we want to increase the volume too much, as then many people would feel the need to filter it out of their inbox, and thus possibly miss important discussions. So in order to keep dev@ low volume (but higher than it currently is) I propose we do something along the lines of the following: When someone has a major feature that they would like to discuss. (Again this is just for major features, not every day bug fixes etc) 1. Make a JIRA for the thing you want to discuss (will automatically be sent to commits@) 2. Post link to JIRA with a short description to dev@ 3. Have a discussion on the JIRA (will automatically be sent to commits@) about the new thing. 4. If there is some major change/question on the JIRA that people feel needs some extra discussion/involvement email dev@ with question and link back to the JIRA 5. Have more discussions on the JIRA (will automatically be sent to commits@) about the new thing. 6. If something else comes up go back too step 4. 7. When discussions do happen on dev@ about a ticket, those should be summarized on the JIRA as well so that everything is kept in one place. 7. During this process of decision making keep the “Title” and “Description” fields of the JIRA (aka commits@) up to date with what is actually happening in the ticket. 8. Once things settle down make sub tasks or follow on tickets for actually implementing things linked to the initial ticket. That would keep the dev@ list informed of what is going on in new feature proposals, and it will keep discussions on JIRA tickets where they are easily referenced and kept in one place. Keeping the title and description of the ticket up to date is an important part of this, so that when someone new looks at the JIRA they don’t need to read through 5 pages of comments to see what the current state of things is. -Jeremiah
