Difference between revisions of "Compliance"
Jump to navigation
Jump to search
(This changes nothing) |
m (adds references section) |
||
| Line 5: | Line 5: | ||
== Methods == | == Methods == | ||
| − | The Software Freedom Law Center says <ref>https://www.softwarefreedom.org/resources/2014/SFLC-Guide_to_GPL_Compliance_2d_ed.html</ref><-</blockquote> | + | The Software Freedom Law Center says <ref>https://www.softwarefreedom.org/resources/2014/SFLC-Guide_to_GPL_Compliance_2d_ed.html</ref><-</blockquote> |
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). | 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). | ||
| − | The Software Freedom Law Center says <ref>https://www.softwarefreedom.org/resources/2014/SFLC-Guide_to_GPL_Compliance_2d_ed.html</ref><</blockquote> | + | The Software Freedom Law Center says <ref>https://www.softwarefreedom.org/resources/2014/SFLC-Guide_to_GPL_Compliance_2d_ed.html</ref><</blockquote> |
== Enforcement == | == Enforcement == | ||
