3 ms·
The FSF is not 'attacking' such licenses, they're just arguing that they aren't free libre software licenses. It's the SSPL people and others, by trying to co-o
by simonh 7y ago
The FSF is not 'attacking' such licenses, they're just arguing that they aren't free libre software licenses. It's the SSPL people and others, by trying to co-opt the free and Libre software movement by claim their licenses are something they are not, which are mounting the assault. And let's be clear it is a pernicious, aggressive and deliberate attack threatening, and in some cases knowingly intended to fundamentally undermine free software principles. This is an existential threat to the FSF.
If they just went away and propagated and argued for their licenses on their own terms, the FSF wouldn't have anything in particular to say about it.
- zozbot234 7y agoAnd the FSF has even come up with their own license for network services, namely the AGPL - that is a full free-software license, since compared to the GPL it only clarifies requirements around public performance of the covered work (which unlike mere "use" of the software, is something that copyright law expressly grants as an exclusive right of the copyright holder!)
- kemitchell 7y agoSSPL was a direct response to perceived loopholes and inadequacies in AGPL. I’ve written about that here: https://writing.kemitchell.com/2018/11/04/Copyleft-Bust-Up.html https://writing.kemitchell.com/2018/11/04/Copyleft-Bust-Up.h... Most people never get that far, because they write the license off as an attack on principles. The debate about the substance didn’t really get to happen. As for public performance, I’m not aware of any case law to suggest that the public performance right applies to software as you suggest. And I’ve never seen FSF or independent legal counsel argue that GPLv3 and AGPLv3 are functionally equivalent due to background law. The FSF theorists I’ve read describe AGPL as “synthesizing” a public performance right for software that doesn’t otherwise exist under current copyright law. They do so out of two existing exclusive rights: the right to prepare derivative works (making changes or building larger programs) and the right to reproduce in copies (incidental to use).
- zozbot234 7y agoWell, I'm not aware of any case law to suggest that the right would not apply. Until the question is decided either way, it makes sense to assume that it would be applicable.
- kemitchell 7y agoThat’s not how US law works. Van Lindberg has done a lot of work on public performance recently. You might like to read his blog.
- the_duke 7y agoThe "aggressive, deliberate, threatening attacks" I have seen in discussions like this almost always seem to come from the FSF crowd. (not necessarily official sources, but supporters in public discussion channels)
- simonh 7y agoIf the source available people weren’t trying to appropriate the term Free Software (with capitals) this argument wouldn’t exist. Free Software has a long standing, broadly accepted definition which many of these companies accepted and see to their advantage for many years. Now they want to change their licenses, but keep using the term. They are trying to take other people’s stuff. They can’t just walk away with all the good Will and social capital Free Software has built up over the years because it’s beneficial to their shareholders. That’s the attack, it’s a smash and grab, and that’s why FOSS is fighting for its life in this.
- cy_hauser 7y agoFrom where I sit it appears the FSF has come up with a particular definiton of "free" and opposes anyone using the term "free software" if their meaning of free differs from what the FSF desires. Maybe the term "FSF free" should be used when that is the intent rather than trying to corral the term "free software" itself.
- danShumway 7y agoThe FSF came up with a particular definition of "free", the community broadly accepted it, the community and developers releasing software under that definition built up a particular public association with that term, and then a bunch of companies decided they wanted the all the goodwill of that term without paying attention to any of the fundamental rules the community had established years ago. Literally this entire conflict could go away if critics of the FSF just used the term "Source Available". What would be wrong with that? Why does our community need to be the one to give up our terms and muddy years of existing language, documentation, and cultural association? What exactly is the problem with just using the words "Source Available"? If someone develops a new license, why is it suddenly my responsibility to redefine the terminology I used for everything I've ever built?
- cy_hauser 7y agoBefore now there was no conflict for the the term free software. When it accomplished the same goal for everyone many people just didn't care about a precise meaning. It was "free enough" for all views to fit in the same tent. Large corporations are now stepping the unwritten meaning held by one portion who were previously satisfied with the overall outcome. Before, these people didn't care who owned the term as long as the goal was achieved. Now that the situation has changed these people want the phrase to mean what they always believed it meant. Even though you might not have been aware this difference even existed. The meanings of words change with the progress of humanity. Nobody gets to hold on to a word like free just because they're comfortable with its current usage.
- danShumway 7y ago