Skip to content
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

Campaign to find additional maintainers of this upstream zigpy-zigate repository? #116

Open
Hedda opened this issue Jan 25, 2022 · 2 comments

Comments

@Hedda
Copy link
Contributor

Hedda commented Jan 25, 2022

@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)

Sorry, no time to work on zigate 😞

Originally posted by @doudz in #113 (comment)

I just have no time to work on this repo but PR are welcome :)

@fairecasoimeme @MichaelBitard @nlhomme @Jsl-1 @onkelbeh @devbis @badzz @pipiche38 know any potential candidates?

@nlhomme
Copy link

nlhomme commented Jan 26, 2022

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

@Hedda
Copy link
Contributor Author

Hedda commented Feb 4, 2022

Please also see related discussion -> zigpy/zigpy#880 (ZiGate users help wanted to test ZHA with fork of zigpy-zigate w. patches)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants