Re: [eclipse-pmc] Works-with dependency on WebKitGTK

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

The Mozilla CQ was approved years ago,
before there was such a 3rd party library policy. It should probably also
be reclassified as a works-with dependency. One category of works-with
dependency is where the software requires one of several possible third
party libraries, which I believe is the case here. Interestingly they even
use a web browser as an example in the policy doc:

a) Works-with Dependencies:

i. The Eclipse software does not require
the third party software to be present. If the third
party software happens to be present,
the Eclipse software may call or invoke it.
Example: If a web browser is present,
clicking on URL's in Eclipse will cause the user's
configured web browser to open the URL.

or

ii. The Eclipse software is designed
to work with multiple third party software choices that
provide similar functionality - the
choice of which to use is up to the user. At least one of
those must be a pre-req (see below)
or approved by the EMO for distribution by the
project. Example: If a project requires
a persistence

I think the WebKitGTK case actually
falls into both categories at the moment. It is one of several browser
options, and the Eclipse platform as a whole can continue to function even
without a browser being available at all.

John

Mike Wilson/Ottawa/IBM@IBMCA
Sent by: eclipse-pmc-bounces@xxxxxxxxxxx

02/08/2010 11:10 AM

Please respond to
eclipse-pmc@xxxxxxxxxxx

To	eclipse-pmc@xxxxxxxxxxx
cc
Subject	Re: [eclipse-pmc] Works-with dependency on WebKitGTK

I believe the intent is, over time, for this to become
the basis for the browser plug-in on GTK, in order to avoid the (significant)
time spent every mozilla release dealing with changes in their API. Although
we do currently fall back to the old code, it would largely negate the
value of switching if we were to continue to do this in all future releases.
If we were to flag this as a "works with" dependency now, would
we then have to re-request clearance if the fallback code eventually gets
removed?

Hm... Actually, I don't believe you *need* a web browser on the machine
to run the SDK, at least. Does that mean that the mozilla interface is
also flagged "works with"?

McQ.

John
Arthorne---2010/02/08 10:08:34---Two new CQ's were filed recently for libraries
that SWT wants to use in its Browser widget. The libraries are not strictly
requ

From:	John Arthorne/Ottawa/IBM@IBMCA
To:	eclipse-pmc@xxxxxxxxxxx
Date:	2010/02/08 10:08
Subject:	[eclipse-pmc] Works-with dependency on WebKitGTK

---

Two new CQ's were filed recently for libraries that SWT wants to use in
its Browser widget. The libraries are not strictly required, and SWT will
fall back to using a Mozilla-based browser if the libraries are not available.
Based on this information I believe we should classify these libraries
as a "works with" dependency as defined in the 3rd party dependencies
document [1]. Please follow up here if there are any concerns, questions,
etc, or to give your +1 in favor of this (policy requires discussion on
PMC mailing list). 

https://dev.eclipse.org/ipzilla/show_bug.cgi?id=3780
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=3781

John 


[1] http://www.eclipse.org/org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc

_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc