It was my understanding that there was a requirement that there be at least 4 committers on an incubating project before it could graduate from the incubator. I was the 4th committer.
I think most people would agree that log4net has been considered quite stable for a number of years. ----- Original Message ---- From: Curt Arnold <[EMAIL PROTECTED]> To: Log4NET Dev <log4net-dev@logging.apache.org> Sent: Monday, September 18, 2006 5:06:21 PM Subject: 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.
