It is very common in every project I participate to use different mailing list for these different goals: users, developer discussion, bug tracking and commits. It makes it easier to filter, and it allows for people that care about one particular area to focus on that area.

If you want all the mail mixed up, you have the choice of doing that in your email program, but there is no need to force other people into your development model. Having multiple lists, one per task makes it so that people can opt-in into what they want instead of having to opt-out with complicated rules that they have to updated every once in a while.


On Feb 14, 2009, at 11:53 AM, Oswald Buddenhagen wrote:

On Sat, Feb 14, 2009 at 05:43:55PM +0100, Patrick Winnertz wrote:
Well.. I would like to have some place to discuss everything.

of course.

If this is too much it would be worth to move this to a separate

yes - *if*. but that's not going to be the case. i cannot imagine that
the additional effort resulting from fragmenting the communication
channels even more would be in any way justified. but that's not my
decision anyway ...
Mc-devel mailing list

Mc-devel mailing list

Reply via email to