Full disclosure - I'm on the Board of Directors of the Software Freedom Conservancy.
Having said that, please donate to the Conservancy - they are the only organization doing GPL compliance work like this for the Linux kernel. This blog post shows how hard they work behind the scenes (they've been working with Tesla on this violation since June 2013) to help get everyone access to the source code they are entitled to have.
5 years to get them to comply? Shows how much Tesla cares. All it shows that I can rip code and get away with it after making millions.
I can walk into a lot of companies that do exactly what Tesla does. Hell, you can just go to the up coming PackExpo show and find violators all over the damn place (Nobody really checks industrial machine software since very little people have access to it). The industry has shown that you can do this and chances are you will get away with it. None of them contribute anythin
I think you seriously underestimate the ability and staffing of engineering groups doing this stuff. I would bet 99% aren't aware of it. Has any big huge revelation come from these releases? It looks like a pretty boring code release, technically.
It's why companies like the BSD. And history shows it's not that they don't give back (Look at FreeBSD's commits from corporations) it's that they don't like being strong armed into nothing.
It's why companies like the BSD. And history shows it's not that they don't give back (Look at FreeBSD's commits from corporations) it's that they don't like being strong armed into nothing
I'd say its more a lawyer thing than anything. The engineers want to give back. But the GPL terrifies the lawyers because they seem to think it means you have to. Heres the thing you ONLY have to if the end result is being distributed, and even then your only obliged to provide source access to whoever you've distributed
https://github.com/teslamotors... [github.com]
Full disclosure - I'm on the Board of Directors of the Software Freedom Conservancy.
Having said that, please donate to the Conservancy - they are the only organization doing GPL compliance work like this for the Linux kernel. This blog post shows how hard they work behind the scenes (they've been working with Tesla on this violation since June 2013) to help get everyone access to the source code they are entitled to have.
https://sfconservancy.org/supp... [sfconservancy.org]
5 years to get them to comply? Shows how much Tesla cares. All it shows that I can rip code and get away with it after making millions.
I can walk into a lot of companies that do exactly what Tesla does. Hell, you can just go to the up coming PackExpo show and find violators all over the damn place (Nobody really checks industrial machine software since very little people have access to it). The industry has shown that you can do this and chances are you will get away with it. None of them contribute anythin
I think you seriously underestimate the ability and staffing of engineering groups doing this stuff. I would bet 99% aren't aware of it. Has any big huge revelation come from these releases? It looks like a pretty boring code release, technically.
It's why companies like the BSD. And history shows it's not that they don't give back (Look at FreeBSD's commits from corporations) it's that they don't like being strong armed into nothing.
I'd say its more a lawyer thing than anything. The engineers want to give back. But the GPL terrifies the lawyers because they seem to think it means you have to. Heres the thing you ONLY have to if the end result is being distributed, and even then your only obliged to provide source access to whoever you've distributed