Sling Journal-based Content Distribution - Intellectual Property (IP) Clearance Status
Description
The Sling Journal-based Content Distribution module provides:
- an implementation of SCD agents on top of a journal & Journal messaging API
- an implementation of the Journal messaging API on Apache Kafka
- a definition of the messages exchanged by the SCD agents
- integration tests for the journal distribution modules
Project info
- Apache Sling PMC will be responsible for the code
- This contribution will be pushed to a new GitBox repo.
- Officer or member managing donation: Robert Munteanu (rombert@apache.org)
Completed tasks are shown by the completion date (YYYY-MM-dd).
Identify the codebase
| date | item |
|---|---|
| 2018-04-02 | source code is attached to the SLING-8326 ticket as org.apache.sling.distribution.journal.tar.gz, org.apache.sling.distribution.journal.kafka.tar.gz, org.apache.sling.distribution.journal.messages.tar.gz, and org.apache.sling.distribution.journal.it.tar.gz. |
SHA1 sum for donated software:
SHA1(org.apache.sling.distribution.journal.it.tar.gz) = bea916c7428dabf6dc66048087dbc3a4e0a7c610
SHA1(org.apache.sling.distribution.journal.kafka.tar.gz) = 9be2740511619bc91832c24f00e093ce61f1f128
SHA1(org.apache.sling.distribution.journal.messages.tar.gz) = c75bd3feafd335b23c169e57bb8b298ab25aed76
SHA1(org.apache.sling.distribution.journal.tar.gz) = b49dbcd182765b2351b9204df095a64ae2beb598
Copyright
| date | item |
|---|---|
| 2018-04-04 | 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.
Software grant registered as private/documents/grants/adobe-sling-journal.pdf on 2018-04-04. |
| 2018-04-04 | Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright: done, all source code files have the ASF header in the supplied archive. |
Identify name recorded for software grant: Adobe Systems
Verify distribution rights
Corporations and individuals holding existing distribution rights:
- Adobe Systems
| date | item |
|---|---|
| 2018-04-08 | Check that all active committers have a signed CLA on record. |
| 2018-04-08 | 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. |
| 2018-04-04 | 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. |
| 2018-04-04 | 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:
- Vote on dev@sling: Message-ID: <CA+joGu_X7T9DP+BjQ5D2JNaNG8_x5Po=SZ_wNuF8m_73cOQOSw@mail.gmail.com>
- Vote result on dev@sling: Message-ID: <CA+joGu_zLrjJrfg5vkt9tm3ONvU37aF9f5K2C-RNPXKiwvyBqg@mail.gmail.com>
- Lazy consensus vote on general@incubator: <49efb401496dcd677c6eac6bfededd0161c6c738.camel@apache.org>
- Lazy consensus vote result on general@incubator: <cf49a02c71cee9d1ba78b6488d741d6acf2fa366.camel@apache.org%gt;