News for hackers. Stuff that matters.
Re:Apple not providing LGPL webkit source code for latest iO... by vaporstun on Friday May 06, 2011 @01:21PM (#2521652)
Anyone else find this to be a bit over-dramatic?

They have released every other version and just haven't released the 4.3.x one yet. There is no indication that they refuse to release it ever, the site still says "Coming Soon" and it has still been < 2 months since 4.3 was released.

Yes, I understand that under the GPL they're supposed to release it simultaneously with the launch, which they failed to do, but is this really front page news?

Re:Apple not providing LGPL webkit source code for latest iO... by docgnome on Friday May 06, 2011 @01:31PM (#2521693)
Yes. I take license violation very seriously. Imagine if Apple was violating a Microsoft license in this way. They'd be sued in a heart beat. Companies need to realize the (L)GPL is serious. It's not something you can just ignore because it's convenient.
Re:Apple not providing LGPL webkit source code for latest iO... by edw on Friday May 06, 2011 @04:40PM (#2522396)
If you take license violations very seriously, then I imagine that an audit of your computer would reveal no movies, songs, fonts, or applications that are not properly licensed, right?

Is Apple out of compliance with the license? Perhaps. Is this on my list of the ten thousand things I'm most concerned about? No.

And as for your assertion about Microsoft suing Apple in a heartbeat over a similar compliance issue, I think you don't know what you're talking about. Microsoft, to the best of my knowledge, hasn't sued anyone over the hundreds of MS patents they claim Linux violates. It took Apple a few years to get around to suing Samsung.

In other words, Companies' legal teams are usually subject to adult supervision by their CxOs. They don't just go around suing willy-nilly. Many lawyers see conflicts that lead to lawsuits as failures.

Reality is so surprisingly messy.

Re:Apple not providing LGPL webkit source code for latest iO... by FxChiP on Friday May 06, 2011 @05:53PM (#2522621)
If an audit of his computer revealed unlicensed movies, songs, fonts and applications, I (and probably he) would fully expect him to be litigated against -- such discoveries and resulting lawsuits are quite commonplace nowadays, it seems like. That doesn't make it right for anyone, even a large corporation, to violate intellectual property law.

To put another way: if I were found to be pirating Mac OS X, Apple would be in the right to sue me for intellectual property violation. If I found them to be using my code outside of the license I provided it to them (and the rest of the world) with, I should be in the right to sue them for intellectual property violation. Is this not correct?

(EDIT: fixed problematic grammar)

Re:Apple not providing LGPL webkit source code for latest iO... by daxelrod on Friday May 06, 2011 @08:59PM (#2522985)
Microsoft sued TomTom in 2009 for patent infringement[1]. One aspect of the suit concerned infringement in the implementation of the FAT filesystem in TomTom's Linux-based GPS navigation devices.

The two parties eventually settled[2].

[1] http://arstechnica.com/microsoft/news/2009/02/microsoft-sues...

[2] http://arstechnica.com/microsoft/news/2009/03/microsoft-and-...

Re:Apple not providing LGPL webkit source code for latest iO... by rimantas on Friday May 06, 2011 @03:56PM (#2522238)
Just curious, is source code for Webkit used in Honeycomb available?
Re:Apple not providing LGPL webkit source code for latest iO... by georgemcbay on Friday May 06, 2011 @06:28PM (#2522707)
Yes. While Google hasn't open sourced much of the Apache licensed bits of Honeycomb, they have posted all of the GPL/LGPL code as required by the licenses:

http://groups.google.com/group/android-building/browse_threa...

Re:Apple not providing LGPL webkit source code for latest iO... by rimantas on Friday May 06, 2011 @01:38PM (#2521721)
I don't know what situation is now, but Apple used to be the main contributor to Webkit. Who should sue Apple?
Re:Apple not providing LGPL webkit source code for latest iO... by jrockway on Friday May 06, 2011 @01:40PM (#2521734)
The other contributers whose copyrighted code they are distributing illegally.
Re:Apple not providing LGPL webkit source code for latest iO... by rimantas on Friday May 06, 2011 @01:46PM (#2521762)
Wow. I am pretty sure anyone with this kind of attitude would not work on any project together with guys from Apple.
Re:Apple not providing LGPL webkit source code for latest iO... by jrockway on Friday May 06, 2011 @01:48PM (#2521777)
Apple forked Webkit from KHTML. Google contributes to Webkit. Should the original KHTML and the contributors from Google be deprived of the rights that the LGPL gives them, simply because Apple "owns" the project?

If Apple wants to own Webkit, then answer is simple: require a copyright assignment letter with each patch. Then they can relicense the code whenever they want.

Re:Apple not providing LGPL webkit source code for latest iO... by rimantas on Friday May 06, 2011 @02:08PM (#2521858)

  Apple forked Webkit from KHTML. Google contributes to Webkit.
So? I don't get, why this "forked form KHTML" comes up so often, and how is it relevant. Did Apple ever claim to invent Webkit? Not to my knowledge. What I do know, that a few years ago when Google had no Android and no Chrome Apple was already making Webkit the best rendering engine out there.

But that's completely besides the point. I just cannot imagine someone working on the same project and ready to sue fellow developer's company just because they did not release the source on the same day.

  Then they can relicense the code whenever they want.
If other comments are right, LGPL does not say they must release the source together with a product.
Re:Apple not providing LGPL webkit source code for latest iO... by jrockway on Friday May 06, 2011 @02:32PM (#2521942)
What I'm saying is that the people who wrote KHTML have copyright over Webkit. They released their code under the LGPL, and its Apple's obligation to honor this license until they remove all the original code or get contributers to sign a copyright assignment form. That's how open source projects work: either all the code is owned by some central entity, or the code is owned by the various contributers. When the code is owned by the contributers, your patch is considered a derivative work (for the purpose of copyright) of the other copyright holders' work, so you have to follow the license. On the flip side, if every patch has documentation saying that the central authority (the FSF, the Apache Foundation, etc.) has copyright, then that central authority can relicense however they want. For example, Emacs is now GPLv3, even though most of the code was written well before the GPLv3 existed.

In the case of Webkit, Apple does not require copyright assignment. The code was not originally theirs - their version of Webkit is a fork of KHTML, and so the copyright from KHTML is in force. They have to follow the LGPL, because otherwise they have no legal right to use the code in their products.

That's all I'm saying: the question was "who has a legal claim over Webkit", and my answer was "everyone who's contributed".

The LGPL allows Apple to keep the rest of their stack that links against Webkit proprietary. However, they have to release their changes to Webkit.

Here is the exact wording from the LGPL v2:

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Re:Apple not providing LGPL webkit source code for latest iO... by GHFigs on Friday May 06, 2011 @04:00PM (#2522250)
The LGPL allows Apple to keep the rest of their stack that links against Webkit proprietary. However, they have to release their changes to Webkit.

Quite right, but for this point of pedantry: Apple's fork of KHTML is known as WebCore. That part is LGPL. WebKit (the encompassing project) is BSD and always has been. Safari (the browser) is proprietary.

As far as I can tell, Apple's changes to WebCore are in the public repo. e.g.

http://trac.webkit.org/browser/trunk/Source/WebCore/renderin... Revision 85964, 48.1 KB (checked in by [email protected], 63 minutes ago)

Re:Apple not providing LGPL webkit source code for latest iO... by nikcub on Friday May 06, 2011 @03:00PM (#2522066)
>That's how open source projects work

Just to clarify, that is how GPL licensed software works. There are a lot of different open source licenses that do not require anything.

Re:Apple not providing LGPL webkit source code for latest iO... by jrockway on Friday May 06, 2011 @03:05PM (#2522082)
This is not specific to the GPL. You can't change the license unless the copyright owners agree. That applies for any software license or really anything copyrighted.

Some things are easy because the license specifically permits it: you can GPL a BSD-licensed project, for example. In that case, the agreement from the copyright holders comes in the form of the terms of the license.

Re:Apple not providing LGPL webkit source code for latest iO... by dkersten on Friday May 06, 2011 @08:35PM (#2522951)
But you cannot relicense a BSD-licensed project as GPL because only the original rights-holder can do that. You can apply the GPL on top of the BSD license because the GPL is more specific than the BSD license (ie GPL is a restricted subset of the BSD license, kinda). You must still make the original BSD-licensed code available under the BSD license.
Re:Apple not providing LGPL webkit source code for latest iO... by IgorPartola on Friday May 06, 2011 @04:05PM (#2522268)
Exactly. BSD/MIT/Apache != Public Domain.
Re:Apple not providing LGPL webkit source code for latest iO... by djcapelis on Friday May 06, 2011 @02:34PM (#2521953)
It comes up because Apple is violating the license they agreed to when they started distributing the KHTML sourcecode under the name webkit. And yes, the LGPL requires you to release the code, not wait weeks or months.
Re:Apple not providing LGPL webkit source code for latest iO... by nkassis on Friday May 06, 2011 @02:36PM (#2521960)
They have to be made available. You can ship a binary with a link to the code for example. But I do believe it's supposed to be available from the day the binaries are out.
Re:Apple not providing LGPL webkit source code for latest iO... by rimantas on Friday May 06, 2011 @02:45PM (#2521997)

  But I do believe it's supposed to be available from the day
  the binaries are out.
So, does anyone knows for sure?
Re:Apple not providing LGPL webkit source code for latest iO... by jrockway on Friday May 06, 2011 @03:07PM (#2522093)
"4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange."

"Accompany it" is the key phrase. The source needs to be released at the same time as the binaries.

Re:Apple not providing LGPL webkit source code for latest iO... by allwein on Friday May 06, 2011 @04:15PM (#2522311)
Apparently you stopped reading to soon.

Section 6 states: " As an exception to the Sections above, you may also compile or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications.

You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things:"

And 6B specifically says: "b) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution."

So, since Apple is not distributing just the library binary on its own, but rather as part of Safari, Section 6 excepts Section 4. And all they must do, according to 6B, is accompany the work with a written offer (which it does, see Settings/General/Legal) to provide the source. Since no one has specified that they've written to Apple and been denied, they are not in violation of the license.

Re:Apple not providing LGPL webkit source code for latest iO... by aplusbi on Friday May 06, 2011 @05:12PM (#2522500)
I think you are misinterpreting section 6. Section 6 is about the requirements for software that use the library. Specifically section 6 is about software that statically links to the library (section 5 is about dynamic linking). If you statically link to the library, the resulting binary contains the library and you are required to provide object files so that a user can relink with a different (and hopefully compatible) version of the library.

In the case of Apple, they have made modifications to the library itself. They are then using the library, with modification, in Safari. Safari can be released under any license as outlined in section 5/6 but not the modifications. Those need to be released.

Re:Apple not providing LGPL webkit source code for latest iO... by sp332 on Friday May 06, 2011 @03:01PM (#2522070)
Re:Apple not providing LGPL webkit source code for latest iO... by rimantas on Friday May 06, 2011 @03:55PM (#2522236)
And this helps how exactly? I know what GPL and LGPL is, I was asking, why few there "believe" and "think" instead of quoting.
Re:Apple not providing LGPL webkit source code for latest iO... by tvon on Friday May 06, 2011 @01:41PM (#2521737)
Without looking I think Google is probably the #1 contributor at this point, with Apple being #2.
Re:Apple not providing LGPL webkit source code for latest iO... by alanh on Friday May 06, 2011 @03:06PM (#2522089)
Curious why you say that, as Chrome is definitely a different project than WebKit (obviously they use it, but they defer rendering issues to the main WebKit tracker), and I’m not sure how much Google throws at WebKit. Also, do you me currently, or cumulatively?
Re:Apple not providing LGPL webkit source code for latest iO... by bzbarsky on Friday May 06, 2011 @03:31PM (#2522158)
If you measure by number of commits (whatever that's worth), data is at http://neugierig.org/software/chromium/notes/2010/02/webkit-...

So the answers for "currently" and "cumulatively" differ at least by this metric. And the metric itself is questionable, as the blog post says.

Re:Apple not providing LGPL webkit source code for latest iO... by msbarnett on Friday May 06, 2011 @01:35PM (#2521710)
But surely openness is a spectrum, and if they've released versions in the past, and they claim they will be releasing this one, then that still counts as being "open"?
Re:Apple not providing LGPL webkit source code for latest iO... by Macha on Friday May 06, 2011 @02:14PM (#2521878)
But the conditions of the (L)GPL is that they are _required_ to do so when they release the source at the same time. Releasing it later is more open than not releasing it, but it's still not allowed with the (L)GPL.
Re:Apple not providing LGPL webkit source code for latest iO... by bricestacey on Friday May 06, 2011 @02:33PM (#2521947)
It's not about being "open". Its about following the terms of the license. And I believe the only way to enforce a license is through litigation so a lawsuit should be expected.
Re:Apple not providing LGPL webkit source code for latest iO... by rimantas on Friday May 06, 2011 @01:47PM (#2521769)
Anything related to Apple is always a good source for some sensationalist piece.
Re:Apple not providing LGPL webkit source code for latest iO... by icefox on Friday May 06, 2011 @01:40PM (#2521733)
Actually no, under the GPL they don't have to put the source code on the web. They just have to make it accessible when you request it. If no one requests it then they really don't have to put anything on the web. From a community karma perspective it is good to put up the source when new binaries go out.
Re:Apple not providing LGPL webkit source code for latest iO... by bad_user on Friday May 06, 2011 @02:22PM (#2521911)
Slightly wrong, when distributing the binaries you either have to:

     (a) distribute the source code immediately, 
         along with the binary
     (b) provide a written offer in which you promise 
         to distribute the source-code to anyone 
         who asks in a timely manner
(b) is important because if you fail to provide that written offer as soon as you start distributing the binary, then you're not complying with the GPL.

I'm not in the know if Apple provided such offer, HTC on the other hand ...

And I'm pretty sure somebody requested it by now -- it's not like they are the only contributers to WebKit that would want to merge Apple's changes in master.

In the case of a lawsuit you also have to explain what took you so long to release the source-code -- timely manner is very relative, and in software when things move so fast a couple of months is not soon enough.

I do feel that Apple is somewhat morally justified and should be granted benefit of the doubt, in this particular case, since they invested in WebKit so much. But WebKit got so valuable precisely because it is open-source such that it can be a defacto standard for mobiles. Apple is also not the sole contributer, and they benefited from the work of others, so I don't see why they aren't playing nice.

Also, lots of double standards floating around -- I'm seeing some people that cried wolf on Google's actions regarding postponing the release of Android 3.0, although they are complying with the licenses involved and although they had perfectly understandable business reasons for doing so -- those people are actually trying to justify Apple's actions right now.

I don't know why we treat these stories like some kind of sport, in which everyone cheers for their favorite, but we do, although there isn't anything to gain unless you're a shareholder.

Re:Apple not providing LGPL webkit source code for latest iO... by Someone on Friday May 06, 2011 @02:40PM (#2521974)
I'm not in the know if Apple provided such offer

They do. In settings, General -> Legal one finds:

The WebKit, WebCore and JavaScriptCore software is open source software [...] You may obtain a complete machine-readable copy of the source code for the LGPL-licensed portions under the terms of LGPL, without charge except for the cost of media, shipping, and handling, upon written request to Apple.