3 ms·
Here's one example when I was a consultant doing work on embedded devices, I saw often very flagrant violations of GPL. When I asked what their policy on GPL w
by kenjackson 16y ago
Here's one example when I was a consultant doing work on embedded devices, I saw often very flagrant violations of GPL. When I asked what their policy on GPL was it was that GPL was only allowed in these specific modules, but not these other ones. And they had a review process for it.
When I went and reviewed the logs I saw that the review process did happen, but tailed off and then about two years before I began it had completely stopped. Yet I could find new code checked in that GPL'ed.
This particular place was really receptive to my suggestions and actually refactored the code and rewrote some of the code (although I wouldn't call it clean room). But had I not randomly ran across it, they stopped looking at it. Legal and management cared a great deal about this, but the devs on the floor didn't seem to care quite as much. And I'd heard about some that complained that I had apparently come to slow them down by adding extra process.
In any case, this isn't the only example. I think you'd be surprised how much BSD code gets shipped w/o attribution. And I think you'd also be surprised at how much reverse engineering takes place (which is a slightly different issue, but I think related in liberties devs will often take w/o consulting legal).
- davidw 16y agoAha, embedded: that's definitely an area where companies get busted for GPL violations. Apache Harmony is the other side of the coin from this though: it's an open source project with very strict requirements in terms of contributors: http://harmony.apache.org/contribution_policy.html http://harmony.apache.org/contribution_policy.html And I think Google is likely a lot more careful/knowledgeable than some random hardware company trying to ship a product as fast as it possibly can. Also, my guess is that something like Dalvik is not just something you find laying around on the internet...
- kenjackson 16y agoI just read this snippet from Nilay Patel: http://www.engadget.com/2010/10/05/google-responds-to-oracles-android-patent-lawsuit-we-break-it/ http://www.engadget.com/2010/10/05/google-responds-to-oracle... IANAL and at least he is. I'm not really sure what to think from it. In particular these bullet quoted items: "•Sun open-sourced Java Standard Edition under the GPL in 2006 and 2007, but didn't include a patent or copyright license with the code. In order to get that license, developers have to demonstrate compatibility with the Java specification. •The only way to demonstrate compatibility with the Java specification is to use Sun's Technology Compatibility Kit, or TCK, and Sun / Oracle and Apache have been bickering about the license for the Java TCK, or JCK, for years. (That's putting it lightly, actually. It's been more like a war.) •The only license Sun ever offered Apache for the JCK included significant "field of use" restrictions, including a restriction on mobile phones." This actually makes me believe that Oracle and Google both know what they're doing and this ends up really ugly. Can anyone give a second opinion as to if those bullet points are true?
- davidw 16y ago* Apache's implementation is a clean room one - the ASF agreed to no such restrictions on the TCK, and did not get a license for it. * Dalvik, as other people point out above, is not Java. It is its own virtual machine, built from the ground up by Google, so Oracle can't claim copyright on it, but is going after it with patents, which seems like a low blow (we can't compete, so we'll sue).
- kenjackson 16y agoDalvik seems off the table to me. I suspect Oracle has little case there. But the Apache stuff seems shadier. It reads like you specifically can't use the Apache stuff for mobile devices due to patent and copyright issues. Clean room implementations don't get you around either of those specific legal issues -- unless I've misunderstood something here.
- davidw 16y agoI think you've misunderstood something: Apache never signed anything with Sun. Apache never got to use the TCK, because the ASF didn't accept those terms, and therefore, Apache Harmony can't claim to be an implementation of Java, legally speaking. Copyright doesn't apply because Harmony does not use other people's code. Patents... may or may not apply, but the complaint only goes after Dalvik (Google's VM, not Harmony's) in terms of patents, IIRC.
- kenjackson 16y agoYou can copyright API signatures (classes, methods, functions, etc...). I assumed that was what was at issue. Is it not? If it is are you saying that Apache clean roomed the whole thing so there is no interface compatibility or library similarity? If that's the case then I agree.
- davidw 16y agoMy understanding is that no, you cannot copyright an API.