My original reason for wanting a users mailing list was to separate out discussions about the framework from questions about the domain (so to speak).
It didn't feel appropriate (and it still doesn't) sending questions related to "should I implement this DDD code in the Customer class or in the factory?" It has nothing to do with the framework, per se. With regards to filtering out the auto messages, I have filters in my email client that do that for me. Admittedly, it only works on the one client, but anyway. I would support a vote for a list that receives the JIRA / Hudson messages, if required. On 11 Dec 2011 at 15:34, Rafael Chaves wrote: > It is not that is confusing, it is a matter of increasing the > signal-to-noise ratio. I want to be aware of the discussions. I have no > interest on any of the generated messages (issues, builds, commits). I > suspect others (non-committers) may feel the same. > > I don't get why we would need to pollute the discussion with any > automatically generated messages, even if a single message a day. Those > (probably committers) interested in following commit, issue tracking or > build activity closely are probably already able to opt-in for automatic > notifications on an individual basis, with each one of those activity > streams. > > My 2 cents.
