Email or username:

Password:

Forgot your password?
Top-level
Glyph

@mcc gosh I hope I'm not spreading misinformation here, my memory of this was that it was a pretty pedestrian corporate interaction not some weird urban legend, but it's bothering me that I can't find _any_ news coverage

25 comments
Farce Majeure

@glyph @mcc So the PlayStation thing was basically the way Cygnus did compiler port sales. The Long and short of it is they'd do a gcc target for a given CPU and agree to not release it, then distribute it only to the customer, but still under the GPL, with the caveat that the contracts said they retained all the rights and could use the source code in other ports, and I think it may have also had a timeout. Then, \

Farce Majeure replied to Farce

@glyph @mcc Sony distributed it to game devlopers, who were under their own contracts and NDAs with Sony and received this compiler as a binary and with no right to distribute it. The contractors didn't receive it under the GPL, but Cygnus still had their own copy that would eventually be upstreamed.

This sort of thing has always been part of the business of making and selling GPLed software.

And also the dig at Red Hat above is still just plain not what actually happened.

Farce Majeure replied to Farce

@glyph @mcc (incidentally I think we stopped doing this in the compiler business not long after Red Hat bought Cygnus.)

Glyph replied to Farce

@vathpela @mcc “didn’t receive it under the GPL” is doing a lot of work there. Like presumably portions of it were copyrighted by the FSF? Were they a party to this contract somehow? Were they okay with binary proprietary licensing?

Glyph replied to Glyph

@vathpela @mcc (thank you SO MUCH for pointing me towards the factual history here!)

Farce Majeure replied to Glyph

@glyph @mcc so there are two parts here - 1) Cygnus owned the code they wrote (which wound up being a strikingly large amount of the compiler) until they contributed it back to the FSF, (though they did have a blanket agreement which did that), and ... \

Farce Majeure replied to Farce

@glyph @mcc 2) in terms of software licensing, as I understand it (and let's be sure: IANAL) if you work for a company and they for instance get a copy of Visual Studio and give it to you, Microsoft has given it to them under whatever license, but your employer has more or less just loaned it to you. You don't have that software licensed to you, your employer does. And that's something that can be established through non-employment contracts as well.

mcc replied to Farce

@vathpela @glyph This (conveying code from company A to B to C while claiming it was not "distributed") seems to violate the plain language of "copying" or "distribution" as it would have been understood by people who place their code under GPL2, and I doubt a court would sign on with it if this were tested. In GPL3 "distribution" is replaced with a more fine-grained definition of terms concerning copying, and so if this loophole was ever real, it's probably shut now.

mcc replied to mcc

@vathpela @glyph At any rate if the behavior in question has been halted for unrelated reasons it seems hard to come to a firm conclusion about whether it was entirely legal?

Farce Majeure replied to mcc

@mcc @glyph I think that's a fair conclusion. Also worth noting that there are other slightly different ways they could have done it that are even more confusing (and maybe they did, I wasn't ever in that part of the business). Like, what if they only ever gave the customers patches, and then rented them out a consultant who downloaded, patched, and compiled gcc for them? It's exactly the same in the end, but a largely different thing being handed over.

Glyph replied to Farce

@vathpela @mcc thanks again for stepping in so I wasn't spreading around false claims. I still think the whole scheme sounds confusing and dubious, but now at least I know where to go to do research to understand it better in the future!

Farce Majeure replied to Glyph

@glyph @mcc Also worth keeping in mind that this was like 25 years ago, I didn't work in that part of the company (or indeed for Cygnus ever), I've never paid someone to write a compiler port for me, and it would be remarkable if I didn't have at least some part of this history wrong ;)

mcc replied to Farce

@vathpela @glyph Hrm, well, now that you mention it, I think there might actually *be* a very dangerous patch distribution loophole to the GPL, I'm willing to hear that argument. Especially since I've ALSO seen an almost identical loophole used by people who ADVOCATE the gpl (see "LAME"..)

Farce Majeure replied to mcc

@mcc @glyph I think the argument against that is that a patch to a piece of software must be, at least in some part, a derived work. (Also I have written a lot of GPL'd software. ;)

Farce Majeure replied to mcc

@mcc @glyph Well, I don't think lawyers or the courts see it that way, but again I am not a lawyer so I won't belabor that point any more. Maybe as @luis_in_brief, I hear he is a lawyer, just not your lawyer or my lawyer ;)

Luis Villa replied to Farce

@vathpela @mcc @glyph ugh, I’m a lawyer but despite recent appearances I have a day job, so I should really get back to my work of (checks todo list) writing up more opinionating on xz, oh gooooodddddddddd

Glyph replied to Luis

@luis_in_brief @vathpela @mcc we'd all better stop posting so we can get back to our respective jobs, which are *checks notes* also posting, mostly about the same topics, just with a slightly different emphasis

Glyph replied to Farce

@vathpela @mcc @luis_in_brief ultimately the nature of the debate here just proves the point I was making :). We are arguing over what precise powers that a particular genie would have if it were ever released, but the reality is that the genie gets its power from the tens of millions of dollars that would need to be spent to release it in the first place, and we will never find out so it doesn't matter in any practical sense

Geoffrey Thomas replied to mcc

@mcc @vathpela @glyph I don't know how to conclude whether this article is correct or biased but it talks about the question of whether GPL triggers between e.g. a company and its independent contractors, or when a company is acquired: jolts.world/index.php/jolts/ar

Glyph replied to Farce

@vathpela @mcc also not a lawyer, but this sounds novel and bizarre to me. "licensed to" is a shorthand; the license is a limited right to perform copies that would otherwise be considered infringement, which presumably an employee acting on behalf of a company would need in exactly the same way as the company itself would; everybody involved needs the right to make these copies

Glyph replied to Glyph

@vathpela @mcc (I mean, just kidding, as long as the MAI v. Peak / Cartoon Network v. CSC circuit split holds this is all gibberish in US law and I have _zero_ idea how it would hold up in Japan)

mcc replied to Farce

@vathpela @glyph I find in the text of GPL2: "You may not impose any further restrictions on the recipients' exercise of the rights granted herein."

If Sony [or whoever else] made someone sign an NDA saying they could not distribute the GPLed software they gave them, Sony was violating the GPL, and therefore did not have the right to distribute the modified GPLed code in question.

mcc replied to mcc

@vathpela @glyph (The GPL3 has a more complex clause. The fact I find the GPL3 harder to interpret as a non-lawyer is a reason I prefer GPL2.)

keithzg replied to mcc
@mcc @vathpela @glyph I'm a big fan of copyleft-next for this very reason, it's even easier to read as a non-lawyer while still having upsides from the GPLv3.
Farce Majeure replied to mcc

@mcc @glyph right, but that only applies if you're actually distributing the software, which isn't as straightforward as you may hope (see my other reply to Glyph).

Go Up