False, I suggest you read http://www.gnu.org/philosophy/open-source-misses-the-point.e...
False, I suggest you read http://www.gnu.org/philosophy/open-source-misses-the-point.e...
The two terms describe almost the same category of
software, but they stand for views based on
fundamentally different values.
and “Free software.” “Open source.” If it's the same
software (or nearly so), does it matter which name you
use?
OSI's intent was always to refer to the exact same thing as "free software", just use different language, and thus different arguments in favour of it.http://www.gnu.org/philosophy/categories.html#Non-Copylefted...
If you use "different arguments" than freedom to argue about software freedom, then it's no longer the same movement. The free software movement has always been about ethics. The open source movement has no ethical backing, it values code quality over ethical treatment of users (which is why people talk about "open source DRM implementations" -- since DRM is meant to subjugate users, it cannot be free software. But it can be "open source").
The DRM point you make is nuanced. There can be free DRM implementations -- it would just mean that users could modify the software to remove the DRM. If the DRM is implemented in hardware, like tivoisation, then it is indeed no longer free. I think open source advocates, if they still exist (the open source movement seems dormant because it has "won"), might consider that to be open source. Stallman certainly thinks they would:
However: the GPL2 says that you can impose no restrictions on what what people can implement with free software so long as they it is only redistributed as free software, so it seems to me that while DRM'ed software is not free, DRM software itself could be free. Hey, if a DRM scheme could be designed to ensure software freedom, it might even be embraced; we already have GPL clickwrap license clicks which a narrow reading of the GPL might suggest you can't have (it's an "additional restriction" that the original software you licensed may not have had; for instance, if clickwraps are covered by law that the GPL is not covered by, you are forcing additional terms)
I know that the GPL3 had some fine tuning with regard to TiVoization and web servers, but I'm not aware that it would bar DRM software itself; but perhaps.
OK, I found it here for GPL3. You are partially correct that the GPL3 contains some anti-DRM measures but not in the sense you describe:
http://www.gnu.org/licenses/quick-guide-gplv3.en.html "It's always possible to use GPLed code to write software that implements DRM. However, if someone does that with code protected by GPLv3, section 3 says that the system will not count as an effective technological "protection" measure. This means that if you break the DRM, you'll be free to distribute your own software that does that, and you won't be threatened by the DMCA or similar laws."
I thought one aspect of the GPL (copyleft being a clever copyright hack) is that the license applies only to the code you are licensing, and not to other copyrighted works you may have authored, but in a certain sense it does. I'm sure RMS and Moglen and FSF have thought harder about this than I have, so it's quite likely I'm missing something; however they do have broader agendas as well.
So, practically speaking, you can't have free DRM software. But you can have "open source" DRM software, because there's no part of the OSI that classifies software that acts like such a trap as being immoral. The GPLv3 essentially ensures that a user is not threatened by legal threats about breaking DRM in a piece of free software. It's the only software license that ensures this AFAIK, so I'm a bit sad more people don't use it for firmware and other places where defence against tivoisation matters.