The Sling replication module allows resources to be replicated between Sling instances.
Completed tasks are shown by the completion date (YYYY-MM-dd).
|2013-11-05||source code provided as a patch on SLING-3223 (https://issues.apache.org/jira/secure/attachment/12612201/SLING-3223.patch).|
MD5 or SHA1 sum for donated software: SHA1(SLING-3223.patch.txt)= ee628f4556c71c19fa09ae4e58fc7b32182da11b.
|2013-11-27||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.|
|2013-11-15||Check 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: adobe-sling-replication-grant
Corporations and individuals holding existing distribution rights:
|2013-11-21||Check that all active committers have a signed CLA on record.|
|2013-11-22||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.|
|2013-11-22||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.|
|2013-11-21||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.