http://incubator.apache.org/incubation/Incubation_Policy.html#Minimum
+Exit+Requirements
These requirements were previously considered in [EMAIL PROTECTED] in
2004-11-25, see http://marc.theaimsgroup.com/?l=apache-logging-
general&m=110141756729362&w=2 and following.
This section describes the requirements and process for exiting the
Incubator.
Minimum Exit Requirements
Prior to escalation to the ASF, a Podling needs to show that :
it is a worthy and healthy project;
it truly fits within the ASF framework;and
it "gets" the Apache Way.
This is achieved by imposing a set of Exit Criteria that, when met,
will demonstrate these objectives.
Therefore, to successfully exit the Incubator and be escalated
fully into the ASF, a Podling SHALL meet the minimum exit
requirements detailed below. The Incubator PMC MAY set additional
requirements at their discretion. Such additional requirements MAY
be proposed by the Mentor or the Sponsor, however only the
Incubator PMC is authorised to formally place such requirements on
a Podling.
The minimum requirements that a Podling SHALL meet prior to being
successfully escalated to the ASF are :
Legal
All code ASL'ed
No non ASL or ASL compatbile dependencies in the code base
License grant complate
CLAs on file.
I believe these are all complete based on previous statements and
both LS and the Incubator PMC approving a 1.2.10 development snapshot.
The code base does not have NOTICE and LICENSE files (instead it has
NOTICE.txt and LICENSE.txt) as required in http://www.apache.org/dev/
release.html#license. Also the headers have not changed to be
compatible with the ASF Source Header and Copyright Notice Policy
(http://www.apache.org/legal/src-headers.html, https://
issues.apache.org/jira/browse/LOG4NET-98).
Build process apparently uses a nightly build of NAnt (based on path
in build.cmd) which has a GPL license. Should be updated to NAnt 0.85.
Check of project name for trademark issues
Google search for log4net exclusively came up with ASF related links
(or the earlier SourceForge log4net which indicates code has moved to
ASF) with the exception of log4net.net which appears to be a domain
parker (Domain Drop S.A served by EVERYPARKING.COM) and does not
provide any software. Should make a review of the code base (like
the README.txt) and change plain "log4net" to "Apache log4net" as
appropriate.
Meritocracy / Community
Demonstrate an active and diverse development community
The project is not highly dependent on any single contributor
(there's at least 3 legally independent committers and there is no
single company or entity that is vital to the success of the project)
Commits in 2006 were exclusively rgrabowski and nicko, niall and
drieseng had several commits in 2005. nicko and niall are both
founders of NeoWorks. I am not aware of any other relationships
between committers. psmith and yoavs have commit rights but have not
committed any changes according to the log. carnold has only
committed project metadata. However, I did submit bug fixes to
log4net long before my ASF involvement.
The above implies that new committers are admitted according to ASF
practices
Ron Grabowski was added in 2005: http://marc.theaimsgroup.com/?
l=log4net-dev&m=112446388920346&w=2
ASF style voting has been adopted and is standard practice
Examples:
http://marc.theaimsgroup.com/?l=log4net-dev&m=114176984807315&w=2
http://marc.theaimsgroup.com/?l=log4net-dev&m=114262269805255&w=2
http://marc.theaimsgroup.com/?l=log4net-dev&m=114372496806325&w=2
Demonstrate ability to tolerate and resolve conflict within the
community.
Any examples?
Release plans are developed and excuted in public by the community.
(requriment on minimum number of such releases?)
Note: incubator projects are not permitted to issue an official
Release. Test snapshots (however good the quality) and Release
plans are OK.
Examples:
http://marc.theaimsgroup.com/?l=log4net-dev&m=114175221718400&w=2
Engagement by the incubated community with the other ASF
communities, particularly infrastructure@ (this reflects my
personal bias that projects should pay an nfrastructure "tax").
Plays well with Logging PMC. Not much other interaction that I am
aware of.
Incubator PMC has voted for graduation
Pending.
Destination PMC, or ASF Board for a TLP, has voted for final
acceptance
Pending.
Alignment / Synergy
Use of other ASF subprojects
Would be nice to have an Ant or Maven build in addition to NAnt.
Develop synergistic relationship with other ASF subprojects
Good relationship with log4j and log4cxx.
Infrastructure
SVN module has been created
Yes, http://svn.apache.org/repos/asf/logging/log4net
Mailing list(s) have been created
Mailing lists are being archived
Yes,
http://mail-archives.apache.org/mod_mbox/logging-log4net-user/
http://mail-archives.apache.org/mod_mbox/logging-log4net-dev/
Issue tracker has been created
Yes, JIRA
Project website has been created
Yes, http://logging.apache.org/log4net
Project ready to comply with ASF mirroring guidlines
Should not be an issue.
Project is integrated with GUMP if appropriate
Gump attempts, but fails, to build NAnt and successfully builds
dotnet-antlib. It does appear that Mono is present on Gump, so a
Gump build appears to be achievable. I have posted a message on
[EMAIL PROTECTED] asking for guidance. I assume that pursuing an Ant-
based build on Gump would be more effective.
Releases are PGP signed by a member of the community
No releases so far.
Developers tied into ASF PGP web of trust
I verified Ron Grabowski's PGP fingerprint at ApacheCon US 2006.
I've reiterated a request for him to upload it to a keyserver, but
when he does I can sign it. I participated in the keysigning party
there, so I'm decently cross-signed. Nicko is not cross signed
according to http://people.apache.org/~henkp/trust/apache.html and
niall does not appear. There would seem to be a reasonable chance
that you could track down a cross-signed ASF committer in Central
London, but I could not find one on the people.apache.org map (which
only shows people who disclosed their location).
