5 ms·
We got the GPLv3 to close the TiVo loophole, I wonder if we'll get the GPLv4 to close the Red Hat loophole.
by gary_0 3y ago
We got the GPLv3 to close the TiVo loophole, I wonder if we'll get the GPLv4 to close the Red Hat loophole.
- mindslight 3y agoDon't forget AGPL to close the SaaS loophole. FWIW it's arguable whether GPL3 was even needed to close the Tivo loophole, since GPL2 includes "the scripts used to control compilation and installation of the executable". It's unfortunate that none of the major kernel copyright holders are willing to litigate This whole GPL with contractual restrictions was tried before by Sveasoft (WRT54G firmware). They ended up failing and becoming a footnote in history, but Redhat is obviously much larger and more significant to the overall ecosystem.
- olliej 3y agowhat would that be? "If you ever release something under GPLv4 you must continue publishing updates for all time, and you must provide free build support for all other people/organisations who have ever used, shipped, or repackaged it"? As far as I can make out all RH has done is said "we're no longer spending our own money to support downstream projects and forks of our products", and everyone seems to be saying that they should not be allowed to do that. Which seems to be a very clear statement that RedHat should be required to spend time and money writing code to support other projects, whether or not those projects contribute anything, or are well funded.
- geerlingguy 3y agoI think "you may not put any restrictions on sharing the code for any user who receives the source code, including but not limited to threatening account termination solely for the exercise of the rights granted by this license."