OW2 Intellectual Property Policy Primer
Intellectual Property management is a process used to handle IP issues.
Project must take care of their dependencies, in order to remain license compatible.
Each dependency of a project has its own license, project members have to make sure that they use the dependencies (linking, distribution, ...) within the bounds of the license.
For example, a LGPL3 project cannot depends on a
Another example: a LGPL project has the right to depends on an library.
Project also have to manage code property, ensuring that its codebase remains clean from copyrighted, patented contributions.
- The code you commit in the project belongs to you (Author)
The OW2 Consortium do not own any copyright or claim code ownership on project's contributions.
OW2 only provides the infrastructure that hosts the code.
By default, theapplies on contributions.
- Each project is responsible to handle IP cleanness in its own way
- OW2 only provides guidance
All committers of a project should (must ?) have signed the.
Contributor License Agreement
- CLA for individual contributor
- CCLA for contributions coming from employee during their work hours
- State that the contributed code is their own property
- May state that the contributed code will belongs to someone else (some entity behind the project)
All project's source file (non-generated) must have a license header at the top.
The license header depends on the license selected by the project.
Software Grant Agreement
A Software Grant Agreement (SGA) may be required when a full working code base (like a sub-project, or a significant component) is willing to be contributed to a project.