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

[SUGGESTION] Migrate pyconz repository to upstream zigpy organization even if only kept archived for reference #8

Open
Hedda opened this issue Mar 20, 2020 · 2 comments

Comments

@Hedda
Copy link
Contributor

Hedda commented Mar 20, 2020

@Equidamoid even if this project is now abandoned or put on ice until further notice, I still want to suggest that you please consider talking to zigpy organization community developers Adminiuga & dmulcahey about the possibility of you joining the zigpy organization @ https://github.com/zigpy/ as a member even if just to have your pyconz repository here on GitHub moved to that upstream zigpy organization @ https://github.com/zigpy/ as an archive reference so that the mainstream copy of this repo will remain archived there for reference in the upstream zigpy organization and thus access will always be possible upstream zigpy organization so that this is not lost for reference?

That is, move repo from https://github.com/Equidamoid/pyconz to https://github.com/zigpy/pyconz

That way all developers that are members in the zigpy organization including yourself can have repository ownership and access all zigpy related projects which will then be owned by that zigpy organization collaboration community that will hopefully grow over time? Again, even if the pyconz repository would just be an archive reference in this case.

I know that you already seen the related suggestion I posted as an issue in the upstream zigpy repository at zigpy/zigpy#319 where you replied "pyconz in kind of dead right now".

FYI, I posted a similar suggestion in regards to zigpy-cc by sanyatuning and he liked the idea so aksed Adminiuga & dmulcahey who extended an invitation to sanyatuning and the zigpy-cc repo has since been moved upstream to the the zigpy organization, see zigpy/zigpy-cc#13 and zigpy/zigpy#319

Regardless I hope that you could all come to an agreement that will make everyone happy with sharing access to the pyconz repository without anyone getting offended by ownership conflicts.

@Equidamoid
Copy link
Owner

Hi @Hedda,

I don't mind actually. With recent fixes from deconz I even have some hope of resurrecting this idea of dbus(or grpc) to zigbee connection. Or maybe even some combination of rest and websockets.

Additionally I hope I will find time to contribute to other projects (although I kind of oppose the ubiquitous idea of doing everything via mqtt and/or binding it homeassistant...) =)

Thus, let's move it. Do I need to do something for this?

@Hedda
Copy link
Contributor Author

Hedda commented Mar 23, 2020

@Equidamoid Cool! Yes you would first need to talk to @Adminiuga & @dmulcahey about the possibility of you joining the zigpy organization @ https://github.com/zigpy/ and if that is OK with them then after you have joined you will need to transfer a repository to that zigpy organization.

See https://help.github.jp/enterprise/2.11/user/articles/transferring-a-repository-owned-by-your-personal-account/

Might be that they are not reading this here though so might be better of posting to them under zigpy with tags here zigpy/zigpy#319

Again they have recently done so with zigpy-cc repo by @sanyatuning so perhaps he can help too?

Update: @doudz has now also joined and migrated zigpy-zigate too, see zigpy/zigpy-zigate#17

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