Index: site-author/guides/ip-clearance.xml =================================================================== --- site-author/guides/ip-clearance.xml (revision 0) +++ site-author/guides/ip-clearance.xml (revision 650675) @@ -0,0 +1,243 @@ + + + + XYZ Codebase Intellectual Property (IP) Clearance Status + + +
+ Codebase IP Clearance TEMPLATE + 
-----8-<---- cut here -------8-<---- cut here -------8-<---- cut here-------8-<----
+
+ Preamble +

This document is the template for recording IP clearance on new +codebases. Please store the completed document in this Incubator +repository using a filename that reflects your project.

+

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 project, but +still represents a substantial contribution that was not developed +within the ASF's source control system. 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. 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.

+

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, everything is done.

+

All PMCs must handle incoming code in this way. Any code that was +developed outside of the ASF SVN repository must be processed like +this, even if the external developer is an ASF committer.

+
+
+ Process +
    +
  1. +IP Clearance processing must be executed either by an Officer +or a Member of the ASF. If you are not an Officer or a Member, +please contact your project chair who will find an appropriate +volunteer. Incubator karma is also required. Please request +karma from the incubator pmc if you do not have it. +
    2. +
  2. +(Optional) Commit an outline form, +filling those parts which can be (at this stage). +
    3. +
  3. +A software grant must be provided to the ASF. This grant can either be +done by the ASF Corporate CLA (via Schedule B) or the traditional +License Agreement. Acceptable methods of sending the grant to the +ASF includes: +
      +
    • snail-mail to the ASF office and/or ASF officer
      • +
    • FAXing to the ASF office and/or an ASF officer
      • +
    • Emailing the scanned document to secretary@apache.org + and legal-archive@apache.org.
      • +
    +
    4. +
  4. +Receipt of the software grant form must be acknowledged +by an Officer of the ASF by recording in the correct file (grants.txt for a License Grant +or cclas.txt for a Corporate CLA). In most normal circumstances, +the officer should be the ASF Secretary, who must be provided a copy of +the grant or CCLA in any case (if not originally sent or Emailed +to him). +
    5. +
  5. +Note: the grant form must be acknowledged +before continuing. If the source is referenced by checksum in the grant, +commit the canonical tarball for the donated code into the incubator +drop area together with a checksum and a detached signature. This will +ensure that apache has a legal record of the grant. +
    6. +
  6. +Complete and commit the completed form. +
    7. +
  7. +Post a message to general@incubator prefixed [IP CLEARANCE] asking for +clearance to be checked. Sign off is by lazy consensus so wait at least +72 hours for a -1. +
    8. +
  8. +Post a [RESULT] to close the thread and let the project know that the +code has been cleared for import. +
    9. +
+
+
+ Filling The Form +

What to do to set it up:

+
    +
  • copy this file and re-name it according to +incubator/site-author/ip-clearance/${project-codebase}.html
    • +
  • add a row to the table at +incubator/site-author/ip-clearance/index.html
    • +
  • make a snapshot of the source code available for review
    • +
+

This file should not last long in place before it is moved to the +successful incubation area. The sole purpose is to ensure that IP is +cleared so that the codebase can be merged into the ASF SVN.

+

For this file:

+
    +
  • substitute the XYZ name with the real one
    • +
  • fill in the description
    • +
  • fill in the work items
    • +
  • remove this notice
    • +
  • set a proper "title" element for the html page
    • +
+

When a work item is done, place the date in the supplied space.

+

On the first edit of this file, please delete this notice.

+
+ 
-----8-<---- cut here -------8-<---- cut here -------8-<---- cut here-------8-<----
+
+
+ XYZ Codebase Intellectual Property (IP) Clearance Status +
+
+ Description +

Describe the incoming codebase, including whether it is a large set +of patches, new functional modules, etc.

+
+
+ Project info + + + +

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

+
+ Identify the codebase + + + + + + + + + +
dateitem
....-..-..If applicable, make sure that any associated name does not + already exist and is not already trademarked for an existing software + product.
+

+MD5 or SHA1 sum for donated software: (Note versioned software used to calculate sum in parentheses). +

+ +
+ Verify distribution rights +

+Corporations and individuals holding existing distribution rights: +

+
    +
  • +For individuals, use the name as recorded on the committers page +
    • +
+ + + + + + + + + + + + + + + + + + + + + +
dateitem
....-..-..Check that all active committers have a signed CLA on + record.
....-..-..Remind 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.
....-..-..Check 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.
....-..-..Check 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: +

+
    +
  • The VOTE thread accepting the donation may happen either +before or after IP clearance. Adoption by lazy concensus is acceptable but +not recommended.
    • +
+
+
Determine Export Status +

TODO

+
+
+ + Property changes on: site-author/guides/ip-clearance.xml ___________________________________________________________________ Name: svn:eol-style + native Name: svn:keywords + author date id Index: site-author/ip-clearance/ip-clearance-template.xml =================================================================== --- site-author/ip-clearance/ip-clearance-template.xml (revision 650674) +++ site-author/ip-clearance/ip-clearance-template.xml (revision 650675) @@ -7,234 +7,102 @@
Codebase IP Clearance TEMPLATE 
-----8-<---- cut here -------8-<---- cut here -------8-<---- cut here-------8-<----
-
- Preamble -

This document is the template for recording IP clearance on new -codebases. Please store the completed document in this Incubator -repository using a filename that reflects your project.

-

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 project, but -still represents a substantial contribution that was not developed -within the ASF's source control system. 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. 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.

-

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, everything is done.

-

All PMCs must handle incoming code in this way. Any code that was -developed outside of the ASF SVN repository must be processed like -this, even if the external developer is an ASF committer.

-
-
- Process -
    -
  1. -IP Clearance processing must be executed either by an Officer -or a Member of the ASF. If you are not an Officer or a Member, -please contact your project chair who will find an appropriate -volunteer. Incubator karma is also required. Please request -karma from the incubator pmc if you do not have it. -
    2. -
  2. -(Optional) Commit an outline form, -filling those parts which can be (at this stage). -
    3. -
  3. -A software grant must be provided to the ASF. This grant can either be -done by the ASF Corporate CLA (via Schedule B) or the traditional -License Agreement. Acceptable methods of sending the grant to the -ASF includes: -
      -
    • snail-mail to the ASF office and/or ASF officer
      • -
    • FAXing to the ASF office and/or an ASF officer
      • -
    • Emailing the scanned document to secretary@apache.org - and legal-archive@apache.org.
      • -
    -
    4. -
  4. -Receipt of the software grant form must be acknowledged -by an Officer of the ASF by recording in the correct file (grants.txt for a License Grant -or cclas.txt for a Corporate CLA). In most normal circumstances, -the officer should be the ASF Secretary, who must be provided a copy of -the grant or CCLA in any case (if not originally sent or Emailed -to him). -
    5. -
  5. -Note: the grant form must be acknowledged -before continuing. If the source is referenced by checksum in the grant, -commit the canonical tarball for the donated code into the incubator -drop area together with a checksum and a detached signature. This will -ensure that apache has a legal record of the grant. -
    6. -
  6. -Complete and commit the completed form. -
    7. -
  7. -Post a message to general@incubator prefixed [IP CLEARANCE] asking for -clearance to be checked. Sign off is by lazy consensus so wait at least -72 hours for a -1. -
    8. -
  8. -Post a [RESULT] to close the thread and let the project know that the -code has been cleared for import. -
    9. -
-
Filling The Form -

What to do to set it up:

+

+ This is the short version for those who are familiar with the process. + Others should read the guide first. +

-

This file should not last long in place before it is moved to the -successful incubation area. The sole purpose is to ensure that IP is -cleared so that the codebase can be merged into the ASF SVN.

-

For this file:

- -

When a work item is done, place the date in the supplied space.

On the first edit of this file, please delete this notice.

-----8-<---- cut here -------8-<---- cut here -------8-<---- cut here-------8-<----
- XYZ Codebase Intellectual Property (IP) Clearance Status + XYZ Codebase Intellectual Property Clearance + +
+ Date +

1 Jan 2000

-
- Description -

Describe the incoming codebase, including whether it is a large set -of patches, new functional modules, etc.

+ +
+ Identify Contribution + + + + + + + + + + +
NameSum
FooBarMD5 1234567890
-
- Project info + +
+ Identify Contributors
    -
  • Which PMC will be responsible for the code
    • +
  • ACME CORP
+
+ +
+ Location Of Initial Import +

http://issues.apache.org/JIRA/XYZ

+
+ +
+ Destination Project +

Apache FOO

+
+ +
Agreements +

Import is covered by the following agreements:

    -
  • Into which existing project/module
    • +
  • Software grants named: +
      +
    • FILENAME OF SOFTWARE GRANT
      • +
    +
    • +
  • Individual CLAs for: +
      +
    • CONTRIBUTOR NAME
      • +
    +
    • +
  • Corporate CLAs for: +
      +
    • CORPORATION NAME
      • +
    +
-
    -
  • Officer or member managing donation:
    • -
+
+ +
Cryptography

- Completed tasks are shown by the completion date (YYYY-MM-dd). + This code requires a ECCN. + ASF Export Classifications has been updated + and the required notification sent.

-
- Identify the codebase - - - - - - - - - -
dateitem
....-..-..If applicable, make sure that any associated name does not - already exist and is not already trademarked for an existing software - product.
-

-MD5 or SHA1 sum for donated software: (Note versioned software used to calculate sum in parentheses). -

- -
- Verify distribution rights -

-Corporations and individuals holding existing distribution rights: -

-
    -
  • -For individuals, use the name as recorded on the committers page -
    • -
- - - - - - - - - - - - - - - - - - - - - -
dateitem
....-..-..Check that all active committers have a signed CLA on - record.
....-..-..Remind 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.
....-..-..Check 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.
....-..-..Check 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: -

-
    -
  • The VOTE thread accepting the donation may happen either -before or after IP clearance. Adoption by lazy concensus is acceptable but -not recommended.
    • -
-
+

+ OR +

+

This code does not require a + ECCN.

+ +