-
Notifications
You must be signed in to change notification settings - Fork 48
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
PEP 541 Request: sphinxcontrib-openapi #2463
Comments
I'm hoping to get permission to publish new releases to this [1]. Until that happens, we must install from source. [1] pypi/support#2463 Signed-off-by: Stephen Finucane <[email protected]>
I'm hoping to get permission to publish new releases to this [1]. Until that happens, we must install from source. [1] pypi/support#2463 Signed-off-by: Stephen Finucane <[email protected]>
Hello @stephenfin, it looks like @ikalnytskyi is active in GitHub, hopefully he can add you as a maintainer or owner. |
Hey, I've emailed Ihor and pinged him a few times via GitHub mentions. No luck, unfortunately. I have been able to release packages since but only because he had already configured a GitHub Workflow with a PyPI token. Not a great long term strategy to be relying on though. |
Since Yuray seems to no longer be involved, we will start the reachability process on our end. |
We are working to contact the owner to determine if they're reachable. Disclaimer: We are providing support to the PyPI Administrators to validate this request and make a recommendation on the outcome and actions to be taken. Final determination will be made by the PyPI Administrators when our process is complete. |
Hello everyone, I'm sorry for being unreachable for so long. Unfortunately, my priorities shifted, and I have neither desire nor time to maintain this project at the moment. As I can see, there are no issues with publishing new releases, as the token I previously set up is still working fine. Regardless, I just added @stephenfin as a co-owner on PyPI. |
I got that invite. Thanks, @ikalnytskyi. I think we can close this now. |
Project to be claimed
PROJECT_NAME
: https://pypi.org/project/sphinxcontrib-openapiYour PyPI username
USER_NAME
: https://pypi.org/user/stephenfinReasons for the request
I help maintain the sphinx-contrib organisation on GitHub. We had a request a number of months ago to help maintain the sphinx-contrib/openapi project. I requested that they reach out to the author, https://github.com/ikalnytskyi, directly, which they duly did, however we haven't heard anything back since. The project's dependencies are rather out-of-date but PRs have been proposed to fix these and it's simply a case of merging these. In the absence of https://github.com/ikalnytskyi I'd like to take over maintenance of this project and explore adding additional maintainers myself in short order. Since https://github.com/ikalnytskyi was happy to move the project to the shared GitHub organisation years ago, I suspect they would be okay with this.
Maintenance or replacement?
Maintenance
Source code repositories URLs
https://github.com/sphinx-contrib/openapi
Contact and additional research
Code of Conduct
The text was updated successfully, but these errors were encountered: