Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Text edits for clarity

...

For most open source development, you or your employer will own all the rights to the code, and will be responsible for them. The Nordix Foundation allows you to contribute code to the foundation directly. This means that when you copyright the code instead of using your own name you use Nordix Foundation as the copyright holder to indicate that the rights to the code have been assigned to Nordix.  This requires a specific agreement clause to be signed by you, or your employer, which has language that ensures contributions done in this way are done in the best interest of the open source community and foundation.  Do notes if you wish to make contributions and assign the copyright to Nordic the code needs to be done on the Nordix foundation infrastructurethings like deciding what open source license to apply to the code. As an optional alternative, the Nordix Foundation offers a way for you to assign copyright for your contributions to the foundation, instead of keeping that responsibility yourself. Copyright assignment isn't automatic, so if you ever want it, you or your employer will need to sign a specific agreement with the Nordix Foundation, which includes terms to ensure that the foundation will only use the contributions you make in a way that's beneficial for the open source community. After the agreement is signed, any new copyright headers you add should  list the Nordix Foundation as the copyright holder instead of your name or your company's name. The copyright assignment agreement with the Nordix Foundation only applies to development you do on the Nordix Foundation infrastructure, it doesn't have any effect on code you develop elsewhere.

Copyright (C) 2018, Nordix Foundation

When you edit an open source file that already has a copyright header already , you should not remove the original header , nor or change the licence information that you have accepted by choosing to edit someone else file.  In license information. Adding some lines of your own code to a file doesn't mean you own the entire file, so it doesn't give you the right to change the license on the entire file. In this case you can either;

...

It is important in open source, collaborative development, that when we create code we can trace to be able to trace who created code, and who added what to the file files, and that we agree on the terms and conditions of use.

Open Source

...

Licenses

There are many open source licenses that can be used to share the software you produce.  Choosing an open source licence license has an impact on how others can use or work with your code and the terms and responsibilities that are associated with it.  The Open Source Initiative, OSI (https://opensource.org (OSI), is the body that maintains what we mean when we say open sourcean independent, non-profit body that reviews and approves licenses to ensure they meet community standards for open source, and is widely accepted as an authority on what it means to call software "open source".  The OSI states that "We are the stewards of the Open Source Definition (OSD) and the community-recognized body for reviewing and approving licenses as OSD-conformant." which is commonly understood to be the metric by which we define open source.

The OSI maintains a list of licenses that can be used it has approved for open source development, most developers . Developers today will often come across GPL (used for Free Software Foundation projects, Linux Foundation projects), Eclipse (used for Eclipse) and Apache (used for Apache Software Foundation projects, OpenStack) licenses.  When you see a license header you can visit the OSI web pages to learn more about them and what your rights are when using and contributing to the code.

Nordix

...

Foundation licenses

We don't specify a specific licence require projects in the Nordix Foundation to use one specific license, though we do require our projects to use licenses that have been approved by the OSI.  We expect that many of people in our community will be working with other communities and foundations, such as LinuxFoundation Linux Foundation and OpenStack Foundation where they very clearly specify the licence to be used in those projects.  It is important that a project uses a consistent licence policy that maintains licence compatibility, who do require one specific license for their projects. Giving our community the flexibility to choose between open source licenses is important, so our projects can maintain license compatibility with other projects.

If you are starting a new project in Nordix you can choose a popular OSI licence license to use.  You need to specify that when you are creating your project and it will need to be approved by the technical committeeTechnical Committee.  If you are not sure about the right licence for you, what license to choose, you can reach out and ask on discuss@nordicon discuss@lists.nordix.org as it I . In general, it is best to choose a licence an open source license that is compatible with any other projects you may be working closely withthat are closely related to your project.