1. IMHO asking products to move user lists will creat an unneccessary reason why a move might be rejected.
I think one credible sign of how large a project is how busy the users traffic would be.
It might be the first sign that a project should be spun off to a TLP.
2. the experience at jakarta-commons is that the dev lists are too high traffic for many users. users who can stand the heat can sign up for the kitchen. those who can't, sign up for a low traffic user list. developers are expected to sign up for both.
Isn't it that jakarta-commons has one dev list for everyone? Here in Apache Commons, we've proposed one list per functional grouping (provided the caveat from before that a 'large' functional grouping should be split off). I think it's reasonable to at least try that model.
Over on the incubator, I know Greg and many others have strongly advocated the one list approach until a project grows in size. I tend to think that's right for projects with the correct scope/size in Commons. If that doesn't work for a community, then the community is probably too big. -- justin
