Title: Sling Resource Editor Intellectual Property (IP) Clearance Status

The Sling resource editor allows for editing Sling resources in a browser.

  • Apache Sling PMC will be responsible for the code

  • This contribution will be placed under contrib/explorers

  • Officer or member managing donation: Bertrand Delacretaz (bdelacretaz@apache.org)

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

Identify the codebase

dateitem
2014-10-13source code is attached to the SLING-4001 issue as apache _sling_resource_editor.zip

MD5 or SHA1 sum for donated software: SHA1(apache _sling_resource_editor.zip)= 65dd93cfb932915a232ef576c6580685907449de

Copyright

dateitem
2014-10-13Check 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.
N/ACheck and make sure that the files that have been donated have been updated to reflect the new ASF copyright: will be done once the donation is incorporated in the Sling codebase, before releasing the software.

Identify name recorded for software grant: sandro-boehme-sling-resource-editor.pdf

Verify distribution rights

Corporations and individuals holding existing distribution rights:

  • Sandro Boehme
dateitem
2014-10-13Check that all active committers have a signed CLA on record.
2014-10-13Remind 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.
2014-10-13Check 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.
As per the NOTICE in the source archive, all dependencies have ASF-compatible licenses.
2014-10-13Check 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.
As per the NOTICE in the source archive, all dependencies have ASF-compatible licenses.

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: