- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
TLDR: Companies should be required to pay developers for any open source software they use.
He imagines a simple yearly compliance process that gets companies all the rights they need to use Post-Open software. And they’d fund developers who would be encouraged to write software that’s usable by the common person, as opposed to technical experts.
It’s an interesting concept, but I don’t really see any feasible means to get this to kick off.
What are your thoughts on it?
On what is your doubt based? Like what devices do you have that you think are violators? Like I say I imagine that careless violations aren’t, like, un-heard of, but correcting them once things are explained is almost always the response. I mean, correcting the violation is usually free and easy. I’m not real familiar with the SFC, but I know they’re actively suing Visio right now, and I know the FSF is happy to bring cases to trial if it comes to that (they kind of like doing it it seems like).
Link to the Best Buy case
This talk says “[Free Software] is generally everywhere and a lot of these smart devices that you buy off the shelf most likely is running some sort of free software but most people would never know that. Generally it’s not indicated anywhere that it’s running any type of free software. There’s no written offer for sources which is sadly the most popular… the written offer for source code seems to be the most popular way that they go about distributing the software but generally they don’t follow up with it or what they distribute is not really that.”
This article mentions that “I’ve been on a mission in recent months to establish just how common and mundane GPL violations are. Since 21 August 2009, I’ve been finding one new GPL violating company per day (on average) and I am still on target to find one per day for 365 days straight.”
I’ve got a robot vacuum cleaner that runs the Linux kernel and Busybox but came with no written offer for source code. (Per the article above, I’ll refrain from naming and shaming the company.) I might go look at the documents that came with my smart phone a little later and see if I can find any written offers for source.
Hm, interesting stuff. Yeah, maybe it’s more common than I was aware of – that’s still a little weird to me, because there are entities like FSF that are so happy to go to bat for people legally if they do want to make it a legal issue.
Maybe it’s made a little more complex because a lot of authors don’t want to “punish” the company involved so much as they just want people to comply with the terms of the license, and a lot of companies aren’t violating the license out of maliciousness but just from lack of knowledge or it just being more difficult than it sounds to keep your ducks in a row with source availability.
FWIW, I know Android phones generally have something buried in the settings where it explains what the licensing is for the code on the phone and with a theoretical offer for the source if you want it. That seems like what the Youtube talk is about; just creating the technical tools so that people can be in compliance without it being a pain in the butt that costs your engineers time and costs you money to do which companies are going to be tempted to avoid. But yeah, maybe people are getting sloppy about it in a way I wasn’t aware of; that’s sad to me if so.