Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [incubation] Adding dependencies -- abbreviated instructions

Hi David,

 

when introducing new dependencies for which no CQ has been filed (nor approved) so far, checking the license is only part of the process. While I am pretty sure that you cannot use any pre-req dependencies that are GPL (GPL is simply not compatible with EPL), the more time consuming part of the check is the source code scan for copyright and/or IP problems. You therefore need to attach the source code of the component you create the CQ for (and make sure that it is the source code for the version that you are filing the CQ for).

 

Regards,

Kai

 

 

From: incubation-bounces@xxxxxxxxxxx [mailto:incubation-bounces@xxxxxxxxxxx] On Behalf Of David Smiley
Sent: Monday, March 14, 2016 10:17 PM
To: Discussions for new Eclipse projects
Subject: Re: [incubation] Adding dependencies -- abbreviated instructions

 

On Mon, Mar 14, 2016 at 3:37 PM Eike Stepper <stepper@xxxxxxxxxx> wrote:

> (license), and to humbly ask that another PMC member "+1" the CQ.  As an aside -- I think this step ought to be
> eliminated for certain categories of licenses!  Lets stop wasting people's time on both sides.
I'll bring the topic up on the next Architecture Council call. Can you please elaborate on the "certain categories of
licenses" part of your suggestion?

 

It's truly up to the Eclipse's IP Team, not to me.  I would imagine that the more "viral" licenses (e.g. GPL) might require more IP team review than anything else but since I don't do their job, I am not one to say.  As a reviewer of other CQs in my PMC, that's really all I care about.

 

~ David

--

Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker

Back to the top