COPYRIGHT SYMBOL COPY AND PASTE 1976 CODE

Importing third-party source code that claims to be licensed under Apache Version 2 AND that third-party source code also embeds some other third-party source code under a different type of licensing Modifications within ONAP would cause a fork, and would make it more difficult to maintain over time. In that case, licensing would be governed by the other community. It would be best to make any modifications within the scope of that other community, and only do an integration within ONAP. It is assumed that such binaries are produced by a different upstream community.

COPYRIGHT SYMBOL COPY AND PASTE 1976 SOFTWARE

Modify and compile third-party source code into binaries, reference these binaries from our code and include them in ONAP software distribution

binaries are not limited in type of code, but should also include images, sounds, fonts and other non-text file types and file types that do not actually result in code execution.

binaries that are not linked/referenced means they execute in separate contexts, in separate processes, or on distinct physical or virtual processors.

COPYRIGHT SYMBOL COPY AND PASTE 1976 LICENSE

Usage of third-party binaries that are linked/referenced statically or dynamically within ONAP are subject to Apache 2 license requirement or Governing Board approval (for non Apache 2 License).License compliance requirements for such elements must be observed with each ONAP distribution (including supply of source code when required).ONAP should track use of such unmodified executable binaries (hence the table down below for each project).

Usage of third-party unmodified executable binaries that are not linked/referenced statically or dynamically within ONAP code and included in ONAP software distribution is permitted.Standalone elements (unmodified third party elements) The name of the publication and it's publisher.

URL location of the source code files or web article.

All snippets reuse must also be documented with an adjacent comment in the code: Copy/paste third-party source code directly into our code files and compile it into ONAP binariesДЄs ONAP is recompiling the code, the third-party source code must be Apache Version 2 (or an exception must approved by Governing Board). To be more specific, the sections below illustrate a couple of different situations ONAP Community may be facing. Linux Foundation operates the scan on ONAP source code and is using FossologyВ to look at disclosure of License. In those cases, please notify the Release Manager so we can document the licensing and the reasoning in the tables below. It is permissible to use such third-party unmodified binariesВ without Governing Board approval (even if it is not licensed under Apache 2). In addition to source code contributions, we may need to incorporate third-party unmodified binaries. In the case you would like to bring in third-party source code, that is not under Apache 2, we need to ask for a Governing Board exception. Inbound represents all source code that goes into ONAP Software Configuration Management (Gerrit) independently of the origin (either ONAP community member or code from third-party source).

Interpretation of the rulesДЄll inbound source code contributionsВ and documentationВ must be licensed under Apache 2 LicenseВ or Creative Commons Attribution 4.0 International License. All documentation will be contributed to and made available by the Project under the Creative Commons Attribution 4.0 International License (available at ).

Copyright symbol copy and paste 1976