[SUGGESTION] Move zigpy-zboss repository to the shared zigpy organization? #17
Comments
|
FYI, while the same people keep working on it, the governance of zigpy organization's libraries as well as many other open-source home automation libraries/projects have officially been moved to a non-profit organization called the "Open Home Foundation": For the full story on that check out these articles and the announcement video during Home Assistant's State of the Open Home:
The Open Home Foundation was created by the same people who founded Home Assistant and it is a new non-profit organization that will manage over 240 open-source Smart Home projects and related standards, specifications, drivers, and libraries, including Home Assistant, ESPHome, ZigPy, Piper, Improv Wi-Fi, with this new non-profit organization having the goal of making sure all those projects follow the fundamental principles of privacy, choice, and sustainability for smart homes. As I understand it, none of the users will be impacted, as the main purpose of the non-profit organization is more or less just there to make sure these open-source projects do not end up being abandoned or sold to commercial entities and licenced changed. So commercial companies (like example Nabu Casa or Kardia AS and others) will still be able to continue utilizing all these projects and libraries in their products as long as they follow the license, just as it is done with other free and open source libraries/projects. The foundation blog post further explains the goal of teaming multiple projects together in a stronger structure: "We’ve done this to create a bulwark against surveillance capitalism, the risk of buyout, and open-source projects becoming abandonware. To an extent, this protection extends even against our future selves—so that smart home users can continue to benefit for years, if not decades. No matter what comes." … "Our aim is to have the resources to be an active political advocate. Serving to educate the public, public servants, and the companies making smart home devices and services, about the importance of open standards, open-source projects, and privacy, choice, and sustainability when it comes to the future of smart homes." PS: The Verge also posted a very nice summary with their added point-of-view of this change and what it means for the future:
|
|
@DamKast Noticed that puddly now posted the question to you if you would like to transfer this repo to the zigpy organization:
|
|
Hey, |
Probably best to reply to puddly here -> #58 |
@DamKast can I suggest that you consider asking/discussing the possibility with puddly of having this zigpy-zboss repository moved from https://github.com/kardia-as/zigpy-zboss moved to the zigpy organization @ https://github.com/zigpy/ on GitHub so that the mainstream copy of this repo will stay there become upstream for shared access together by the collective of developers that make up the zigpy organization?
That is, make puddly and the other administrators from the zigpy project co-administrators of this repository and then have them move this whole repository from https://github.com/kardia-as/zigpy-zboss to https://github.com/zigpy/zigpy-zboss
That "organization" is just GitHub's terminology as I understand it is more or less still only an informal collaboration between like-minded ZHA and zigpy developers in order to collect ZHA and zigpy projects ín one place and shared access rights, (noting that the zigpy organization on GitHub has no public members and that you must be a member to see who’s a part of that organization, which I am not myself).
https://github.com/zigpy/
Note that this does not mean that support for zigpy-zboss have to be implemeneted upstream into Home Assistant's ZHA integration right away. This zigpy-zboss can still remain experimental. I am however sure that it would gain much more attention from additional third-party developers if this repository belonged to the existing zigpy organization.
Most other ZHA related repositories have sooner or later been moved to the zigpy organization over time as a way for like-minded ZHA and zigpy developers that are members of the zigpy organization with yourself included can have shared ownership and access to your zigpy-zboss repository and the other projects for collaboration within that community.
Again, moving this zigpy-zboss repository there could potentially also help both new ZHA/zigpy developers and others to take more notice that this zigpy-zboss radio library project exist (which is much less likely with it remaining here) and hopefully more developers will then eventually be interested to help and assistant with improving and maintaining.
Perhaps ask if could do the same with your nrf-zboss-ncp repo with your reference firmware image for testing?
https://github.com/kardia-as/nrf-zboss-ncp
Hope that you at least will consider this option and if you think it is a good idea then hoping that you all could come to an agreement that will make everyone happy with you continuing this zigpy-zboss repository under the zigpy organization together without getting offended by any ownership conflicts.
Anyway, I believe moving zigpy-zboss is wanted by the overall zha community and would make so more people notice it:
PS: By the way, the same people who are members of that zigpy organization on GitHub also share another GitHub organization called "zha-ng" (guess it is short for "ZHA next-generation"?) which historically previously contains additional early experimental projects before they became mature and was later moved to the common zigpy organization on GitHub:
The text was updated successfully, but these errors were encountered: