> For an example, see [EMAIL PROTECTED] - flood and the > perl-framework 'share' the same infrastructure. Perhaps have a > general [EMAIL PROTECTED] for these 'smaller' components. If > requested, then components can have discrete infrastructure support. > But, it's a royal PITA to create infrastructure for small stuff. I > think commons is going to have a lot of smaller codebases than other > projects mainly because reuse will be a prevailing factor.
Agreed. This has shown to work very well in jakarta-commons. When httpclient started taking up over 1/2 of the mailing list traffic, we just created a httpclient-dev list, while keeping all the lower traffic projects together on the dev list. Scott
