Alexandre and Doru,
I see your point, and I see many other open source projects mixing issue notifications with the real development mails, thus corroborating it. However, I would say that the best setup would be using two different mailing lists, because many of the issue notifications are not informative at all (e.g., "Issue #x fixed.") and you get a wrong idea of how much "real" discussion is going on the list.
Other projects, such as ArgoUML adopt the multi lists approach. For example Argo has these lists:
org.tigris.argouml.announce org.tigris.argouml.commits org.tigris.argouml.dev org.tigris.argouml.issues org.tigris.argouml.modules-dev org.tigris.argouml.users
I've seen development mailing lists without discussions but with 2000 emails per month generated only by the issue tracking system. If this will be the case with moose-dev, (and many of the emails are really generated by the issue tracker) I would try to consider something different from mailing lists to coordinate.
In any case, this is my opinion, and it's up to you to decide. Of course, I can always filter emails out ;)
Thanks for reading.
Cheers, Alberto
On 7 February 2011 14:20, Alexandre Bergel alexandre@bergel.eu wrote:
I personally like the current setting. You can always filter out the mails you do not want to see
Alexandre
Le 7 févr. 2011 à 06:35, Alberto Bacchelli alberto.bacchelli@usi.ch a écrit :
Hi all,
Why is the issue tracking system sending messages to this mailing list?
Wouldn't it be better to have a second mailing list for issue notifications, so that moose-dev does not receive so many messages?
We can always discuss here the issues that are worth-discussing, just by forwarding emails from the "issue notifications" mailing list to here.
Just in my humble opinion.
Alberto _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev