Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of christian.mueller@gmail.com
 designates 209.85.192.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <238159616.7583007.1427795882706.JavaMail.zimbra@redhat.com>
References: <30275679.7576098.1427794619148.JavaMail.zimbra@redhat.com>
	<238159616.7583007.1427795882706.JavaMail.zimbra@redhat.com>
Date: Mon, 6 Apr 2015 22:18:03 +0200
Message-ID: 
 <CALvzYd_ZP1f0H2Xc4iMXRfOG58MYWaikss2wA5vKbpJc3OSBHw@mail.gmail.com>
Subject: Re: Licence camel-raspberrypi
From: =?UTF-8?Q?Christian_M=C3=BCller?= <christian.mueller@gmail.com>
To: "dev@camel.apache.org" <dev@camel.apache.org>
Content-Type: multipart/alternative; boundary=047d7bb04304c6d948051313fefd

--047d7bb04304c6d948051313fefd
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello Greg!

No, that's not possible from my point of view. Please have a look at [1].

I think the Apache Camel Extra project is the right place for this
component.

Can Apache projects rely on components whose licensing affects the Apache
product? Apache projects cannot distribute any such components. However, if
the component is only needed for optional features, a project can provide
the user with instructions on how to obtain and install the non-included
work. Optional means that the component is not required for standard use of
the product or for the product to achieve a desirable level of quality.

[1] https://www.apache.org/legal/resolved.html

Best,

Christian
-----------------

Software Integration Specialist

Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member

https://www.linkedin.com/pub/christian-mueller/11/551/642

On Tue, Mar 31, 2015 at 11:58 AM, Greg Autric <gautric@redhat.com> wrote:

> Hi, all,
>
> Just a question about licencing around camel-raspberrypi component I wrot=
e.
>
> this component uses pi4j lib also licensed under ASF licence :
> http://pi4j.com/license.html
> but it uses wiringpi library http://pi4j.com/dependency.html, for static
> dependency
> and this lib is licensed under LGPLv3. (
> https://github.com/Pi4J/pi4j/blob/master/NOTICE.txt, http://wiringpi.com/
> )
>
> camel-raspberrypi component doesn't ship wiringpi lib and end user has to
> install it himself.
>
> how can we manage it ?
>
> can I still push camel-raspberrypi to camel master branch without pb.
>
> by advance, thx,
>
> Greg AUTRIC
> JBoss Middleware Consultant
>
> email   : gautric __at__ redhat __dot__ com
> twitter : @gautric_io
>
> Red Hat Global Services
> Red Hat France SARL                sit: http://www.redhat.fr
> Le Linea, 1 rue du General Leclerc, 92047 Paris La D=C3=A9fense Cedex
> Sent from webmail
>

--047d7bb04304c6d948051313fefd--