Hi @reactive-firewall,

We are working to contact the owner to determine if they're reachable and have sent them a courtesy message.

Final determination regarding project ownership will be made when the research process involved in PEP 541 issues is complete.

@Thespi-Brain @reactive-firewall Thank you for contacting me.

I have now retired from software engineering and am unable to maintain this project on PyPI on an ongoing basis.

If it can evolve into better software, I would be very happy.

Should I perform any actions via the PyPI web UI? or is it sufficient to simply indicate my agreement to this request? Please advise on the next steps.

@raimon49 I'm looking to take up maintaining the GitHub repository, (mostly custodial, like reviews and break-fix, not so much new features) if you find this agreeable, that can be handled:

• on the GitHub UI, by inviting me as a collaborator and giving me maintainer + write permissions on the github repository (see https://docs.github.com/en/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository and https://docs.github.com/en/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository). (if you truly wish to wash your hands of it you can also transfer the project, but let's not be hasty)
• Regarding pypi UI, I similarly would need to be invited as a maintainer: (e.g., https://pypi.org/help/#collaborator-roles )

My information for both accounts are in the description of this GHI.

🙇 Thank you for all your work on this project and I hope this helps.

Additionally comments:

If you have any vision/roadmap/etc. for the project I am happy to follow those as a maintainer (besides I can make a private fork for where my vision differs, IF at all, so I want to honor your existing project on behalf of the community, as per the PSF Code of Conduct).

If you rather complete the transfer, I'll work with the Package Index Admins (e.g., @Thespi-Brain, etc.) to complete this PEP541 request. -- Package Index Admins PLEASE ADVISE.

@reactive-firewall Sure, I invited you from your GitHub and PyPI accounts.

If anything is missing, please reply.

If you have any vision/roadmap/etc. for the project I am happy to follow those as a maintainer (besides I can make a private fork for where my vision differs, IF at all, so I want to honor your existing project on behalf of the community, as per the PSF Code of Conduct).

I'm just happy that you're offering to maintain the project 😃 .

I don't have a roadmap for new features or releases. However, if you're interested in more modern Python project management (e.g., support for uv) or release automation, feel free to take the lead.

@reactive-firewall Sure, I invited you from your GitHub and PyPI accounts.

@raimon49
🎉 Confirmed and accepted. 🙇 thank you for your assistance with this. I will start by triaging the open issues and reviewing the open PRs.

If anything is missing, please reply.

I over looked the codecov link, however the free plan only will allow the owner user (e.g., 1 user limit, and github owner is only default admin on projects so 🤷) so I'm not sure how to advise you on that, it is already configured, so no maintenance is needed atm anyway.

I don't have a roadmap for new features or releases. However, if you're interested in more modern Python project management (e.g., support for uv) or release automation, feel free to take the lead.

I do want to migrate the pypi publishing over to the new, and more secure, Trusted publishers workflow, if you are willing:

• see https://pypi.org/help/#trusted-publishers (you can add it now and it will be pending, until next release)

short instructions: under your account settings > publishing > add (add a trusted publisher for the github project)

Settings:
Service: GitHub
PyPl Project Name: pip-licenses
Owner:raimon49 (e.g., b/c your GitHub user is the github project owner)
Repository name: pip-licenses (e.g., the GitHub Repository is the same here)
Workflow name: CD-PyPi.yml (e.g., this is what I will call the file that will be treated as trusted)
Environment name: (e.g., leave empty)

This will ensure no API keys for publishing need to be managed by you going forward, the GitHub action will be trusted.

Additional Comments:

Feel free to check in on the project from retirement anytime, your input will always be appreciated, even if very infrequent.

Once again, I want to thank you for all your work creating this project 🙇

@Thespi-Brain, thank you for your assistance getting me and @raimon49 connected; I will be withdrawing my PEP-541 request soon.

Hope this helps!

@reactive-firewall Codecov's API is unstable and frequently fails even during PRs. Should we stop using it and look for a long-term SaaS alternative? Feel free to modify the workflow as you work on automating the publishing process.

I do want to migrate the pypi publishing over to the new, and more secure, Trusted publishers workflow, if you are willing:

• see https://pypi.org/help/#trusted-publishers (you can add it now and it will be pending, until next release)

short instructions: under your account settings > publishing > add (add a trusted publisher for the github project)

I just added it from the web UI 👍

I'm attaching a screenshot. Please let me know if anything is missing.

Feel free to modify the workflow as you work on automating the publishing process.

I may just do that 🤓

I just added it from the web UI 👍

I'm attaching a screenshot. Please let me know if anything is missing.

👍 looks correct to me. I think we're all set. I'm going to close out this PEP-541 issue now.