| Re: [polarsys-iwg] Licenses authorized in Polarsys projects |
|
Given Mike’s answer I think we are good on the LPGL front. Now I know that it is currently not possible to host GPL, yet we know that CDT or other tools interact
with tools that are GPL but are running in a different process. So my question now is the following: -
Could a Polarsys project host p2 metadata (where p2 metadata is defined as being a machine-readable description of a component) that mentions the
existence of a GPL component but yet the component is not stored or obtained from the Eclipse Foundation server?
From: polarsys-iwg-bounces@xxxxxxxxxxx [mailto:polarsys-iwg-bounces@xxxxxxxxxxx]
On Behalf Of Gaël Blondelle Hi Pascal, Others will correct me if I am wrong. A Polarsys project - Can host LGPL code. As soon as it is hosted only under
polarsys.org and does not refer to
eclipse.org in its namespaces. We have a specific case in mind with GPM (http://gforge.enseeiht.fr/projects/gpm/) which is a Topcased project that will migrate to Polarsys soon. GPM relies on dependencies that prevent
it from being licensed under EPL and LGPL seems to be the voice of the project. - Can't mix LGPL and EPL licensed code. I think that the two licenses are not compatible. - May give the possibility for its users to install LGPL dependencies. I think that putting code in a project that enable users to download and install other components under other licenses is not an issue as you don't redistribute
the components and don't link with it explicitly. We have to ask the legal team about that. Do you have a specific case in mind? Best regards, Gaël Blondelle Le 12 juin 2013 à 04:16, Pascal Rapicault a écrit :
Could you please clarify the scope authorized? - Can
a project host LGPL code? - Can
a project distribute LGPL code (like distribute a tool as part ) ? - Can
a project give the possibility for its user to install LGPL dependencies? Also for record, I paste here the segment of text from the minute. RESOLVED, The Board unanimously
approves the use of the “GNU Lesser General Public License (LGPL)” license for projects hosted by the OPEES Industry Working Group. Such projects must be clearly identified as separate and distinct from Eclipse Foundation projects, hosted on a web property
other than eclipse.org, and not using the org.eclipse namespace. From: polarsys-iwg-bounces@xxxxxxxxxxx [mailto:polarsys-iwg-bounces@xxxxxxxxxxx] On
Behalf Of Mike Milinkovich Pascal, As it often happens, the rumour mill is in error. The board has approved the use of the LGPL, in addition to the EPL, for Polarsys. You can find this in the
minutes link below. Look for the name “OPEES”, as that was the previous name of Polarsys. Eclipse working groups which maintain a separate forge and brand identity can ask the Board for some licensing discretion, which must be unanimously approved.
LocationTech is a second example. Hope that helps. From: polarsys-iwg-bounces@xxxxxxxxxxx [mailto:polarsys-iwg-bounces@xxxxxxxxxxx] On
Behalf Of Pascal Rapicault Hi Rumour has it that Polarsys is a special island where a wider variety of OSS license can be used. In fact the craziest rumour mentioned GPL! Could someone clarify what is allowed? Thx Pascal _______________________________________________ |