4 ms·
It seems like Google is hoping that Oracle effectively made a mistake in their claim (claiming infringement on something that was released to open source). Whi
by kenjackson 16y ago
It seems like Google is hoping that Oracle effectively made a mistake in their claim (claiming infringement on something that was released to open source). While this is possible, it seems more likely that Google sucked in some code that it shouldn't have. This is based on my past work with engineers and OS code. I've worked on projects with specific rules about what we use, to only audit and see that these rules were quickly abandoned w/o review.
I have no idea what happened in this case, but I do fear that when you have various rules relating to various pieces of code, engineers often don't pay attention or often simply disregard the rules in the belief that no one will care -- "Sun will never sue us... oh, Oracle bought them... brb, I need to go make some reverts"
- davidw 16y agoThere are two main bodies of code in question: the VM that Google did, which I'm sure was vetted by their own team, and the Apache Harmony classlib, which is a project that has always had very high standards in terms of what is included - they knew from the get-go that they were operating in a potentially dangerous space. So this doesn't sound plausible to me.
- kenjackson 16y agoThe other psosibility is that Oracle/Sun doesn't know the law or are just lying. Again, I have no clue, but my experience in the space of dealing with open source are lots of violations of various forms. Most innocuous as virtually no one seems to care, but they exist nevertheless. But maybe Google is really different than most organizations and they actually did a thorough vetting over the lifetime of the project.
- davidw 16y ago> my experience in the space of dealing with open source Could you be more specific? I'm curious, as this is not something that seems familiar to me, but 'open source' is pretty big.
- kenjackson 16y agoHere'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?