Telstra Violating the GPL?
daria42 writes "It looks like Australia's largest telco, Telstra, hasn't exactly been paying attention to its responsibilities under the GNU GPL. Australian coder Angus Gratton has been investigating the company's branded T-Hub, T-Box and T-Touch products — all based on Linux, and all without any source code or GPL license attached. Naughty. However, it's not as though Telstra is the only one to blame — the goods are manufactured by Sagem, Netgem and Huawei respectively."
Telstra responded quickly to Gratton's claims, saying they would work with the vendors to straighten out the licensing situation and fix any compliance issues.
In Australia Telstra is the villain that everyone loves to hate. But in this case, it is not really their problem. They paid some OEM for a branded product that I very much doubt they had that much invested in. This is really a minor oversight that has been turned into a story.
Just because they have branded it does not mean they have changed any source. I have never seen one of these things so I don't know anything about them; but they may not be obligated to distribute any source. Also you don't have to provide the source with your binaries to satisfy the gpl. You just have to make the source available in a useful format if someone wants it. Has anyone asked Telstra or any of the manufacturers for the code?
Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
Telstra should get a serious ass kicking over this. The amount of money they've spent on advertising alone for this product line wipes out any possible "we didn't know" excuse.
They had to have been told, by multiple lawyers, that this is happening.
If an ordinary person can get fined millions of dollars for minor IP violations, then a corporation the size of Telstra should be fined tens of billions for knowingly violating the GPL in a flagship product. But of course, the law is never fair.
How could they not have known? You don't spend a hundred million dollars promoting a product without hiring competent lawyers to cross your t's and dot your i's.
Any IP laywer would check the origin and license of the software.
They have a special bundle that includes the T-Hub, T-Box and T-Touch all in a velveteen container. They call it the T-Bag.
The company did a sales demo recently, and one of the main concerns of the client was that 'we don't use open source in any way'. The client was shit scared of anything to do with 'open source' because they believed that if any were used for anything, suddenly they had to give away all their proprietary secrets to the world.
I tried to explain the differences between the licenses to my boss (BSD vs. GPL vs. Apache etc) and what the GPL really meant (If you don't distribute you have no problem) but since it was my leaving do and people just wanted to drink beer, I don't think anyone was listening.
Stories like this about Telstra just pander to the FUDists.
It is not sufficient to merely provide links. Telstra must provide the source code.
Huh? If this were literally true, then an N-level distribution chain would require separate copies of the source on machines owned by every part of the distribution chain, including the delivery companies that merely transport the physical packages, or the customer's ISP if the product is downloaded. It's fairly common for GPL-compliant suppliers to merely link to the source on a web site owned by one company in the chain. As far as I know, this has generally been held acceptable.
If every company involved in the distribution has to have a separate source repository, it would seriously interfere with the distribution of GPL'd software. It would be quite reasonable for a distribution company to refuse to deliver GPL'd products if they were required to supply the source to software inside packages that they were delivering. Here in the US, I'd expect that USP and FedEx would be very unhappy about being required to run source repositories, as would every ISP (though the ISPs would at least have employees who know what software source code is ;-).
I hope this isn't an actual requirement of any version of the GPL. Has anyone collected a list of the wording of various versions, with explanations of their legal implications? If some version does actually have such a stringent requirement, it would be useful to know about it, so we can avoid using that version with software that needs to be "delivered" in physical or electronic form.
Those who do study history are doomed to stand helplessly by while everyone else repeats it.