• 1 Post
  • 114 Comments
Joined 4 months ago
cake
Cake day: August 21st, 2024

help-circle





  • well the important distinction is who is bound, right? your examples are all true of open source as well. the main difference between the two concepts is that if i withhold my changes to gpl-licensed code from you, you can sue me for breaching the license. if the software is mit, i am in my full right to deny you access. that’s not what i got from your wording.



  • so, free software is a philosophy. software is judged to be free based on it’s adherence to the philosophy based on what they call the four freedoms: freedom to use, read, modify and share the software without restriction. based on those freedoms are free software licenses that enforce this. the most famous one, the gpl, also says that any modification must adhere to the same freedoms. this is what makes “free software” distinct from “open source”. (see also: “copyleft”)

    the gpl means that you are entitled to receive the source code of any company that runs modified GPL software upon request. note that this does not prevent them from making money on the software, only that you as a (potentially paying) user must be able to get the sources without jumping through extra hoops.

    this matters because all improvements are shared as a matter of course, and all source code can be audited. in theory. in reality this does not always happen, of course, which is why the fsf and similar organizations exist to drive these cases through courts. it matters because it acts as a brake on large actors using community-developed software without reciprocating.