RE: [eclipse-pmc] On using WebKitGTK
Note that none of this is the "proposal". The intent here was simply to provide background information for the board. In any case, I've asked Grant to put together an updated version of the content based on your feedback.
"Oberhuber, Martin" ---2010/03/17 02:52:54---+1 on the proposal. Great work!
"Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
RE: [eclipse-pmc] On using WebKitGTK
+1 on the proposal. Great work!
Regarding Jeff's proposal, the wording "reship WebKitGTK" is confusing. We are talking about a pre-req here. All we are going to ship is Java +JNI code that's supposed to link dynamically to the WebKitGTK sharedlibs which are expected to be pre-installed. Or did I miss the point here?
I agree that the answers to a/b/c could better relate to the requirements a/b/c. Rather than in-lining with the requirements, it could also work to re-phrase the req at the beginning of the answer, e.g. a) Pre-req: ....
On section  suggested workarounds, I'm missing a statement that we tried to work with the Mozilla Foundation on freezing the APIs that we need, and what their take was.
From: eclipse-pmc-bounces@xxxxxxxxxxx [mailto:eclipse-pmc-bounces@xxxxxxxxxxx] On Behalf Of Jeff McAffer
Sent: Wednesday, March 17, 2010 2:49 AM
Subject: Re: [eclipse-pmc] On using WebKitGTK
Awesome! Likely the most well researched proposal ever at Eclipse. A couple small tweaks
- Suggest putting a line at the beginning somewhere saying that "The Eclipse Project requests approval to reship WebKitGTK under the LGPL because is addresses critical community needs." Then launch into the whole story.
- "to help in this disregard" --> "to help in this *regard*"
- suggest trimming the answers to a, b, c and putting them with the points. See below. The idea is to give board members something they can easily parse and understand (they don't know the ins and outs of this stuff). If they want more info they can read on.
Anyway, just a suggestion.
On 2010-03-16, at 4:45 PM, Mike Wilson wrote:
The Browser widget is an optional piece of the overall platform. WebKitGTK integration is an enabling adapter that allows the Browser to work on Linux platforms. Without it the vast majority of Eclipse continues to work.
It's been clear for a while now that using XULRunner as the basis for the SWT Browser control on Linux has caused significant problems for our consumers. In current Linux distros, there is a compelling alternative, WebKitGTK, which is licensed under LGPL. The Eclipse Board has recently approved a new policy to allow the use of LGPL APIs in certain circumstances. According to this policy, to approve the request to use the APIs, the board must determine that:
a) The library or application invoked by the APIs is a “pre-req,” as defined in the Eclipse Foundation’s Guidelines for the Review of Third Party Dependencies.
WebKitGTK is the only embeddable web browser that provides a frozen API that is rich enough to meet the Browser's needs and can be counted on to be pre-installed in modern Linux distributions.
b) There is no alternative open source software that provides the same or similar function to the WebKit APIs that can be obtained under a more permissive license.
Despite being optional, the Browser widget is widely used in end-user scenarios. Without the use of WebKitGTK the instability that currently plagues the Browser on Linux will continue and inevitably reduces the consumability of Eclipse as an application platform for both product teams and end-users.
c) The functionality, usability or consumability of the Eclipse project would be severely restricted or reduced without the APIs.
is pleased to make available the supporting information supplied below.
<end here with the rest as an appendix.>
In determining these things the board may rely on information provided by the PMC, and to help in this disregard, the PMC (with the help of our browser guru, Grant Gayed) investigated and
eclipse-pmc mailing list