Hi Christian,
it's what I said in my other e-mail: we should wait that Chronicle fully
switches to Apache (and not dual license).
If they already plan to go to Apache license, IMHO, it doesn't make
sense to use another cat B license: they just have to go to Apache
license if they agree with.
Regards
JB
On 03/25/2016 09:05 AM, Christian Schneider wrote:
As far as I understand it a downstream project would be able to use
chronicle under apache license if it is open source itself.
So it would create problems when integrating Aries rsa into a commercial
product.
I talked to Dan Kulp yesterday and he said that this is a field of use
restriction that is not allowed at apache. Is that correct?
If yes we would have to decline and ask Peter if they are willing to
switch back to Apache License completely. Another possible solution
brought up by Dan was that they could choose a suitable category b
license if they want to exercise more control over their software while
allowing apache use.
Christian
On 24.03.2016 15:15, David Bosschaert wrote:
Hi Christian,
If they relicense for Aries to ASL I would still have the question
whether
I as a user of Aries in some different project can still use this library
under ASL. I mean is the relicensing only valid in the context of the
Aries
project or also in the context of other unrelated downstream projects or
products that use RSA from Aries?
Cheers,
David
On 24 March 2016 at 13:42, Christian Schneider <[email protected]>
wrote:
I just did a POC Aries rsa transport using Chronicle Queue. It is indeed
very fast. I get about 500 000 msg/s for one way calls.
So from a performance perspective I think it would be very
interesting to
have this as a transport.
I am not sure if their licensing works for us though. They have switched
to lgpl mid last year.
The good news is that I was able to get Peter Lawrey to add a special
licensing for open source projects like Aries.
See: https://github.com/OpenHFT/Chronicle-Queue/issues/250
and:
https://github.com/OpenHFT/Chronicle-Queue/blob/master/LICENSE%20for%20Open%20Source%20product%20usage.txt
So we are allowed to use the software under the apache license. Is that
good enough for us to include Chronicle queues into Aries rsa?
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
