this post was submitted on 27 Jun 2023
62 points (100.0% liked)
Technology
37800 readers
315 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think they'll still be compliant as long as they offer their source to customers. The GPL doesn't require that you make source available to anyone, but to anyone that you distribute binaries to. From the GNU website:
Source: Quick GPLv3 Guide under the More Ways for Developers to Provide Source section.
Of course the GPL also allows redistribution of source code, and Red Hat seems to want to threaten customers who do so.
Yeah, preventing your users from redistribution this is where they might get into trouble and the GPL license would be retracted and thus they would have pirated the software. But someone would need to prove it in court and IBM has a couple of good lawyers.
Maybe I'm missing something; I thought the issue here was that they "aren't" making their source code available. Just modifications to the original code that can be supplied back to the original source. That doesn't cover all derivative work though.
Not quite--all developer accounts for RHEL will have access to source. They're just trying to restrict redistribution of said source by downstreams.