[legal-discuss] [keystone] ldappool - using MPL licensed code in-tree

Steve Martinelli s.martinelli at gmail.com
Thu May 12 17:03:32 UTC 2016


Morgan Fainberg and I contacted the original author of ldappool and he
agreed to let us maintain the project (provided we keep the list of
contributors and authors).

  - pypi has now been updated accordingly (
https://pypi.python.org/pypi/ldappool)
  - There is a patch to import the code into gerrit (
https://review.openstack.org/#/c/315267/)

Lastly, no changes to the license were made, we're keeping it MPL. We can
fix bugs and release new versions as needed.

On Tue, May 10, 2016 at 12:05 PM, Steve Martinelli <s.martinelli at gmail.com>
wrote:

> A bit of background:
>
> - In order to make keystone py3 compatible, we have to make our LDAP code
> compatible
> - We use two libraries for our LDAP code: python-ldap and ldappool, both
> are not actively maintained
> - python-ldap has a py3 port called pyldap. Great!
> - ldappool does not have a py3 port.
>
> With all that said, ldappool is only a few hundred lines of code. Can we
> pull it in-tree?
>
> It looks like ldappool is MPL licensed:
>   Version: MPL 1.1/GPL 2.0/LGPL 2.1
>
> Exact license for ldappool is here:
> https://github.com/mozilla-services/ldappool/blob/master/ldappool/__init__.py#L1-L35
>
>
> We have a patch that pulls it in tree up for review (with a few changes to
> make it py3 friendly):
> https://review.openstack.org/#/c/311827/3/keystone/common/ldap/ldappool.py
>
>
> stevemar
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/legal-discuss/attachments/20160512/7be755e8/attachment.html>


More information about the legal-discuss mailing list