Slashdot Mirror


Australian Telco Telstra Complies With GPL

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!"

6 of 90 comments (clear)

  1. I LOVE MY CAPS! by Frosty+Piss · · 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 complying, perhaps it will ENCOURAGE others to comply as well?

    Of course you all can SHIT ALL OVER THEM and see how that works, as well...

    --
    If you want news from today, you have to come back tomorrow.
  2. Adhering to standards. by Jarryd98 · · Score: 4, Insightful

    I'd have to agree with the above comments. Telstra doesn't deserve any credit for compliance alone. It's expected. Many people seem far too willing to forgive/forget within a short period of time. They delivered what was expected of them after an extended period of inaction. That is all.

  3. Re:"Engaging"? by cheese_wallet · · 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.

  4. Re:Just for clarity by williamhb · · Score: 4, 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.

  5. Re:"Engaging"? by williamhb · · 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.

  6. Correct title: by Ant+P. · · Score: 4, Insightful

    "Telstra profits off software piracy for half a year without repercussions"