Discussion: Moving to a dedicated org

Question

Discussion: Moving to a dedicated org

Opened this issue a month ago · 15 comments

Hi there,

Seeing that there are new forks happening because of limited capacity around current maintainers, in combination with not enough administrative rights, I suggest we should revive the idea of moving this project to a dedicated org "PyViCare", where maybe the home assistant integration could be located as well. So those are not tied anymore to individuals, but more to a group allowing things move forward without having to constantly adding new libraries/repos/pypi confusing the outside of the community especially new people.

Looking forward to your feedback @crazyfx1 @CFenner @oischinger and especially @somm15 as you would need to transfer the repo.

Tasks:

Create new organisation
Transfer Github repo
Create new pypi release ~~under new name~~
~~Create new pypi release under old name referencing new pipy package.~~

Answer 1 · 2024-08-19T06:15:40.000Z

Yes, this should have been done when we took over from somm15. I hope he is available to transfer.

Answer 2 · 2024-08-19T06:31:29.000Z

That's a great idea, however @somm15 seems not to be active on GH anymore. Alternative could be to create yet another fork on the new org.

I'm about to switch the HA internal integration to a new release from my fork as there are some deprecations and bugs we need to tackle now. But I guess it's no big deal to switch it back again once the new org is created.

Answer 3 · 2024-08-19T08:27:24.000Z

Thank you for your feedback. I created the organization https://github.com/openviess and added you both already. I hope @somm15 is willing to transfer the repo, so links and stars are retained. If we haven't heard for a while, we can also just shift the repo there.

Answer 4 · 2024-08-19T08:36:37.000Z

Create new pypi release under old name referencing new pipy package.

We probably could keep on using https://pypi.org/project/PyViCare/, just need to link to the new repo slug.

Answer 5 · 2024-08-19T20:41:16.000Z

Hello, I'm not dead :-)
I can transfert the ownership to the new org. I don't have time for this project anymore (and for a very long time).

Answer 6 · 2024-08-19T20:44:18.000Z

@woehrl01 Could you please grant me the permission to create repos on the new org? Otherwise, I can't transfer.

Answer 7 · 2024-08-20T06:21:24.000Z

@somm15 I made you an owner as well. Could you add us as owners to the PyPi project as well? That way we can continue to use the same package name.
Thanks!

Answer 8 · 2024-09-04T09:03:30.000Z

@somm15 would you give it another try?

Answer 9 · 2024-09-04T10:54:04.000Z

Well, the issue is still there: "You don’t have the permission to create public repositories on openviess"
You're the only person listed in openviess.

Answer 10 · 2024-09-04T11:02:35.000Z

@somm15 I just saw that there has been a "failed invitation" to your account, can you please accept and then retry?

Answer 11 · 2024-09-04T11:05:13.000Z

It should done now !
Thank you.

Answer 12 · 2024-09-04T11:56:08.000Z

@woehrl01 can we reuse pyvicare on pypi?

Can you add me as a maintainer?

Answer 13 · 2024-09-04T12:02:09.000Z

@CFenner I can't modify the maintainers on pyvicare, @somm15 likely has to give this to you.

Answer 14 · 2024-09-04T12:05:04.000Z

You can push new PyViCare versions to pypi by using the already existing Github actions. No need to be maintainer.

Answer 15 · 2024-09-06T08:47:35.000Z

True, but I think it would be nice to use trusted publishing together with poetry to manage and upload the project.

https://packaging.python.org/en/latest/guides/tool-recommendations/#uploading-to-pypi

For projects hosted on GitHub, it is recommended to use the trusted publishing, which allows the package to be securely uploaded to PyPI from a GitHub Actions job.