-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
License? #3
Comments
Hi there! Thanks for the feedback! I'm happy it has been of use to you. Don't worry about the changes. I had a look over your repository, but when I noticed the 2to3 change I knew merging was not going to be easy ;) LightDHT is licensed under the GPL version 2 (including the "or at your option, any later version" bit). I'm really sorry I forgot to include the COPYING file. I'm usually fairly consistent with that, but it must have slipped my mind on this one. You can use this message as a license statement until I have added COPYING to the repository. It should be compatible, but let me know if you require different terms for some reason. Cheers, drxzcl. |
Ah, yes; I only code in Python 3, forgot to mention my repo was bumped That said, I have made more changes than are currently visible in Thanks for the license, delighted to hear it's GPL'd with "future" Best, On Fri, 05 Jul 2013 01:11:39 -0700
|
Hey, thanks for LightDHT! I was looking for a pure-python Mainline implementation for a project I'm working on, and I've been using LightDHT as the DHT backend during development.
The final project is to be AGPL'd, so I'd love to know what the license is for LightDHT: Do I need to rewrite a new lib from the ground up, or is this OSI/GPL compatible?
PS: My version of LightDHT is by now very different from the clone I made of your repo, if I were being more careful I'd have made more atomic commits and suggested some pulls. :( Suffice to say I did find a few bugs.. the chief one being that if peers are removed from a PrefixRoutingTable bucket and leave it empty, then this can lead to failures later when the empty bucket is used to seek peers and turns up empty. A quick patch to check if the bucket's empty when deleting peers fixes this.
The text was updated successfully, but these errors were encountered: