-
Notifications
You must be signed in to change notification settings - Fork 760
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
Official Apache 2.0 License Transition #697
Comments
Yes, I consent to the change to the Apache 2.0 license. |
Yes, I consent to the change to the Apache 2.0 license |
1 similar comment
Yes, I consent to the change to the Apache 2.0 license |
I'm fine with it either way… but I'm a bit confused because I don't ever recall contributing code to this project and indeed the contributors list does not list me as being a contributor. So my consent or refusal is dubious at best. |
Yes, I consent to the change to the Apache 2.0 license |
2 similar comments
Yes, I consent to the change to the Apache 2.0 license |
Yes, I consent to the change to the Apache 2.0 license |
I am fine with it.
Pb
…On Fri, May 21, 2021, 8:09 PM Robert Xiao ***@***.***> wrote:
Yes, I consent to the change to the Apache 2.0 license.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#697 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC4OPZCTLRMD2ET42PE3F2LTO3Y5BANCNFSM45KBNUIQ>
.
|
Yes, I consent to the change to the Apache 2.0 license |
@sjlongland Thanks for PR #272 The contributor list on github only shows the top 100 contributors, and I found that even the contributor counter undercounts the number of contributors |
Yes, I consent to the change to the Apache 2.0 license. |
Yes, I consent to the change to the Apache 2.0 license |
2 similar comments
Yes, I consent to the change to the Apache 2.0 license |
Yes, I consent to the change to the Apache 2.0 license |
Yes, I consent to the change to the Apache 2.0 license
… On May 21, 2021, at 21:15, Will Stott ***@***.***> wrote:
Yes, I consent to the change to the Apache 2.0 license
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Yes, I consent to the change to the Apache 2.0 license |
Yes, I consent to the change to the Apache 2.0 license
…On Fri, May 21, 2021 at 6:26 PM Masashi Shibata ***@***.***> wrote:
Yes, I consent to the change to the Apache 2.0 license
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#697 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGJNUS2476HQFWGUGNDKALTO4B37ANCNFSM45KBNUIQ>
.
|
Yes, I consent to the change to the Apache 2.0 license |
Yes, I consent to the change to the Apache 2.0 license. |
3 similar comments
Yes, I consent to the change to the Apache 2.0 license. |
Yes, I consent to the change to the Apache 2.0 license. |
Yes, I consent to the change to the Apache 2.0 license. |
Yes, I consent to the change to the Apache 2.0 license |
Yes, I consent to the change to the Apache 2.0 license. |
Yes, I consent to the change to the Apache 2.0 license
…------
Truong Hua
M: 09 7997 9779
E: ***@***.***
C: calendly.com/truonghua (book meeting with me here)
Lv 5, La Bonita Building, Nguyen Gia Tri street, Binh Thanh District, Ho
Chi Minh City, Vietnam
www.youthdev.net
On Sat, May 22, 2021, 09:54 bpmckinnon ***@***.***> wrote:
Yes, I consent to the change to the Apache 2.0 license
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#697 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPPDE7BIB65OXTDSBTIZO3TO4MHDANCNFSM45KBNUIQ>
.
|
Yes, I consent to the change to the Apache 2.0 license. |
1 similar comment
Yes, I consent to the change to the Apache 2.0 license. |
Thanks to everyone's effort here, we are nearly done with the license change process! The unfortunate news is that we are not quite done yet, but we are close. I have classified the contributors who have not replied to the license change below. Most of the non-responsive contributors had their contribution removed, changed, or provided an extremely minor or not novel change. As maintainer of this project, I don't think these contributions should hold back the license change process. However, I identified 3 contributors who I think provided a "substantial" contributions where a new feature was added to websocket-client. I think reverting these contributions would impact how some users use this library, and we might reach this situation if we cannot get consent from these contributors, but I would prefer to try to find alternative means of communication with these contributors to get their consent to the license change. I would appreciate if others are able to help with getting in contact with these 3 contributors! The 3 contributors I am aiming to get license change approval from are: @cmiacz, @jhtitor, and @juhhov. I expect to post an update here in the next 1-2 weeks with the progress on this final stage of the process. In an effort to be as transparent as possible, below are my detailed notes analyzing the contributions of each contributor who did not respond to this thread. Comments on my approach or conclusions are welcome. Status Key
|
Yes, I consent to the change to the Apache 2.0 license. |
1 similar comment
Yes, I consent to the change to the Apache 2.0 license. |
@engn33r just an fyi - you should manually mark 'unhelpful' comments on this thread as 'helpful' |
@graingert yes, I was a bit too optimistic waiting for a response there My current plan is to replace the commits from @jhtitor, but I won't get around to that for another few days. If someone wants to handle that quicker, feel free to submit a PR. Otherwise after I replace that code we should ideally switch this project over to the Apache 2.0 license in early August. |
Yes, I consent to the change to the Apache 2.0 license. |
Yes, I consent to the change to the Apache 2.0 license. |
Due to the ongoing license change process in #697, PR #417 from @jhtitor needed to be removed. PR #417 added SOCKS proxy support using PySocks, which is the most popular Python SOCKS proxy and is used by libraries such as 'requests' and 'urllib3'. However, as of mid-2021, PySocks has not seen any activity since Sep 2019 and has several open issues. Because PySocks does not appear to be maintained and has no forks that are actively trying to replace the old repository, python-socks may be a better choice going forward. Although python-socks is a newer project, it has good code coverage and recent commits from earlier this year (2021).
Thank you contributors - we did it! 🎉🎉🎉 The websocket-client project has now officially transitioned to the Apache 2.0 license with the 1.2.0 release. |
core equivalent of MycroftAI/mycroft-messagebus-client#21 There was an incompability with the latest websocket-client and the messagebus which needed fixing for Linux distro compatibility. Since messagebus-client>=0.9.4 it also supports old websocket client versions this is now safe to do This solves the issues surrounding licensing, see websocket-client/websocket-client#697
core equivalent of MycroftAI/mycroft-messagebus-client#21 There was an incompability with the latest websocket-client and the messagebus which needed fixing for Linux distro compatibility. Since messagebus-client>=0.9.4 it also supports old websocket client versions this is now safe to do This solves the issues surrounding licensing, see websocket-client/websocket-client#697
core equivalent of MycroftAI/mycroft-messagebus-client#21 There was an incompability with the latest websocket-client and the messagebus which needed fixing for Linux distro compatibility. Since messagebus-client>=0.9.4 it also supports old websocket client versions this is now safe to do This solves the issues surrounding licensing, see websocket-client/websocket-client#697
core equivalent of MycroftAI/mycroft-messagebus-client#21 There was an incompability with the latest websocket-client and the messagebus which needed fixing for Linux distro compatibility. Since messagebus-client>=0.9.4 it also supports old websocket client versions this is now safe to do This solves the issues surrounding licensing, see websocket-client/websocket-client#697
core equivalent of MycroftAI/mycroft-messagebus-client#21 There was an incompability with the latest websocket-client and the messagebus which needed fixing for Linux distro compatibility. Since messagebus-client>=0.9.4 it also supports old websocket client versions this is now safe to do This solves the issues surrounding licensing, see websocket-client/websocket-client#697
core equivalent of MycroftAI/mycroft-messagebus-client#21 There was an incompability with the latest websocket-client and the messagebus which needed fixing for Linux distro compatibility. Since messagebus-client>=0.9.4 it also supports old websocket client versions this is now safe to do This solves the issues surrounding licensing, see websocket-client/websocket-client#697
core equivalent of mycroft-messagebus-client/pull/21 There was an incompability with the latest websocket-client and the messagebus which needed fixing for Linux distro compatibility. Since messagebus-client>=0.9.4 it also supports old websocket client versions this is now safe to do This solves the issues surrounding licensing, see websocket-client/websocket-client/issues/697
core equivalent of mycroft-messagebus-client/pull/21 There was an incompability with the latest websocket-client and the messagebus which needed fixing for Linux distro compatibility. Since messagebus-client>=0.9.4 it also supports old websocket client versions this is now safe to do This solves the issues surrounding licensing, see websocket-client/websocket-client/issues/697
core equivalent of mycroft-messagebus-client/pull/21 There was an incompability with the latest websocket-client and the messagebus which needed fixing for Linux distro compatibility. Since messagebus-client>=0.9.4 it also supports old websocket client versions this is now safe to do This solves the issues surrounding licensing, see websocket-client/websocket-client/issues/697
core equivalent of mycroft-messagebus-client/pull/21 There was an incompability with the latest websocket-client and the messagebus which needed fixing for Linux distro compatibility. Since messagebus-client>=0.9.4 it also supports old websocket client versions this is now safe to do This solves the issues surrounding licensing, see websocket-client/websocket-client/issues/697
core equivalent of mycroft-messagebus-client/pull/21 There was an incompability with the latest websocket-client and the messagebus which needed fixing for Linux distro compatibility. Since messagebus-client>=0.9.4 it also supports old websocket client versions this is now safe to do This solves the issues surrounding licensing, see websocket-client/websocket-client/issues/697
core equivalent of mycroft-messagebus-client/pull/21 There was an incompability with the latest websocket-client and the messagebus which needed fixing for Linux distro compatibility. Since messagebus-client>=0.9.4 it also supports old websocket client versions this is now safe to do This solves the issues surrounding licensing, see websocket-client/websocket-client/issues/697
core equivalent of mycroft-messagebus-client/pull/21 There was an incompability with the latest websocket-client and the messagebus which needed fixing for Linux distro compatibility. Since messagebus-client>=0.9.4 it also supports old websocket client versions this is now safe to do This solves the issues surrounding licensing, see websocket-client/websocket-client/issues/697
core equivalent of mycroft-messagebus-client/pull/21 There was an incompability with the latest websocket-client and the messagebus which needed fixing for Linux distro compatibility. Since messagebus-client>=0.9.4 it also supports old websocket client versions this is now safe to do This solves the issues surrounding licensing, see websocket-client/websocket-client/issues/697
core equivalent of mycroft-messagebus-client/pull/21 There was an incompability with the latest websocket-client and the messagebus which needed fixing for Linux distro compatibility. Since messagebus-client>=0.9.4 it also supports old websocket client versions this is now safe to do This solves the issues surrounding licensing, see websocket-client/websocket-client/issues/697
core equivalent of mycroft-messagebus-client/pull/21 There was an incompability with the latest websocket-client and the messagebus which needed fixing for Linux distro compatibility. Since messagebus-client>=0.9.4 it also supports old websocket client versions this is now safe to do This solves the issues surrounding licensing, see websocket-client/websocket-client/issues/697
Hello websocket-client contributors! 👋
After discussion with the community, a consensus decision has been made to move the websocket-client project to the Apache 2.0 license. This issue was created to receive all project contributor’s approval for changing to this open and permissive license.
If you are on the list of contributors below, you can show your approval by commenting on this issue saying “Yes, I consent to the change to the Apache 2.0 license”. That’s all you need to do, but more explanation is below if you want. The deadline is
June 30July 15 2021. If you have not contributed code, please refrain from cluttering this thread. Issue #665 was created for the license discussion if you have general comments on this transition.Why is the license changing? Depending on when you contributed, the project was previously labeled LGPL or BSD. The license history for this project was a bit messy, so with this change we aim to:
Why do I have to approve of the change? To make the license change official, all contributors must agree to have their work relicensed under the new license. That’s how it works in the open source world - your contribution became part of the project, but it still belongs to you.
What if I don’t approve? Please leave a note stating this. Most likely your contribution will be removed from the code base.
Other questions: The process of changing a license can be confusing, so just ask if you have questions. General comments on the transition can be added to issue #665.
Contributors:
Note 1: crossed out names have granted their consent to this change and this post will be edited regularly with updates to the list
Note 2: the contributor list is split up due to the GitHub limit on the number of people that can be tagged in one post
@0qdk4o@2-5
@71FIL@aarondav@abma@achille-roussel@adam-stokes@aeroaks@agalera@aholen@allanlewis@alunduil@aluzzardi@anshulguleria@anuragbeniwal@aoberoi@apple314159@attzonko@atzm@AZaugg@basak@bashlakov@BonkaBonka
@bpmckinnon@brandonmoser@bubbleboy14@bytesofmyself@caseq@c-bata@cdare
@cgtx
@cjds@cjellick@cjhanks
@cmiacz
@Codeglitches@coolyuyuyu@CptPicard
@DaanVanVugt@DainDwarf
@damjanstulicsonos
@dannywillems@danrobinson88@deniskolodin@devmonkey22@dimaqq@dmiyakawa
@drew-gross@dsuch@dwelch91
The text was updated successfully, but these errors were encountered: