On 25 March 2016 at 08:07, Jean-Baptiste Onofré wrote:
>
> it's what I said in my other e-mail: we should wait that Chronicle fully
> switches to Apache (and not dual license).
>
Dual-license is generally not a problem, I think. If a project is
dual-licensed, for example
+1
2016-03-22 17:43 GMT+01:00 Christian Schneider :
> +1
>
> Christian
>
>
> On 18.03.2016 18:03, Guillaume Nodet wrote:
>
>> I've staged a release of Blueprint CM at
>>https://repository.apache.org/content/repositories/orgapachearies-1062
>>
>> I forgot to release
Closing this vote with 6 +1s.
I'll publish the binaries asap.
Thx !
2016-03-18 18:03 GMT+01:00 Guillaume Nodet :
> I've staged a release of Blueprint CM at
> https://repository.apache.org/content/repositories/orgapachearies-1062
>
> I forgot to release it with the other
Closing this vote with 8 +1s.
I'll publish the binaries asap.
Thx !
2016-03-15 17:24 GMT+01:00 Guillaume Nodet :
> I've staged a vote for the following bundles:
> * proxy-impl 1.0.5
> * jmx-core 1.1.6
> * blueprint-core 1.6.0
> * blueprint-spring 0.2.0
> *
+1
2016-03-16 21:13 GMT+01:00 Grzegorz Grzybek :
> +1 (non-binding)
>
> Guillaume - is there a chance for blueprint-cm:1.0.8 (ARIES-1503)?
>
> regards
> Grzegorz Grzybek
>
> 2016-03-16 17:43 GMT+01:00 Łukasz Dywicki :
>
> > +1 (non binding)
> >
> >
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
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