You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by Curt Arnold <ca...@apache.org> on 2006/09/18 23:06:21 UTC
Escaping the incubator
Could someone summarize the unfulfilled criteria that is preventing
log4net from exiting the incubator? Any thoughts on a plan to reach
those criteria. I haven't been following log4net closely, but it
seems to be mature and accepted enough that it should graduate
sometime soon.
One thing that is problematic for log4cxx and may also affect log4net
is the umbrella structure of the Logging Services project. Umbrella
projects, where a Apache top-level project (a TLP) is composed of
independent semi-autonomous subprojects, have fallen out of favor and
several have spun out their subprojects as full-fledged TLP's. For
Logging Services, I would think that a reorganization as a single
project with multiple products would be beneficial, particularly to
projects that might have quorum issues. Since all the logging
frameworks in Logging Services (log4j, log4cxx, log4net and log4php)
have similar designs and concerns, it seems reasonable that a LS
committer might be well qualified to vote on a subproject issue even
if he does not usually contribute to that code base. The right place
to discuss project reorganization and bylaws changes is
general@logging.apache.org, but I did want to offer the option of LS
organization changes as a potential remedy if a quorum issue is
blocking log4net exiting the incubator.