Repository navigation
[Previous Contributors Response Needed] Transition python-roborock to Apache-2.0 License #876
Description
We plan to migrate python-roborock from GPL-3.0 to Apache 2.0. To do this we need every contributor's permission to relicense their contributions.
If you are a contributor, please respond to this issue with something along the lines of:
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
(Future contributions will simply be made under the repository's Apache 2.0 license, as with any permissively licensed project — no ongoing obligation is created by consenting here.)
I'd also recommend turning off notifications afterwards so GH does not needlessly ping you!
Contributors
Below is a list of contributors sorted by their active lines of code in the current tree. Note that trivial changes (e.g. adding an enum member or bumping a dependency pin) are generally not copyrightable and would not require consent. For now we are tracking all contributors regardless; if we don't hear back from someone, we will evaluate their actual contributions case by case.
| Contributor | Active lines | Consent |
|---|---|---|
| @allenporter | 24,290 | ✅ |
| @Lash-L | 12,713 | ✅ |
| @tubededentifrice | 2,798 | ✅ |
| @humbertogontijo | 1,433 | ✅ |
| @arduano | 662 | ✅ |
| @andrewlyeats | 587 | ✅ |
| @lboue | 280 | ✅ |
| @pike00 | 247 | ✅ |
| @meilon | 152 | ✅ |
| @Kraina68512 | 85 | ✅ |
| @ximex | 85 | ✅ |
| @regevbr | 58 | ✅ |
| @barneyonline | 44 | ✅ |
| @starkillerOG | 43 | ✅ |
| @Kranzes | 42 | ✅ |
| @shields | 29 | ✅ |
| @johnmph | 20 | ✅ |
| @chrisn-au | 17 | ✅ |
| @rccoleman | 17 | ✅ |
| @Jezza34000 | 16 | ✅ |
| @heikkih | 12 | ✅ |
| @pauloruberto | 8 | |
| @justprox | 8 | ✅ |
| @RaddedMC | 8 | ✅ |
| @NOisi-x | 6 | ✅ |
| @Ongy | 6 | ✅ |
| @user-08-151 | 4 | ✅ |
| @mang1985 | 3 | ✅ |
| @TheMerinoWolf | 2 | ✅ |
| @thibaultmol | 2 | ✅ |
| @shbatm | 1 | ✅ |
| @Christopher-Masselli | 1 | |
| @cryptk | 1 | |
| @stefanroellin | 1 | ✅ |
| @cdce8p | 1 | ✅ |
| @LeonMeistrowitz | 1 | ✅ |
| @bdraco | 1 | ✅ |
| @ethemcemozkan | 1 | ✅ |
| @CountGreven | 1 | |
| @0xEJan | 1 | ✅ |
| @CSdread | 0 |
Bot / automated accounts (no consent needed)
| Account | Active lines | Notes |
|---|---|---|
| semantic-release | 6,320 | Changelog / version bump commits |
| github-actions | 296 | CI-generated commits |
| dependabot[bot] | 19 | Dependency bump commits |
Reasoning:
There's a few reasons:
GPL doesn't actually make a lot of sense on this project. The point of GPL is to add copyleft protection, however, the valuable thing in this repo is the reverse engineered protocol knowledge, which copyleft can't protect anyway and anyone can come and read the code to understand the protocol and reimplement it themselves without any GPL obligation. So GPL mainly adds friction that isn't helpful.
GPL adds a potential barrier for anyone who wants to build off of this library and the work done here.
We want to be very permissive with the work done here, if someone wants to rewrite this library in rust, they should be able to with no barriers.
The primary consumer is Home Assistant, which is Apache 2.0 and I think it makes sense to match HA.
I don't have an explicit purpose (i.e. I need this to be Apache 2.0 so that we can ...), it is more so I think GPL just isn't the right fit and I think it's worth changing. I've had this opinion for a while, but never took the initiative to do it.
Activity
allenporter commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
rccoleman commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
shbatm commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
barneyonline commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
arduano commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license
johnmph commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license
Jezza34000 commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
shields commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
andrewlyeats commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
pike00 commentedon Jul 15, 2026
What's the rationale for this change?
mang1985 commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
NOisi-x commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
Kraina68512 commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
ximex commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
10 remaining items
justprox commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
cdce8p commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
TheMerinoWolf commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
Lash-L commentedon Jul 15, 2026
@pike00 @Ongy @meilon
Good question! I will update the issue to reflect this as well.
There's a few reasons:
GPL doesn't actually make a lot of sense on this project. The point of GPL is to add copyleft protection, however, the valuable thing in this repo is the reverse engineered protocol knowledge, which copyleft can't protect anyway and anyone can come and read the code to understand the protocol and reimplement it themselves without any GPL obligation. So GPL mainly adds friction that isn't helpful.
GPL adds a potential barrier for anyone who wants to build off of this library and the work done here.
We want to be very permissive with the work done here, if someone wants to rewrite this library in rust, they should be able to with no barriers.
The primary consumer is Home Assistant, which is Apache 2.0 and I think it makes sense to match HA.
I don't have an explicit purpose (i.e. I need this to be Apache 2.0 so that we can ...), it is more so I think GPL just isn't the right fit and I think it's worth changing. I've had this opinion for a while, but never took the initiative to do it.
meilon commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
RaddedMC commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
pike00 commentedon Jul 15, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
ethemcemozkan commentedon Jul 16, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
lboue commentedon Jul 17, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
heikkih commentedon Jul 17, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
humbertogontijo commentedon Jul 17, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
regevbr commentedon Jul 18, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
Kranzes commentedon Jul 18, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
CSdread commentedon Jul 19, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.
pauloruberto commentedon Aug 2, 2026
I consent to my contributions to the python-roborock repository being relicensed under Apache 2.0 in place of the current GPL license.