Re: [DISCUSS] Camel-Extra Licenses

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [DISCUSS] Camel-Extra Licenses

Christian Müller
Administrator
Regarding c):

+1 to move the following components to the official Apache Camel repo (I have also checked the license of the transitive dependencies of these components): camel-couchbase and camel-zeromq


-1 for camel-spring-neo4j because of the following dependency tree::

[INFO] org.apache-extras.camel-extra:camel-spring-neo4j:bundle:2.14-SNAPSHOT
[INFO] +- org.springframework.data:spring-data-neo4j-rest:jar:2.2.2.RELEASE:compile
[INFO] |  +- org.springframework:spring-tx:jar:3.2.9.RELEASE:compile
[INFO] |  +- org.springframework:spring-context:jar:3.2.9.RELEASE:compile
[INFO] |  |  \- org.springframework:spring-expression:jar:3.2.9.RELEASE:compile
[INFO] |  +- org.springframework:spring-beans:jar:3.2.9.RELEASE:compile
[INFO] |  +- org.springframework:spring-aspects:jar:3.1.4.RELEASE:compile
[INFO] |  |  \- org.springframework:spring-context-support:jar:3.2.9.RELEASE:compile
[INFO] |  +- org.springframework:spring-aop:jar:3.2.9.RELEASE:compile
[INFO] |  |  \- aopalliance:aopalliance:jar:1.0:compile
[INFO] |  +- org.springframework:spring-core:jar:3.2.9.RELEASE:compile
[INFO] |  +- org.neo4j:neo4j-kernel:jar:1.8.1:compile
...


org.neo4j:neo4j-kernel:jar:1.8.1 is GNU General Public License, Version 3 [1]. Also the latest version of neo4j-kernel is GNU General Public License, Version 3.

[1] http://search.maven.org/remotecontent?filepath=org/neo4j/neo4j-kernel/1.8.1/neo4j-kernel-1.8.1.pom

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 Mon, Jun 16, 2014 at 12:12 PM, cemmersb [via camel-extra] <[hidden email]> wrote:
Dear all,

after quite some discussions about the current licensing model of Camel-Extra, I've started some work to bring light into the license dependencies.

I've checked the POM and Feature dependencies that apply to the different components and saw three different clusters:

(a) Dependencies to GPL License
Components that have at least one GPL dependency must comply to GPL those are:
* camel-db4o
* camel-esper
* camel-virtualbox
* camel-vtdxml
For those components, we should apply the current GPL license of Camel-Extra. The natural home of these libraries remains within Camel-Extra space

(b) Dependencies to LGPL License
Components that have at least one LGPL and no GPL license must comply with LGPL standards:
* camel-exist
* camel-hibernate
* camel-jboss
* camel-jboss6
* camel-jcifs
* camel-rcode
The current GPL license is still valid. Nevertheless, we should consider the introduction of a second LGPL license to open restrictions for these components. Their natural home remains within Camel-Extra.

(c) Dependencies to ASF License
Components that have no GPL or LGPL license and are maintained under ASF license are:
* camel-couchbase
* camel-spring-neo4j
* camel-zeromq
The original introduction to Camel-Extra was due to underlying GPL / LGPL licenses. Since we have only direct dependencies to ASF license, I would kindly ask to consider a contribution towards ASF Camel.

Please find attached two speard sheets providing further details on my short analysis.

Looking forwards towards any feedback, especially regarding the opening and contribution options.

Kind regards,

Christoph

Camel-Extra_Maven-Dependencies.pdf
Camel-Extra_Feature-Dependencies.pdf


If you reply to this email, your message will be added to the discussion below:
http://camel-extra.1091541.n5.nabble.com/DISCUSS-Camel-Extra-Licenses-tp332.html
To start a new topic under camel-extra, email [hidden email]
To unsubscribe from camel-extra, click here.
NAML

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [DISCUSS] Camel-Extra Licenses

cemmersb
Hi Christian,

thanks for your feedback, … I must have missed this one :-(

So I’ll open two tickets for the migration of camel-couchbase and camel-zeromq. In addition, I’ll adjust the licensing within the camel-extra code base.

Has anyone a suggestion about the timing of the migration and the licensing adjustment? Is 2.14.0 a good version for this change or should we consider this change somewhere within the 2.13.x branch?

Best,

Christoph


On 23 Jun 2014, at 12:30, Christian Müller [via camel-extra] <[hidden email]> wrote:

Regarding c):

+1 to move the following components to the official Apache Camel repo (I have also checked the license of the transitive dependencies of these components): camel-couchbase and camel-zeromq


-1 for camel-spring-neo4j because of the following dependency tree::

[INFO] org.apache-extras.camel-extra:camel-spring-neo4j:bundle:2.14-SNAPSHOT
[INFO] +- org.springframework.data:spring-data-neo4j-rest:jar:2.2.2.RELEASE:compile
[INFO] |  +- org.springframework:spring-tx:jar:3.2.9.RELEASE:compile
[INFO] |  +- org.springframework:spring-context:jar:3.2.9.RELEASE:compile
[INFO] |  |  \- org.springframework:spring-expression:jar:3.2.9.RELEASE:compile
[INFO] |  +- org.springframework:spring-beans:jar:3.2.9.RELEASE:compile
[INFO] |  +- org.springframework:spring-aspects:jar:3.1.4.RELEASE:compile
[INFO] |  |  \- org.springframework:spring-context-support:jar:3.2.9.RELEASE:compile
[INFO] |  +- org.springframework:spring-aop:jar:3.2.9.RELEASE:compile
[INFO] |  |  \- aopalliance:aopalliance:jar:1.0:compile
[INFO] |  +- org.springframework:spring-core:jar:3.2.9.RELEASE:compile
[INFO] |  +- org.neo4j:neo4j-kernel:jar:1.8.1:compile
...


org.neo4j:neo4j-kernel:jar:1.8.1 is GNU General Public License, Version 3 [1]. Also the latest version of neo4j-kernel is GNU General Public License, Version 3.

[1] http://search.maven.org/remotecontent?filepath=org/neo4j/neo4j-kernel/1.8.1/neo4j-kernel-1.8.1.pom

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 Mon, Jun 16, 2014 at 12:12 PM, cemmersb [via camel-extra] <<a href="x-msg://2/user/SendEmail.jtp?type=node&amp;node=341&amp;i=0" target="_top" rel="nofollow" link="external">[hidden email]> wrote:
Dear all,

after quite some discussions about the current licensing model of Camel-Extra, I've started some work to bring light into the license dependencies.

I've checked the POM and Feature dependencies that apply to the different components and saw three different clusters:

(a) Dependencies to GPL License
Components that have at least one GPL dependency must comply to GPL those are:
* camel-db4o
* camel-esper
* camel-virtualbox
* camel-vtdxml
For those components, we should apply the current GPL license of Camel-Extra. The natural home of these libraries remains within Camel-Extra space

(b) Dependencies to LGPL License
Components that have at least one LGPL and no GPL license must comply with LGPL standards:
* camel-exist
* camel-hibernate
* camel-jboss
* camel-jboss6
* camel-jcifs
* camel-rcode
The current GPL license is still valid. Nevertheless, we should consider the introduction of a second LGPL license to open restrictions for these components. Their natural home remains within Camel-Extra.

(c) Dependencies to ASF License
Components that have no GPL or LGPL license and are maintained under ASF license are:
* camel-couchbase
* camel-spring-neo4j
* camel-zeromq
The original introduction to Camel-Extra was due to underlying GPL / LGPL licenses. Since we have only direct dependencies to ASF license, I would kindly ask to consider a contribution towards ASF Camel.

Please find attached two speard sheets providing further details on my short analysis.

Looking forwards towards any feedback, especially regarding the opening and contribution options.

Kind regards,

Christoph

Camel-Extra_Maven-Dependencies.pdf
Camel-Extra_Feature-Dependencies.pdf


If you reply to this email, your message will be added to the discussion below:
http://camel-extra.1091541.n5.nabble.com/DISCUSS-Camel-Extra-Licenses-tp332.html
To start a new topic under camel-extra, email <a href="x-msg://2/user/SendEmail.jtp?type=node&amp;node=341&amp;i=1" target="_top" rel="nofollow" link="external">[hidden email]
To unsubscribe from camel-extra, click here.
NAML




If you reply to this email, your message will be added to the discussion below:
http://camel-extra.1091541.n5.nabble.com/Re-DISCUSS-Camel-Extra-Licenses-tp341.html
To start a new topic under camel-extra, email [hidden email]
To unsubscribe from camel-extra, click here.
NAML

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [DISCUSS] Camel-Extra Licenses

Christian Müller
Administrator
Let's do it in the 2.14 branch.

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 Mon, Jun 23, 2014 at 12:38 PM, cemmersb [via camel-extra] <[hidden email]> wrote:
Hi Christian,

thanks for your feedback, … I must have missed this one :-(

So I’ll open two tickets for the migration of camel-couchbase and camel-zeromq. In addition, I’ll adjust the licensing within the camel-extra code base.

Has anyone a suggestion about the timing of the migration and the licensing adjustment? Is 2.14.0 a good version for this change or should we consider this change somewhere within the 2.13.x branch?

Best,

Christoph


On 23 Jun 2014, at 12:30, Christian Müller [via camel-extra] <[hidden email]> wrote:

Regarding c):

+1 to move the following components to the official Apache Camel repo (I have also checked the license of the transitive dependencies of these components): camel-couchbase and camel-zeromq


-1 for camel-spring-neo4j because of the following dependency tree::

[INFO] org.apache-extras.camel-extra:camel-spring-neo4j:bundle:2.14-SNAPSHOT
[INFO] +- org.springframework.data:spring-data-neo4j-rest:jar:2.2.2.RELEASE:compile
[INFO] |  +- org.springframework:spring-tx:jar:3.2.9.RELEASE:compile
[INFO] |  +- org.springframework:spring-context:jar:3.2.9.RELEASE:compile
[INFO] |  |  \- org.springframework:spring-expression:jar:3.2.9.RELEASE:compile
[INFO] |  +- org.springframework:spring-beans:jar:3.2.9.RELEASE:compile
[INFO] |  +- org.springframework:spring-aspects:jar:3.1.4.RELEASE:compile
[INFO] |  |  \- org.springframework:spring-context-support:jar:3.2.9.RELEASE:compile
[INFO] |  +- org.springframework:spring-aop:jar:3.2.9.RELEASE:compile
[INFO] |  |  \- aopalliance:aopalliance:jar:1.0:compile
[INFO] |  +- org.springframework:spring-core:jar:3.2.9.RELEASE:compile
[INFO] |  +- org.neo4j:neo4j-kernel:jar:1.8.1:compile
...


org.neo4j:neo4j-kernel:jar:1.8.1 is GNU General Public License, Version 3 [1]. Also the latest version of neo4j-kernel is GNU General Public License, Version 3.

[1] http://search.maven.org/remotecontent?filepath=org/neo4j/neo4j-kernel/1.8.1/neo4j-kernel-1.8.1.pom

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 Mon, Jun 16, 2014 at 12:12 PM, cemmersb [via camel-extra] <<a href="x-msg://2/user/SendEmail.jtp?type=node&amp;node=341&amp;i=0" target="_top" rel="nofollow" link="external">[hidden email]> wrote:
Dear all,

after quite some discussions about the current licensing model of Camel-Extra, I've started some work to bring light into the license dependencies.

I've checked the POM and Feature dependencies that apply to the different components and saw three different clusters:

(a) Dependencies to GPL License
Components that have at least one GPL dependency must comply to GPL those are:
* camel-db4o
* camel-esper
* camel-virtualbox
* camel-vtdxml
For those components, we should apply the current GPL license of Camel-Extra. The natural home of these libraries remains within Camel-Extra space

(b) Dependencies to LGPL License
Components that have at least one LGPL and no GPL license must comply with LGPL standards:
* camel-exist
* camel-hibernate
* camel-jboss
* camel-jboss6
* camel-jcifs
* camel-rcode
The current GPL license is still valid. Nevertheless, we should consider the introduction of a second LGPL license to open restrictions for these components. Their natural home remains within Camel-Extra.

(c) Dependencies to ASF License
Components that have no GPL or LGPL license and are maintained under ASF license are:
* camel-couchbase
* camel-spring-neo4j
* camel-zeromq
The original introduction to Camel-Extra was due to underlying GPL / LGPL licenses. Since we have only direct dependencies to ASF license, I would kindly ask to consider a contribution towards ASF Camel.

Please find attached two speard sheets providing further details on my short analysis.

Looking forwards towards any feedback, especially regarding the opening and contribution options.

Kind regards,

Christoph

Camel-Extra_Maven-Dependencies.pdf
Camel-Extra_Feature-Dependencies.pdf


If you reply to this email, your message will be added to the discussion below:
http://camel-extra.1091541.n5.nabble.com/DISCUSS-Camel-Extra-Licenses-tp332.html
To start a new topic under camel-extra, email <a href="x-msg://2/user/SendEmail.jtp?type=node&amp;node=341&amp;i=1" target="_top" rel="nofollow" link="external">[hidden email]
To unsubscribe from camel-extra, click here.
NAML




If you reply to this email, your message will be added to the discussion below:
http://camel-extra.1091541.n5.nabble.com/Re-DISCUSS-Camel-Extra-Licenses-tp341.html
To start a new topic under camel-extra, email [hidden email]
To unsubscribe from camel-extra, click here.
NAML




If you reply to this email, your message will be added to the discussion below:
http://camel-extra.1091541.n5.nabble.com/Re-DISCUSS-Camel-Extra-Licenses-tp341p342.html
To start a new topic under camel-extra, email [hidden email]
To unsubscribe from camel-extra, click here.
NAML

Loading...