Hello all,
The ultimate goal of any Commons is to develop a shared codebase of
components that are not large enough to be maintained on their own, and
reduce replication of functionality in separate projects. This is not
only integral to a healthy developing codebase at Apache, it is
Mark R. Diggory wrote:
I personally think that the idea of Commons should become more
Virtual and Evolutionary in nature.
if theres ever the case that xml commons and jakarta commons
could become a shared community, it would produce the following
benefits
Mark, what you are saying is
Why don't the various commons groups in the ASF just have the AC PMC
add things on the A-C site and 'federate' that way? The respective
PMCs would still do what they do - oversee the projects - and the AC
PMC can maintain the website.
geir
On Dec 23, 2003, at 4:44 PM, Noel J. Bergman wrote:
Hell ya. We can start this right away. Great idea, Geir.
Now why didn't I think of that? :-)
Cheers,
-g
p.s. note that Jakarta acting as a Java-based codebase federation is a
separate matter; the J PMC can deal with that...
On Tue, Dec 23, 2003 at 09:12:34PM -0500, Geir Magnusson Jr wrote:
Geir Magnusson Jr wrote:
Why don't the various commons groups in the ASF just have the AC PMC
add things on the A-C site and 'federate' that way? The respective
PMCs would still do what they do - oversee the projects - and the AC
PMC can maintain the website.
I don't see why not. That
Quoting Noel J. Bergman [EMAIL PROTECTED]:
Geir Magnusson Jr wrote:
Why don't the various commons groups in the ASF just have the AC PMC
add things on the A-C site and 'federate' that way? The respective
PMCs would still do what they do - oversee the projects - and the AC
PMC can
Noel J. Bergman wrote:
Mark R. Diggory wrote:
I personally think that the idea of Commons should become more
Virtual and Evolutionary in nature.
if theres ever the case that xml commons and jakarta commons
could become a shared community, it would produce the following
benefits
Mark, what