Australian Telco Telstra Complies With GPL 90
An anonymous reader writes "Late last year, Australia's biggest telco Telstra was sharply criticised for using GPL'd code in several of its new products — but not publicly distributing changes it made to the code when doing so. However, it looks as though the company has now come clean, publishing a source code CD of the files changed in its development effort and acknowledging the GPL and Lesser GPL. It's good to see companies responding to the open source community this way and engaging — makes a change from the past!"
Wow. (Score:1)
And it's Telstra of all companies deciding to do the right thing. I find that amazing.
Re: (Score:2)
*sips coffee*
Indeed.
Re: (Score:1)
Re: (Score:2)
they haven't fixed the false positives in their billing system yet... i still get called at work by them, asked if i'm someone else, hassled for money and when i ask to see a bill, they say i'm not such-and-such and thus am not entitled to know. when i ask why my number is connected to that account, they hang up.
pricks.
Re: (Score:2)
Re: (Score:2)
When it comes to litigation, Telstra is like Microsoft and will quite happily keep something in the courts for as long as required, in order to maintain some sort of market advantage... this is quite a change !
Having said that Telstra -
WHERE THE HELL IS FROYO FOR MY WILDFIRE !?!?!? YOU'VE BEEN PROMISING I
Re: (Score:1)
When it comes to litigation, Telstra is like Microsoft and will quite happily keep something in the courts for as long as required, in order to maintain some sort of market advantage... this is quite a change !
Telstra probably realised pretty quickly - well, 10 months is relatively quick for a monolithic company - that they had no market advantage to maintain by dragging this through the courts.
Re: (Score:2)
WHERE THE HELL IS FROYO FOR MY WILDFIRE !?!?!?
Right here. [xda-developers.com]
Wow. I'm having to add a line of no-value text because quoting your yelling and providing a link in response is "lameness". Thanks, Slashdot. You're the best!
Re: (Score:2)
"Engaging"? (Score:3)
How is this anything but an eventual response to an internal snafu which could've resulted in (much more expensive) litigious actions?
The GPL violations, and the resulting denial of compliance (for years, wasn't it?) was nothing but bad press. In contrast, had they admitted to the snafu right off the bat and addressed it promptly (a couple months? 6 on the outside?) it'd have been another thing entirely - the press would've been positive. GNU 'compliance' types just want the (free to the violators) adherence to the GPL - they don't care about the money or licensing aspect of it.
In my mind, this almost says less than doing nothing about it at all - "oh, we've got another release, let's include those license files and source code this time".
(What do you want to bet the code is significantly aged and with numerous vulnerabilities known for a long time?)
Re:"Engaging"? (Score:4, Insightful)
If they complied from the start, there wouldn't have been any press at all. Now they have it.
Just like at most businesses, it's not the engineers who get it right from the start that get credit. It's the ones who screw things up and then heroically fix it later that get all the kudos.
Re:"Engaging"? (Score:5, Informative)
How is this anything but an eventual response to an internal snafu which could've resulted in (much more expensive) litigious actions?
The GPL violations, and the resulting denial of compliance (for years, wasn't it?) was nothing but bad press. In contrast, had they admitted to the snafu right off the bat and addressed it promptly (a couple months? 6 on the outside?) it'd have been another thing entirely - the press would've been positive. GNU 'compliance' types just want the (free to the violators) adherence to the GPL - they don't care about the money or licensing aspect of it.
In my mind, this almost says less than doing nothing about it at all - "oh, we've got another release, let's include those license files and source code this time".
(What do you want to bet the code is significantly aged and with numerous vulnerabilities known for a long time?)
Actually, it wasn't Telstra who was doing the wrong thing in the first place. The company that makes the T-Hub device, that included the GPL code, and that hadn't released their code is Sagemcom. Telstra just re-sell the device with their sticker on it. (Very much like how iiNet sell Belkin-made modems under the brandname "BoB".) Is a shop selling physical objects a GPL licensee if the manufacturer of one of its physical object happened to include some GPL code? Would Wal-Mart be in breach if they'd stuck one of these on their shelves? In this story, Telstra has put pressure on Sagemcom to make the code available and comply with the GPL. I think that's a good outcome, and I can see why it would take some time for Telstra to comply -- they didn't have the code to be able to release it.
Re: (Score:2)
Re: (Score:3)
"Would Wal-Mart be in breach if they'd stuck one of these on their shelves?"
Yes, distributing hardware with software in it, is still distributing software.
If Telstra sold re-badged devices with unlicensed copies of windows on it would you expect them to get away with it ?
Interesting you mention iiNet, they have some issues as well.
Re: (Score:2)
If WalMart were to sell 3rd shift Cisco gear, you don't think Cisco would have all the units pulled and someone's head would roll?
Re: (Score:2)
Yes, distributing hardware with software in it, is still distributing software.
I don't think this is right. Copyright doesn't protect distribution, it protects reproduction. The software would be reproduced onto the device before it ever arrived at Walmart. It just so happens in the internet age that distribution equates to copying since servers don't typically delete their source copy when someone downloads, but the minute you revert to transferring something in meat space you're back to distribution being different from copying.
Re: (Score:2)
To arent allowed to "reproduce" GPL'ed works unless you conform to the license, the license places obligations on distribution.
This has been to court before, companies involved where Best Buy, Samsung and Westinghouse. Walmart would be no different
http://linux.slashdot.org/story/09/12/14/210207/SFLC-Sues-14-Companies-For-BusyBox-GPL-Violations [slashdot.org]
Re: (Score:2)
> Is a shop selling physical objects a GPL licensee if the manufacturer of one of its physical object happened to include some GPL code?
You seem to be implying that a reseller is not governed by the licence! Actually, resellers/redistributors are the one of the addressees of the GPL licence, otherwise copyright law would prevent resale of the software. The licence is granting a right, not removing it, which is why it is called a licence!
If I sell physical CDs with copies of Microsoft Windows on the
Re: (Score:1)
Re: (Score:2)
But it seems you forget the court ruling that was posted here on slashdot (although it was a while ago).. the guy who purchased some Adobe suite, and then sold the parts he never used on Ebay. IIRC they ruled you were only licensing the "product" and therefor the First Sale Doctrine did not apply. Search and I'm sure you'll find it.
Re: (Score:2)
The 'First Sale Doctrine' is a US specific thing; while there is similar "exhaustion of rights" law elsewhere, these laws are not general principles that allow arbitrary copying of software. These decisions and laws treat software as a 'product' rather than as information, which is a legal fiction; it is not a very strong protection for the consumer and soon or or later will be challenged.
My actual words were "physical CDs with copies of Microsoft Windows"; I used the word 'copies' deliberately to make t
Re: (Score:2)
Re: (Score:2)
I would have thought someone at Telstra would actually look at one of the devices and see that there could be a problem.
T: "What does it run?"
S: "Some form of magic. Its ok, just leave it up to us."
Re: (Score:2)
Since the OEM is distributing the software to the vendor customer, the OEM should already be aware of the licence issues surrounding that redistribution. If the software had all been proprietary, you would have been making sure you didn't break the licence agreements. Why would the free licences be treated differently - just because the OEM can't be bothered with an audit?
If the OEM was following the licences, then it would already have supplied (or made available) the GPL portions of the code to the ven
Re: (Score:2)
Re: (Score:2)
Re:"it's required by contract" (Score:2)
If the DRM contract requires you to protect the code by obscuring all of it, then it is incompatible with the licence contract that has been made with the owners of the GPL code that is in the machine.
You make it sound like there is no alternative other than to break the DRM contract. In fact, there are two alternatives: don't use code that is under a GPL licence; or don't make contracts that you cannot fulfil.
Making a contract does not invalidate all the licence agreements you have entered into; if yo
Re: (Score:2)
Most device makers use ancient versions of software, once they pull it in they rarely touch it.
I encourage people to use the (A)GPLv3, but thats not going to change anything in the short-medium term. We cant force device makers to update their software and commit themselves to a different license.
Busybox on the Telstra T-Box (netgem device) was from October 2004, changes they had made to the source included things such as adding some casts !
The problems isnt with open source coders and the license they choo
Re: (Score:2)
While I agree with you that the GPLv3 is preferable, the GPLv2 is not completely worthless even when DRM tricks are being used. The GPLv2 still makes the source available, and allows some freedoms - to study and share the code, even when the hardware is locked down. The Tivo legal trick has created the major problem that the user can no longer modify the code and use it on the existing hardware; but even Tivo was still required to make source available.
I did not write my post to support GPLv2 over GPLv3
Re: (Score:2)
Re: (Score:2)
Wow indeed (Score:1)
Yes lets give Telstra a pat on the back for finally complying with the GPL while this should have been expected from day one. The GPL is yet another licence agreement but not a restrictive one, if you don't like it, don't use it.
Re: (Score:2)
In the U.S. phone lists aren't copyrightable (Score:2)
Re: (Score:2)
Is the GPL legally binding in Australia?
Well, for their sake, it better be. Because if it were not binding, default copyright regulation would apply and these companies would not have the right to reuse and redistribute this code from the first place. Arguing GPL does not apply (as SCO claimed in the past) is shooting in its own foot.
Re: (Score:2)
Is the GPL legally binding in Australia?
Oh and as an Austrailian I would like to say " Fuck Telstra" they are the worst company in this once great country that is rapidly descending into mediocrity.
The thing is: If it is not binding for whatever reason, you cannot distribute the software at all. That is, without GPL giving you a license to use the software, normal copyright applies and you are not allowed to just copy and distribute copyrighted software. I don't believe there is more than a handful or 2 countries in the world who does not have copyright on software, and certainly, Australia is not exempt.
Re: (Score:2)
Is the GPL legally binding in Australia?
The usual response to that question is (and I have not legal training so I don't know how valid said response is) to point out that the license gives them the right to use the code, so if they state "we don't accept the terms of that license as it isn't enforceable in our territory" they give up the right to use the code under that license and need to negotiate something else.
Many a commercial entity will scream "no fair, no fair, waa, waa, waaaaa" at this point and claim that OSS is an airborn cancer that
Re: (Score:2)
i'm not sure to what extent the GPL has been tested in court anywhere. its legally binding in the sense that nobody has sued over it yet.
Re: (Score:2)
Careful there son thats the Post Master General you are messing with there. If it wasn't for the PMG inventing the telephone in 1961 none of you twitterers would be able to send your meaningless messages to each other.
Oh any by the way, 2400 bps should be enough for anybody.
Re: (Score:1)
Pffh. Telstra is the Vizzini to the PMG's Fezzik.
Re: (Score:2)
Apart from the fact that my wife has shares in them, I will be glad to see Telstra finally fold. Back when the Optus long distance service was new I used call forwarding from my telstra land line to my optus mobile. The telstra bill was in 25 cent units with no more detail than that so I called the telstra service line and asked them how much it actually cost to enable and disable forwarding. They put me on hold for five minutes and came back eventually: we are unable to answer your query because you have s
Re: (Score:1)
If it wasn't for the PMG inventing the telephone in 1961...
You're only off by 85 years... Alexander Graham Bell was the first to be awarded a patent for the electric telephone by the United States Patent and Trademark Office (USPTO) in March 1876.
Re: (Score:2)
Knowing a few "Telstra People" I am poking fun at their somewhat one dimensional view of the world.
Just for clarity (Score:1)
They're only distributing the files they changed? Then that's not complying with the GPL. The GPL very clearly requires "complete corresponding machine-readable source code". Basically, if you get a product with binaries of GPL licensed code, then you must be able to recreate those binaries from just the files that the vendor made available. Just pointing to someone else's distribution of the source is not allowed (there's only one exception: you got the code in binary form yourself and redistribute it non-
Re:Just for clarity (Score:5, Informative)
They're only distributing the files they changed? Then that's not complying with the GPL. The GPL very clearly requires "complete corresponding machine-readable source code". Basically, if you get a product with binaries of GPL licensed code, then you must be able to recreate those binaries from just the files that the vendor made available. Just pointing to someone else's distribution of the source is not allowed (there's only one exception: you got the code in binary form yourself and redistribute it non-commercially).
Can I suggest reading the article next time? It would have been quicker than typing up your post. From the article:
Gratton last week said he had requested and received a copy of the CD. “It looks like a complete GPL source release, all of the GPL components I identified seem to be there and there are build tools covering the BSP (board support package) for the SoC (system-on-a-chip) in the T-Hub,” he said.
GPL:... (Score:3)
GPL: You need to comply only if you get caught! (And even in this case, you can wait for a year or two)
Yeah, lets encourage this behavior further...
I LOVE MY CAPS! (Score:3, Insightful)
GPL: You need to comply only if you get caught!
On the other hand, are US Copyrights relevant and legally binding in Australia? Probably they are by virtue of treaties and such.
Seriously, not a troll, but what's the beef? We're lucky to see the CD at all...
Rather than raking Telstra over the coals for complying (albeit late) , maybe the more constructive thing would be to use it as an illustration to other companies as to how harmless it was to Telstra to comply - it did not hurt them competitively at all.
By giving Telstra POSITIVE FEEDBACK for compl
Re: (Score:1)
What does hurt mean even? I mean seriously. If you use GPL code you are gaining advantage. if you have to release code that is the cost of your advantage. If you think your additions are more valuable than the base you are using it on only then should you write it from scratch or use a non-free solution. Lets be honest for a moment. Nothing any company is going to add is worth more than the base of just about any GPL application. If Disney can use and contribute to GPL code and lots of other companies which
Re: (Score:1)
GPL: You need to comply only if you get caught!
Oh, good point. Let's force offenders to comply with the GPL before they're caught! Capital idea!
While we're at it, shouldn't we also make it illegal to break the law?
Re: (Score:2)
GPL: You need to comply only if you get caught! (And even in this case, you can wait for a year or two)
Yeah, lets encourage this behavior further...
I think there would be less violations if the FSF offered some useful targeted advice to the vendors. It is the vendor who is distributing the boxes, so they're the ones on the hook to supply the source code but they're often not the ones doing the firmware. Usually they'll subcontract that out and there could be subcontractors underneath them. Everyone in the chain needs to know their obligations during requirements gathering, contract negotiation phase, deliverables and in support. The FSF should produce
Adhering to standards. (Score:4, Insightful)
Re: (Score:1)
I'd have to agree with the above comments. Telstra doesn't deserve any credit for compliance alone. It's expected.
I expect my dog to come if I call him, but that doesn't mean I shouldn't praise him when he does.
Correct title: (Score:5, Insightful)
"Telstra profits off software piracy for half a year without repercussions"
Telstra's Intentions (Score:2)
Im a local copyright holder and am following this (There are still things that need to be done)
The impression i have is that Telstra just didnt realise what they where getting into, but since then they have made a genuine effort to fix the problem.
I give Telstra credit for accepting their mistake and trying to fix it, which is lot more than happens in other cases. They certainly could have made it more difficult.
Device manufacturers are the biggest problems, they never talk to developers, they already have
Upstream changes? (Score:2)
What upstream changes are likely to come of this? Will we see support for new chipsets as a result of this code release? New Drivers? New interfaces?