Hi,

What granularity do you think that should be allowable as commons codebases? 
Should we define the granularity as focus, as number of files, as committers 
or what?

For example. Where I am from we have a small library for dealing with Java 
Extensions (think .dlls or .sos with additional metadata). When the component 
started it had 2-3 source files with a single purpose. Over time it grew to 
be about 15-20 source files + ~40 unit tests. 

I guess my question is, Would it have been accepted when it was tiny (2-3 
source files), small or does it still not qualify. It matches other criteria 
(and was actually the merge of multiple projects code) but I am curious what 
you consider of the scope. 

It probably does not warrant it's own mailing list or it's own dedicated 
space. However it is a reusable focused component.

What do you think of this sort of situation (translated as appropriate for 
your own technology)? In or out?

-- 
Cheers,

Peter Donald
--------------------------------------------------
"An intellectual is someone who has been educated 
beyond their intelligence."
-------------------------------------------------- 

Reply via email to