Ok, here are my comments:
-jon
4.2.1: Define "minimized". In other words, something that seems minimal to
one may not seem minimal to another.
4.2.2: I think that "should" should be changed to "must".
4.3: Define a number on the amount of committers.
5: It should be a "must". Also, this whole point is *WAY* to broad. What is
"standard"? I see at the bottom there is a Resource section, but I don't
think that covers it well enough.
6: I think that "should" should be changed to "must".
7: Should provide an interface or implement a Sun defined interface. (ie:
The connection pool would fall under this wouldn't it?)
9: what is the definition of "preferred"? Is that a "should" or "must"? Is
that really what you want to say there? Again, the example of the db
connection pool. If Turbine is going to integrate/use this connection pool
that is defined by this project, it *must* have its configuration in a
Properties file (or have pluggable configuration that allows for a
properties file) because that is the way that Turbine does it. Therefore, I
propose that all commons projects which have the need for configuration have
a pluggable configuration mechanism.
15: Should be broken into two separate points.
Resources:
May I suggest that the Java coding documentation be amended to require
*NOT* having tabs in the files. The reason it simple: tabs make it
nearly impossible to read the CVS commit logs because emails don't
format properly with tabs.
Additional: the issues surrounding logging and pluggable logging
implementations are not covered here. I think they have the same importance
as configuration. My vote is that we standardize on simply using Log4J and
its interfaces for *everything*.
thanks,
-jon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
