Difference between revisions of "Compliance"
Jump to navigation
Jump to search
(adds Termination section and Complete and Corre) |
(Adds Methods section) |
||
| Line 3: | Line 3: | ||
== Compliance between Licenses == | == Compliance between Licenses == | ||
The compliance drama is not just one between proprietary and free software. There is an over abundance of software licenses, and many of the so-called 'open source' or 'permissive' licenses are incompatible with each other. So, compliance is actually about what code you have, what license is that code under, and are you compliant with all the terms of every license that you are a party to. | The compliance drama is not just one between proprietary and free software. There is an over abundance of software licenses, and many of the so-called 'open source' or 'permissive' licenses are incompatible with each other. So, compliance is actually about what code you have, what license is that code under, and are you compliant with all the terms of every license that you are a party to. | ||
| + | |||
| + | == Methods == | ||
| + | |||
| + | |||
| + | You can generally do this at the 'file scope' or the 'project scope' (also called "centralized notice").<ref>http://softwarefreedom.org/resources/2012/ManagingCopyrightInformation.html</ref> We believe project scope is the best way to do this, in conjunction with good [[Version Control]] (and also contributor [[assignment]] agreements). | ||
== Enforcement == | == Enforcement == | ||
