Title: Cactus Codebase Intellectual Property (IP) Clearance Status

Cactus is an existing project at Jakarta. It was tempoarily outside the ASF repositiries, but on the sourceforge where we tested the new maven build system:

  • maven2 build system: A bunch of pom.xml's that automate the cactus build process.

  • maven2 plugin: Initial implementation of the “cactify” and “webxmlmerge” mojos.

  • cactus-site: A number of xdoc xml‘s that are transformed to html’s using maven2.

The contributed code can be found at https://mamouth.svn.sourceforge.net/svnroot/mamouth/Cactus/ and will be completely ported back to the current Jakarta Cactus codebase.

  • Which PMC will be responsible for the code: Apache Jakarta

  • Into which existing project/module: Cactus

  • Officer or member managing donation: Martin van den Bemt

Completed tasks are shown by the completion date (YYYY-MM-dd).

Identify the codebase

dateitem
NAIf applicable, make sure that any associated name does not already exist and is not already trademarked for an existing software product.

Complete move from sourceforge to Apache Jakarta Cactus. See https://mamouth.svn.sourceforge.net/svnroot/mamouth/Cactus/

Copyright

dateitem
2007-03-15Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project.
2007-03-16Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright.

Identify name recorded for software grant: Cactus Maven2 Build System ...

Verify distribution rights

Corporations and individuals holding existing distribution rights: Petar Tahchiev

dateitem
2007-03-15Check that all active committers have a signed CLA on record.
2007-03-15Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is required to authorize their contributions under their individual CLA.
2007-03-15Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute.
2007-03-15Check and make sure that all items depended upon by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms.

Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License.

Organizational acceptance of responsibility for the project

Related VOTEs: