On 7 Nov 2003, at 05:59, Justin Erenkrantz wrote:

--On Thursday, November 06, 2003 23:09:56 +0000 robert burrell donkin <[EMAIL PROTECTED]> wrote:

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.

sorry - i think we've been talking a little at cross purposes.

my point is that for some products, the requirement to merge existing user and dev lists into a single list may be a reason for rejecting the move to apache commons. i was trying to suggest that existing users lists are allowed to be retained (if that's what it takes) rather than insisting that (as part of the move to apache-commons) that the user lists must be combined with the development lists.

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

there's one dev list and one user list in jakarta-commons. it seems to work very well. the user list is there for users who don't want to subscribe to a high volume development list. user questions are definitely allowed on the development list.


you're probably right that the volumes within groups are unlikely to be too high to put off dedicated users. the only possible exception would be the propose core.

- robert



Reply via email to