The license shall be chosen accordingly:

Other licenses can be used after consultation with and approval by the Product Owner and CEO.

Example of License Header Follows:

Standard License Header for Apache 2.0: Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

NuNet follows and promotes Apache Software Foundation's Code of Conduct and Etiquette guidelines. Please read and follow them when contributing to NuNet and interacting in our spaces.

We have standardized on the code of conduct that governs how we interact with contributors to our open source projects. All NuNet contributors are required to follow the code in order to be part of the community. NuNet reserves a right to ban individuals who do not follow the code of conduct. Please find details via the following link Code of Conduct.

The above text shall be included in each repository in file CODE_OF_CONDUCT.md.

NuNet framework consists of three component classes:

1. Core Platform Components

Platform code that has to be used by all stakeholders of the framework in order to use the platform and cannot be duplicated – therefore have to be shared. As the name indicates, the code that constitutes these components makes the platform a platform. These include, but not limited to communication protocols, application programming interfaces (APIs), software development kits (SDKs), encryption mechanisms, blockchain integrations (smart contracts), transaction settling mechanisms (NTX token), network tokenomics, device management service (DMS), etc.

2. Non-core Platform Components

Components and code that are still needed for the platform to function, but the ones that can be duplicated / operate concurrently within the platform and therefore the development of these components can be decentralised. These components include network operating agents (as called in the original Whitepaper), which will provide capabilities and AI services for managing the network, reputation systems, oracles (for compute verification), developer tooling (development and debugging frameworks for building on NuNet) etc. Currently (and in the foreseeable future) NuNet is building these components as they are needed for the platform to function properly. The long term goal, however, is to to build the core platform components (most importantly APIs, SDKs and blockchain integrations) in a way that enables community developers to compete in developing (and possibly monetizing via NuNet network tokenomics) non-core platform components and run them concurrently on the platform – allowing users to choose their preferred network operating agents, reputation systems and oracles.

3. Use-case applications and IP protected components

As per the platform-as-a-service business model, NuNet should be able to execute any third party application – which is actually the definition of the platform. The medium-to-long term goal of platform development is to reach the tipping point, when third parties are able to successfully execute the IT part of their business models on NuNet platform without NuNet’s development team contribution (save for support services). However, due to reasons explained in the section on our use-case based platform development model, NuNet core developers team is building use-case applications in order to reach that tipping point. Nevertheless, these components should be properly licensed and separated from the core platform code, which will become more important when we will attract different business usages and parties.

One of NuNet’s core values is Open Source code for the community and business use. Our business model combines the open source software world with the business and commercial applications world and enables both communities to interact via open APIs and protocols. Much of the corporate, development team and business model structuring of the first 14 months of NuNet development was related to identifying and purifying the structure of NuNet framework and aligning its technical, business and legal aspects. The main reason for this work is the long term goal of NuNet to evolve into the framework and ecosystem aligning the interaction between a few types of stakeholders (see description of the use-case based platform development model above) – in the future allowing independent developers and businesses to build their solutions on the NuNet platform – so developing into a decentralized platform-as-a-service solution.

NuNet will be using three licensing regimes in order to establish proper interaction across the boundaries between these components in technical, legal and business terms. The idea behind this structure was being considered from the start, formalized and clarified at the end of 2022. Based on this, in the beginning of 2023 we chose actual licenses to be used for each regime, assigned that to the current code and developed and approved the procedure of code licensing for the subsequent development of the platform. Based on further evaluation, in 2024, we updated the licensing approach and decided to exclusively use Apache License 2.0 in the first regime. This decision was made to ensure flexibility, promote widespread commercial use, and simplify legal compliance while maintaining openness in the development process. The Apache License 2.0 allows for both internal and external contributions without the restrictive requirements of copyleft licenses, aligning with our goals for decentralized platform development and global collaboration.

Each newly created repository in NuNet GitLab project is assigned licensing regime as per the approved policy, assigned concrete open source licence and committed to the root of the repository so that each repository is identified by a distinct LICENSE.md file, and in the last stanza of the Readme.md, titled “License” following this format: PROJECT_NAME is licensed under the LICENSE_NAME (linked to LICENSE).