9.7_How_do_you_manage_projects_licenses

How do you manage projects licenses?

    A "license" means here a given version of a given license.

    1) License choice

    Any OSS license recognised and endorsed by the Open Source Initiative may be accepted, as defined by our Intellectual Property Rights Policy (paragraph 1.7). The Board makes the final decision. When accepted, the license should be immediately published on the project's web pages.

    2) License change

    While projects are free to choose their own licenses, any license change requires a Board decision. When accepted, the license change should be immediately published on the project's web pages. 

    3) Board decision guidelines

• Should not arbitrarily ban any OSS business model.
• Should not affect negatively any member's business model (eg. dual-licensing, subscription...).
• Should foster reusability of OW2 components (beware of usage restrictions).
• Should not impede cross-project collaborations.
• Should exercise regulation (eg. prevent appropriation of OSS components, reject a project that is not perceived as truly OSS, act as a "referee" to solve conflicts...).
• Should not allow a license change toward more restrictive usage terms, unless OW2 has strong strategic reasons to do so.