You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@doudz expressed that he, unfortunately, don't have enough spare time to spare on actively developing/maintaining zigpy-zigate.
I understand that is also not enough ZHA testers with ZiGate activly volunteering to test new pull requests for regressions, etc..
Wondering if it would be a good idea to do some kind of campaign to try find additional maintainers, volunteering developers that can help with reviewing PRs, verify/commit pull requests + release both development and stable releases on GitHub and/or PyPI?
More volunteering testers are probably wanted too to help offload testing functions/features, regression testing, and possibly also help write down testing procedures and steps needed to allow other novice testers to contribute with testing pull requests.
I'm not suggesting to push out @doudz and not volunteering myself, but don't think any will step up until make a public request for help?
Believe getting more testers onboard might help a little but think ultimately need developers with interest who also use ZiGate hardware.
Guess I'm suggesting asking previous contributors as well as posting some kind of plea for help in both ZiGate and ZHA communities?
As I understand, zigpy "organization" on GitHub was set up for loose collboration and multiple developers already who have access to repositories within the zigpy organization (and matching PyPI published packages) where others are acting as the primary developer, which is a great concept to hopefully avoid having to fork if a developer no longer has interest or time to spend on one of the projects that is part of the zigpy organization. Note that "organization" here just referred to GitHub term for a grouping of Git repositories for collaboration purposes.
I'm sorry, I don't have the skills to maintain the code or make reviews :(
Plus I don't have the time to test, and I don't really wish to as I am trying to keep my Home Assistant instance the most stable as possible.
The best I can do is to open issues (with logs extracts, screenshots etc...), discuss with people to investigate and test the proposed fixes in the context of thoose issues
@doudz expressed that he, unfortunately, don't have enough spare time to spare on actively developing/maintaining zigpy-zigate.
I understand that is also not enough ZHA testers with ZiGate activly volunteering to test new pull requests for regressions, etc..
Wondering if it would be a good idea to do some kind of campaign to try find additional maintainers, volunteering developers that can help with reviewing PRs, verify/commit pull requests + release both development and stable releases on GitHub and/or PyPI?
More volunteering testers are probably wanted too to help offload testing functions/features, regression testing, and possibly also help write down testing procedures and steps needed to allow other novice testers to contribute with testing pull requests.
I'm not suggesting to push out @doudz and not volunteering myself, but don't think any will step up until make a public request for help?
Believe getting more testers onboard might help a little but think ultimately need developers with interest who also use ZiGate hardware.
Guess I'm suggesting asking previous contributors as well as posting some kind of plea for help in both ZiGate and ZHA communities?
As I understand, zigpy "organization" on GitHub was set up for loose collboration and multiple developers already who have access to repositories within the zigpy organization (and matching PyPI published packages) where others are acting as the primary developer, which is a great concept to hopefully avoid having to fork if a developer no longer has interest or time to spend on one of the projects that is part of the zigpy organization. Note that "organization" here just referred to GitHub term for a grouping of Git repositories for collaboration purposes.
Originally posted by @doudz in #93 (comment)
Originally posted by @doudz in #113 (comment)
@fairecasoimeme @MichaelBitard @nlhomme @Jsl-1 @onkelbeh @devbis @badzz @pipiche38 know any potential candidates?
The text was updated successfully, but these errors were encountered: