David Sean Taylor asked:
> I am checking into Jetspeed CVS a set of patches that I wrote as a work
> for hire, paid for by Gluecode Inc
> The Software Grant from Gluecode has been received by the ASF via Geir
> Magnusson Jr as a tiff, with hardcopy coming this weekend.
> Are there any other steps we (the Portals PMC) should take to register
> this information?
We have drafted a short checklist using the cwiki doc type currently used
for other Incubator documents. There were a couple of minor revisions to
the first draft, none (so far) on the second.
Since "any code that was developed outside of the ASF SVN/CVS repository
must be processed like this, even if the external developer is an ASF
committer", we have tried to make this simple and plainless. More than half
of short file is commentary. The actual checklist, itself, basically asks:
- What contribution does this cover?
- Have we a Software Grant?
- Have we a CLA for each contributor?
- Have we reminded contributors to acquire a Corporate CLA if necessary?
- Is the code under the Apache License?
- Are all dependencies under a compatible license?
Attached is a copy for your usage and review (remove the .txt extension that
is only present to force the attachment type to be something ezmlm won't
filter out). I happened to have it in my buffer. Will commit to CVS as
soon as I can tunnel back into my development server.
--- Noel
!!! X Codebase IP Clearance TEMPLATE
This document is the template for recording IP clearance on new codebases.
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 use with 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/CVS repository must be processed like
this, even if the external developer is an ASF committer.
What to do to set it up:
* copy this file and name it <name>.cwiki
* add a section in incubator/site/projects/index.xml
* 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 CVS.
For this file (syntax reference is at http://xml.apache.org/forrest/wiki-sample.html):
* substitute the XYZ name with the real one
* fill in the description
* fill in the work items
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 IP Clearance Status
!!! Description
Describe the incoming codebase, including whether it is a large set of
patches, new functional modules, etc.
!!! Project info
* Which PMC will be responsible for the code
* Into which existing project/module
'' Completed tasks are shown by the completion date (YYYY-MM-dd). ''
! Identify the codebase
|| date || item
| ....-..-.. | If applicable, make sure that any associated name does not already
exist and check www.nameprotect.com to be sure that the name is not already
trademarked for an existing software product.
! Copyright
|| date || item
| ....-..-.. | Check 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.
| ....-..-.. | Check and make sure that the files that have been donated have been
updated to reflect the new ASF copyright.
! Verify distribution rights
|| date || item
| ....-..-.. | 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 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
* Has the receiving PMC voted to accept it?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
