Licensing

[Sebastian Oerding <se...@robotron.de>]

Hello,

I wondered about the licence of the Apache DS. As far as I know, it is 
ASF 2.0. However the apacheds-all includes for example code from the 
Bouncycastle project for parsing ASN1. Hence the licence for the 
apacheds-all must contain the original licence as far as required by the 
MIT licence of Bouncycastle.

To make it more clear: You may sublicence code which is published under 
a MIT Licence. However you MUST include the relevant portion of the MIT 
licence in your licence in this case (the important item is: "The above 
copyright notice and this permission notice shall be included in all 
copies or substantial portions of the Software", see the MIT licence 
below).

-> MIT Licence:

The MIT License (MIT)

Copyright (c) <year> <copyright holders>

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to 
deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING 
FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

With regards
Sebastian

Re: Licensing

[Sebastian Oerding <se...@robotron.de>]

You are completely right. I created a ticket: 
https://issues.apache.org/jira/browse/DIRSERVER-2006

Regards Sebastian

Am 26.09.2014 09:38, schrieb Emmanuel Lécharny:
> In any case, the BouncyCastle license is derived from MIT, it's not a 
> pure MIT license. Including BC License is the way to go. 

Re: Licensing

[Emmanuel Lécharny <el...@gmail.com>]

Le 26/09/14 07:55, Sebastian Oerding a écrit :
> Hello,
>
> I wondered about the licence of the Apache DS. As far as I know, it is
> ASF 2.0. However the apacheds-all includes for example code from the
> Bouncycastle project for parsing ASN1. Hence the licence for the
> apacheds-all must contain the original licence as far as required by
> the MIT licence of Bouncycastle.

In any case, the BouncyCastle license is derived from MIT, it's not a
pure MIT license. Including BC License is the way to go.

Re: Licensing

[Emmanuel Lécharny <el...@gmail.com>]

Le 26/09/14 07:55, Sebastian Oerding a écrit :
> Hello,
>
> I wondered about the licence of the Apache DS. As far as I know, it is
> ASF 2.0. However the apacheds-all includes for example code from the
> Bouncycastle project for parsing ASN1. Hence the licence for the
> apacheds-all must contain the original licence as far as required by
> the MIT licence of Bouncycastle.
To make it more clear: You may sublicence code which is published under
a MIT Licence. However you MUST include the relevant portion of the MIT
licence in your licence in this case (the important item is: "The above
copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software", see the MIT licence
below).

You are damn right !


Can you fill a JIRA about it ?

Thanks for teh heads up !