65
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 02 Apr 2024
65 points (71.5% liked)
Open Source
31291 readers
489 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
https://www.gnu.org/philosophy/open-source-misses-the-point.en.html
Am I missing something, ~~gnu~~ gpl is a licence, Foss a philosophy, is ~~gnu~~ gpl licence Foss? And if so why are so many people saying charging for software isn't Foss when Richard stalman himself makes the point "This is a matter of freedom, not price, so think of “free speech,” not “free beer.”"
Sorry if I got this wrong I am generally confused by this hole thing.
GNU is not a license, it's a project, one that practically spearheaded the whole FOSS movement back in the 80s. The programs that were part of the GNU project were licenced under the GNU General Public License (GPL), which was originally written by Richard Stallman, and evolved over time to its current version, GPLv3 (now backed by the Free Software Foundation). So the "GPL" is the actual license that can be applied to any program, should the developer choose to do so (so it's not limited just to the GNU project).
All GPL licenced programs are considered to be FOSS. However, FOSS can also imply other licenses such as MIT, LGPL, Apache etc. Most of them are kinda similar, but the way but differ slightly on how permissive/restrictive it is when it comes to modifications and derivatives.
As you said, it's not about the price at all, the "free" means freedom. Specifically, the GPL explicitly states that you may charge money for the software. Other free software licences also generally state something similar.
The confusion regarding selling is best explained by the FSF:
https://www.gnu.org/philosophy/selling.html
Also, just to be clear, opensource =/= FOSS. Opensource just means that the source code is available, FOSS however implies that you're free to modify and redistribute the program (+ some other freedoms/restrictions as per the specific license used).
Incorrect. "Open Source" also means that you are free to modify and redistribute the software.
If the source code is merely available but not free to modify and/or redistribute, then it is called source-available software.
Not necessarily true - that right to modify/redistribute depends on the exact license being applied. For example, the Open Watcom Public License claims to be an "open source" license, but it actually doesn't allow making modifications. This is also why we specifically have the terms "free software" or "FOSS" which imply they you are indeed allowed to modify and redistribute.
I would recommend reading this: https://www.gnu.org/philosophy/open-source-misses-the-point.en.html
If you don't have the right to modify and redistribute it (and to do so commercially) then it does not meet the definitions of free software or open source.
The Sybase Open Watcom Public License does allow making modifications, and distributing modified versions. The reason why the FSF has not approved it is that it requires you to publish source code even if you only wanted to run your modified version yourself and didn't actually want to distribute anything to anyone. (The Watcom license is one of the few licenses which is approved by OSI but not FSF. You can see the other licenses which are approved by one but not the other by sorting this table.)
The FSF's own AGPL license is somewhat similar, but it only imposes the requirement if you run the software for someone else over a network. (Neither of these requirements are likely to be enforceable by copyright law, as I explained in my comment about the AGPL in the thread which this thread is about...)
I would recommend that you re-read that, because it actually explains that the two terms refer to essentially the same category of software licenses (while it advocates for using the term free software to emphasize the philosophical aspects of those licenses).
Thank you for clearing this up, the comments in the linked post where having me question myself
There's nothing wrong with charging for your FOSS. You can't, however, force anybody who gets it from you to also charge the people they end up distributing it to like some sort of Ponzi scheme. The transactional relationship between you, your software, and another party ends at the first level.
This is what I had thought, where I was confused was the vast amount of comments in the linked post stating flatly that charging for software went against foss