close
The Wayback Machine - https://web.archive.org/web/20100125013922/http://incubator.apache.org:80/ip-clearance/index.html
The Apache Software Foundation Apache Incubator

Image Intellectual property clearance

One of the Incubator's roles is to ensure that proper attention is paid to intellectual property. From time to time, an external codebase is brought into the ASF that is not a separate incubating project but still represents a substantial contribution that was not developed within the ASF's source control system and on our public mailing lists. This is a short form of the Incubation checklist, designed to allow code to be imported with alacrity while still providing for oversight.

This form is not for new projects. This is for projects and PMCs that have already been created and are receiving a code donation into an existing codebase. Any code that was developed outside of the ASF SVN repository and our public mailing lists must be processed like this, even if the external developer is already an ASF committer.

Incubating projects should use the incubation STATUS tracking to handle incoming IP clearance.

The intent is to simply help to ensure, and record, that due diligence (Software Grant, CLA, Corp CLA, license and dependencies) has been paid to the incoming code, so that it can be merged into an existing project/module. These legal documents are available on the ASF Licenses page.

The receiving PMC is responsible for doing the work. The Incubator is simply the repository of the needed information. Once a PMC directly checks-in a filled-out short form, the Incubator PMC will need to approve the paper work after which point the receiving PMC is free to import the code. Note that only lazy concensus is required. The IP clearance template contains more details of this process.

For new IP clearance forms, start with our XML IP clearance template and follow its instructions. Here is the more readable HTML version.

Clearance document Receiving PMC Date recorded
Ant Groovy Front Apache Ant 2009-12-18
User Admin Apache Felix 2009-12-01
Improved HttpService Apache Felix 2009-09-04
Sigil Apache Felix 2009-07-03
OSGi Shell Apache Felix 2009-05-26
mod_fcgid Apache HTTP Server 2009-02-03
OpenXML4J Apache POI 2008-11-11
velocity-tiles Apache Tiles 2008-10-31
local-lucene Apache Lucene 2008-09-15
commons-flatfile Apache Commons 2008-09-04
felix-remote-shell Apache Felix 2008-08-11
harmony-1680-contribution-javap-kononov Apache Harmony 2008-05-22
Pax Logging Apache Felix 2008-06-02
OSGi Console Apache Felix 2008-05-13
Kitten Auth Apache Wicket 2008-05-10
harmony-5742-contribution-microemu-teodorczyk Apache Harmony 2008-04-25
UIMA-AS Apache Incubator 2008-04-23
mod_domain Apache HTTP Server 2008-04-18
maven-archiva-webdav Apache Maven 2008-03-13
File Install Apache Felix 2008-02-06
Deployment Admin Apache Felix 2008-01-09
xmlgraphics-batik-xmleditor-component Apache XML Graphics 2007-11-28
trinidad-translations Apache MyFaces 2007-11-27
torque-village-contribution Apache DB 2007-10-22
maven-shade-plugin Apache Maven 2007-09-10
jsr-301-ri Apache MyFaces 2007-09-04
maven-archetypeng Apache Maven 2007-08-29
Apache CXF Wsdl2JS Tool Apache CXF (Incubator) 2007-07-30
Shale Clay Plugin for Eclipse Apache Shale 2007-07-11
maven-patch-plugin Apache Maven 2007-07-05
Cactus Apache Jakarta 2007-03-24
jackrabbit-bundle-persistence Apache Jackrabbit 2007-03-07
derby-2248-contribution-tests-ibm Apache DB 2007-02-26
xmlgraphics-commons-postscript-dsc-parser Apache XML Graphics 2007-02-26
geronimo-2743-ibm-covalent-j2g Apache Geronimo 2007-02-19
TRIPLES-1: mod_sparql Incubator 2007-02-18
TRIPLES-2: libb Incubator 2007-02-18
TRIPLES-3: RDFStore Incubator 2007-02-18
Apache::Reload Apache-Perl 2007-02-08
derby-2134-contribution-tests-ibm Apache DB 2007-01-10
Wombat Apache HTTP Server 2006-12-06
directory-triplesec Apache Directory 2006-10-18
directory-mitosis Apache Directory 2006-10-18
xmlgraphics-fop-afp-renderer Apache XML Graphics 2006-04-20
activemq Apache Geronimo 2006-04-18
servicemix Apache Geronimo 2006-04-18
jakarta-commons-composite-pool Apache Jakarta 2006-03-19
Jakarta Commons CSV Apache Jakarta 2006-04-21
ode-2-intalio-pxe Apache Ode / Incubator 2006-03-13
ode-1-sybase-bpe Apache Ode / Incubator 2006-02-21
geronimo-1478-xbean Apache Geronimo 2006-02-13
harmony-16-contribution-classlib-intel Apache Harmony / Incubator 2005-12-20
myfaces-tobago Apache MyFaces 2005-12-20
harmony-14-contribution-classlib-ibm Apache Harmony / Incubator 2005-11-24
geronimo-1111-trifork-initial Apache Geronimo 2005-10-27
harmony-6-contribution-jvm-daniel-lydick Apache Harmony / Incubator 2005-10-08
harmony-3-ccontribution-jcvm-archie-cobbs Apache Harmony / Incubator 2005-10-04
harmony-5-component-poc-david-tanzer Apache Harmony / Incubator 2005-09-28
harmony-127-contribution-plugin-ibm Apache Harmony / Incubator 2006-03-01
harmony-88-contribution-tests-ibm Apache Harmony / Incubator 2006-03-01
harmony-57-contribution-tests-ibm Apache Harmony / Incubator 2006-03-01
harmony-438-contribution-drlvm-intel Apache Harmony / Incubator 2006-05-31
maven-surefire Apache Maven 2005-11-07
maven-doxia Apache Maven 2005-11-07
geronimo-1016-ibm-daytrader Apache Geronimo 2005-09-20
geronimo-875-ibm-eclipse Apache Geronimo 2005-08-16
geronimo-762-ibm-console Apache Geronimo 2005-07-14
geronimo-iiop Apache Geronimo 2005-01-15
apr-jlibtool Apache Portable Runtime (APR) 2004-07-08
portals-gluecode-jetspeed Apache Portals 2004-06-27
ws-sandesha Apache Web Services 2004-05-02
ws-wss4j Apache Web Services 2004-02-24
Zookeeper Apache Hadoop 2008-07-15

Additional notes

The software grant requires that "Licensor owns or has sufficient rights to contribute the software source code...". In the case where there are multiple entities involved that only together have sufficient rights (for example in the case of an existing external project with multiple contributors), there are basically two possibilities to continue:

  1. All entities sign the same software grant together and submit one software grant form. This is preferred but obviously can complicate the process considerably.
  2. The alternative is that each party sign its own software grant while everyone references the same contribution (designated by a URL and an MD5 hash over the ZIP file representing the contribution). It is recommended that the software grant form is modified in order to have a line for each party so the completeness of the paperwork can be verified upon receipt.