this post was submitted on 09 Nov 2025
43 points (87.7% liked)
Open Source
42798 readers
65 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 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Was this done according to proper clean-room design principles? If so, then imo the GPL is still working as intended. The company had to spend a fuckton of money and time getting one engineer to read the source and describe what was done to other engineers, and then ensure that one engineer never ever worked on the project again.
If they didn't do that then they violated the GPL and someone should report them to the SFLC.
I guess it depends on the goal the author has. If the goal is to let big companies pay their employees for contributions to open source, then it seems GPL3 is not the right license. Which is also the reason why Linux is licensed under GPL2 btw.
If the goal is to make companies avoid contributing and then copy it while claiming they did proper clean-room design (lets be honest, it happens all the time and rarely does anybody hear of it or bring it to court) ... then yeah it works as intended.
the GPL v2 doesn't have any less restrictions around strong copyleft (requiring that a company publish changes for components).
Maybe you're thinking of the fact that GPL requirements don't cross the kernel module syscall boundary?