--- www/philosophy/free-sw.html 2016/08/20 14:28:57 1.148 +++ www/philosophy/free-sw.html 2019/03/20 10:56:16 1.164 @@ -1,8 +1,13 @@ - +
++ ++Have a question about free software licensing not answered here? +See our other licensing resources, +and if necessary contact the FSF Compliance Lab +at licensing@fsf.org.
+“Free software” means software that respects users' @@ -49,19 +70,21 @@ an instrument of unjust power.
+The four essential freedoms
+A program is free software if the program's users have the -four essential freedoms: +four essential freedoms: [1]
-+
- The freedom to run the program as you wish, for any purpose (freedom 0).
- The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this.
-- The freedom to redistribute copies so you can help your neighbor +
- The freedom to redistribute copies so you can help others (freedom 2).
- The freedom to distribute copies of your modified versions @@ -85,24 +108,31 @@ are free. However, if we plan to modify A so that it doesn't use B, only A needs to be free; B is not pertinent to that plan. -
The rest of this page clarifies certain points about what makes -specific freedoms adequate or not.
- -Freedom to distribute (freedoms 2 and 3) means you are free to -redistribute copies, either with or without modifications, either -gratis or charging a fee for distribution, to -anyone anywhere. Being free to do these -things means (among other things) that you do not have to ask or pay -for permission to do so. +
+“Free software” does not mean “noncommercial”. A free +program must be available for commercial use, commercial development, +and commercial distribution. Commercial development of free software +is no longer unusual; such free commercial software is very important. +You may have paid money to get copies of free software, or you may have +obtained copies at no charge. But regardless of how you got your copies, +you always have the freedom to copy and change the software, even to +sell copies.
-You should also have the freedom to make modifications and use them -privately in your own work or play, without even mentioning that they -exist. If you do publish your changes, you should not be required to -notify anyone in particular, or in any particular way. +A free program must offer the four freedoms to any user that obtains a +copy of the software, provided the user has complied thus far with the +conditions of the free license covering the software. Putting some of +the freedoms off limits to some users, or requiring that users pay, in +money or in kind, to exercise them, is tantamount to not granting the +freedoms in question, and thus renders the program nonfree.
+The rest of this page clarifies certain points about what makes +specific freedoms adequate or not.
+ +The freedom to run the program as you wish
+The freedom to run the program means the freedom for any kind of person or organization to use it on any kind of computer system, for any kind of @@ -116,20 +146,12 @@
The freedom to run the program as you wish means that you are not -forbidden or stopped from doing so. It has nothing to do with what -functionality the program has, or whether it is useful for what you -want to do.
+forbidden or stopped from making it run. This has nothing to do with what +functionality the program has, whether it is technically capable of +functioning in any given environment, or whether it is useful for any +particular computing activity. --The freedom to redistribute copies must include binary or executable -forms of the program, as well as source code, for both modified and -unmodified versions. (Distributing programs in runnable form is necessary -for conveniently installable free operating systems.) It is OK if there -is no way to produce a binary or executable form for a certain program -(since some languages don't support that feature), but you must have the -freedom to redistribute such forms should you find or develop a way to -make them. -
+The freedom to study the source code and make changes
In order for freedoms 1 and 3 (the freedom to make changes and the @@ -160,6 +182,29 @@
+Whether a change constitutes an improvement is a subjective matter. +If your right to modify a program is limited, in substance, to changes that +someone else considers an improvement, that program is not free. +
+ +The freedom to redistribute if you wish: basic requirements
+ +Freedom to distribute (freedoms 2 and 3) means you are free to +redistribute copies, either with or without modifications, either +gratis or charging a fee for distribution, to +anyone anywhere. Being free to do these +things means (among other things) that you do not have to ask or pay +for permission to do so. +
+ ++You should also have the freedom to make modifications and use them +privately in your own work or play, without even mentioning that they +exist. If you do publish your changes, you should not be required to +notify anyone in particular, or in any particular way. +
+ +Freedom 3 includes the freedom to release your modified versions as free software. A free license may also permit other ways of releasing them; in other words, it does not have to be @@ -169,15 +214,20 @@
-In order for these freedoms to be real, they must be permanent and -irrevocable as long as you do nothing wrong; if the developer of the -software has the power to revoke the license, or retroactively add -restrictions to its terms, without your doing anything wrong to give -cause, the software is not free. +The freedom to redistribute copies must include binary or executable +forms of the program, as well as source code, for both modified and +unmodified versions. (Distributing programs in runnable form is necessary +for conveniently installable free operating systems.) It is OK if there +is no way to produce a binary or executable form for a certain program +(since some languages don't support that feature), but you must have the +freedom to redistribute such forms should you find or develop a way to +make them.
+Copyleft
+-However, certain kinds of rules about the manner of distributing free +Certain kinds of rules about the manner of distributing free software are acceptable, when they don't conflict with the central freedoms. For example, copyleft (very simply stated) is the rule that when redistributing the program, @@ -199,25 +249,10 @@ relate to each other.
--“Free software” does not mean “noncommercial”. A free -program must be available for commercial use, commercial development, -and commercial distribution. Commercial development of free software -is no longer unusual; such free commercial software is very important. -You may have paid money to get copies of free software, or you may have -obtained copies at no charge. But regardless of how you got your copies, -you always have the freedom to copy and change the software, even to -sell copies. -
- --Whether a change constitutes an improvement is a subjective matter. -If your right to modify a program is limited, in substance, to changes that -someone else considers an improvement, that program is not free. -
+Rules about packaging and distribution details
-However, rules about how to package a modified version are acceptable, +Rules about how to package a modified version are acceptable, if they don't substantively limit your freedom to release modified versions, or your freedom to make and use modified versions privately. Thus, it is acceptable for the license to require that you change the @@ -249,6 +284,8 @@ facility that allows you to specify the original program's name as an alias for the modified version.
+Export regulations
+Sometimes government export control regulations and trade sanctions can constrain your freedom to distribute copies of @@ -271,6 +308,16 @@ software nonfree.
+Legal considerations
+ ++In order for these freedoms to be real, they must be permanent and +irrevocable as long as you do nothing wrong; if the developer of the +software has the power to revoke the license, or retroactively add +restrictions to its terms, without your doing anything wrong to give +cause, the software is not free. +
+A free license may not require compliance with the license of a nonfree program. Thus, for instance, if a license requires you to @@ -285,6 +332,8 @@ law applies, or where litigation must be done, or both.
+Contract-based licenses
+Most free software licenses are based on copyright, and there are limits on what kinds of requirements can be imposed through copyright. If a @@ -304,6 +353,8 @@ it is nonfree.
+Use the right words when talking about free software
+When talking about free software, it is best to avoid using terms like “give away” or “for free,” because those terms imply that @@ -315,6 +366,8 @@ “free software” into various languages.
+How we interpret these criteria
+Finally, note that criteria such as those stated in this free software definition require careful thought for their interpretation. To decide @@ -329,6 +382,8 @@ it easier to see why certain licenses do or don't qualify.
+Get help with free licenses
+If you are interested in whether a specific license qualifies as a free software license, see our list @@ -383,6 +438,7 @@ word “open” never refers to freedom.
+
Copyright © 1996, 2002, 2004-2007, 2009-2016 +
Copyright © 1996, 2002, 2004-2007, 2009-2019 Free Software Foundation, Inc.
This page is licensed under a Updated: -$Date: 2016/08/20 14:28:57 $ +$Date: 2019/03/20 10:56:16 $
- +
The free software definition presents the criteria for whether a particular software program qualifies as free software. From time to @@ -23,7 +35,16 @@ below for a list of changes that affect the definition of free software.
- + ++“Open source” is something different: it has a very +different philosophy based on different values. Its practical +definition is different too, but nearly all open source programs are +in fact free. We explain the +difference in +Why “Open Source” misses the point of Free Software. +
+