-
Notifications
You must be signed in to change notification settings - Fork 102
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
Dual licensed under GPLv3 and Apache 2.0 #85
Comments
I'm fine with this, but this needs approval from the other contributors too. Let's see if summoning them works: @peterfisher You all have contributed at least one patch. Can you please comment to indicate that you approve of dual-licensing your contribution under the Apache 2.0 license? |
Yes, I didn't go through all the code and just assumed you were the only Thanks Dennis // Jonas On Wed, Aug 5, 2015 at 10:26 AM, Dennis Kaarsemaker <
|
I'm happy with dual licensing. Let me know if any papers need to be signed and scanned etc. |
fine with me. |
Not sure if it works by replaying to the mail... But it's fine by me.
|
Fine with me |
I'm more than happy to dual-license (or even change to Apache 2.0). |
Sounds good to me.
|
Hi Guys, This is not a quorum yet right? We are still missing 2? Cheers, // Jonas On Wed, Aug 5, 2015 at 10:45 PM, Nathan Garabedian <notifications@github.com
|
Sounds good to me |
Looks good to me |
Thanks everyone! I'll close this issue to stop spamming you. All new releases will be dual GPL/Apache. |
At the request of HP, we switch to a dual GPL/APL model to make it possible to use python-hpilo with OpenStack projects. All people who contributed have indicated their approval on #85
Due to incompatibility between GPLv3 and Apache 2.0 it is hard to use python-hpilo from, for instance, OpenStack. It would therefore be helpful if the project code could also be released under a more permissive license, like for instance Apache 2.0 (which is how OpenStack is licensed)
The text was updated successfully, but these errors were encountered: