Deployment Admin is an implementation of chapter 114 of the OSGi R4.1 specification. It's a module (bundle) that is responsible for installing and updating deployment packages. These contain bundles and other installable artifacts.
Source available at FELIX-452
Completed tasks are shown by the completion date (YYYY-MM-dd).
|n/a||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: f090af4de098577e8d2b0023b8b8746b (md5).
|2007-11-26||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.|
|2007-12-17||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: Apache Felix Deployment Admin
Corporations and individuals holding existing distribution rights:
|2007-11-26||Check that all active committers have a signed CLA on record.|
|2007-11-26||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.|
|n/a||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.|
|n/a||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.