incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <>
Subject RE: log4net 1.2.9 beta release
Date Sat, 12 Mar 2005 13:19:39 GMT

You have raised the exact same legitimate concern about log4cxx.

Knowing log4X does not necessarily mean knowledge of log4Y, especially to 
the extent of taking over a project if and when the need arises. As such, 
having the LS PMC project take responsibility for log4cxx or log4net would 
be nothing more than an empty promise. However, I am happy to relay your 
concern to the LS PMC for their opinion on the matter. Also, I may not 
correctly understand what you mean by "take responsibility". Would you care 
to clarify what you mean exactly by the term "taking responsibility"?

The "truck numbers" for log4cxx and log4net seem to range between 1 and 
1+epsilon where epsilon is a real number close to zero. The situation for 
many other Apache projects may not be that much different either. Many 
smaller "component" projects do not require several active developers. One 
core developer is all that is required to get the project going. Once they 
reach a certain level of stability, many "component" projects only require 
a small amount of investment. Such projects' needs can be attended to by a 
loose community of semi-active committers.

The point I am trying to make is that smaller projects can do well with 
only a single but active committer while
bigger projects can overcome the test of time only in the presence of 
several active committers. I feel that the strong coupling between the 
required number of active commiters and the size and scope of a project 
should be duly recognized by the ASF. This subject matter was probably been 
beaten to death on previous occasions. Any pointers to such discussions 
would be highly appreciated.

At 09:55 PM 3/10/2005, Noel J. Bergman wrote:
>Roy T. Fielding wrote:
> > Assuming you can also confirm that
> > | ....-..-.. | Add all active committers in the STATUS file.
> > is done and the logging PMC is ready to accept responsibility,
> > then I think log4net should graduate from incubator.  +1
>Does Logging PMC have a community ready to take responsibility for the long
>term maintenance of this project?  One of the outstanding issues is avoiding
>"one man" projects.  AISI, the Logging PMC taking responsibility for log4net
>is a bit like the HTTP Server PMC taking responsibility for a Java re-write
>of HTTPd.
>         --- Noel

Ceki Gülcü

   The complete log4j manual:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message