Editing Open Source Comes to Campus/Curriculum/Licensing

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 13: Line 13:
 
== Permissive free licenses ==
 
== Permissive free licenses ==
  
Now, to the other end of the spectrum: Permissive free licenses. This family of licenses includes such stars as the MIT license, the BSD license family, more joking selections like the WTFPL, and even public domain releases like Creative Commons Zero tool. These licenses put very few, or no, restrictions on people who receive copies under their terms. Many of them include a disclaimer that the program has no warranty, to help protect the distributor (or the programmers), but some do not. Others release the program into the public domain if possible, but some jurisdictions make that nearly impossible, so most of them have a backup clause that makes it practically public domain anyway.
+
Now, to the other end of the spectrum: Permissive free licenses. This family of licenses includes such stars as the MIT license, the BSD license family, more joking selections like the WTFPL, and even cultural licenses like the Creative Commons Zero license. These licenses put very few, or no, restrictions on people who receive copies under their terms. Many of them include a disclaimer that the program has no warranty, to help protect the distributor (or the programmers), but some do not. Others release the program into the public domain if possible, but some jurisdictions make that nearly impossible, so most of them have a backup clause that makes it practically public domain anyway.
  
The Free Software Foundation publishes guidelines on licensing for free projects to help programmers understand the risks and benefits of each. They suggest that if you must use a permissive license, you should use the Apache 2.0 license. FSF recommends this license for permissively-licensed projects because it includes a patent grant and other patent-related clauses—so that contributors to the project are contributing any rights they have, allowing downstream reusers to know that contributors are not withholding these rights and they intend for the software to be truly free to use. (It doesn't eliminate the possibility of third-party patents, but no license does.)
+
The Free Software Foundation, who publish guidelines on licensing for free projects to help programmers understand the risks and benefits of each, suggest that, if you must use a permissive license, you should use the Apache 2.0 license. It includes a patent protection clause, and as such is better from their perspective, because it ensures that the project and programmers will be somewhat safer from litigation.
  
 
== Copyleft licenses ==
 
== Copyleft licenses ==

Please note that all contributions to OpenHatch wiki are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) (see OpenHatch wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)