Closed egeakman closed 9 months ago
Kindly pinging @bozhodimitrov
To be honest, we should use pre-commit's setup entirely to avoid the current mess (which doesn't even include testing on windows at all)
https://github.com/pre-commit/pre-commit/blob/main/.github/workflows/main.yml
But for now, there is no much point for major changes since the owner of this repository is busy and PyPi updates are not possible anyways.
Also, I don't think that it's a good idea to allow checks on everything. When I get back home, I will push some adjustments to your branch and will merge.
Hi, thanks for getting back!
About the owner not being available, I believe that poses a significant drag on the project. The last release on PyPI was about one and a half years ago and that discourages potential contributors from contributing. So, I have a few questions:
If he is, would he consider:
If he is not, this project is eligible for the implementation of PEP 541.
Quoting PEP 541:
The user of the Package Index is solely responsible for being reachable by the Package Index maintainers for matters concerning projects that the user owns. In every case where contacting the user is necessary, the maintainers will try to do so at least three times, using the following means of contact:
The maintainers stop trying to reach the user after six weeks.
A project is considered abandoned when ALL of the following are met:
All other projects are considered active.
If a candidate appears willing to continue maintenance on an abandoned project, ownership of the name is transferred when ALL of the following are met:
Under no circumstances will a name be reassigned against the wishes of a reachable owner.
I can open a separate issue to further discuss the maintenance of this project. Please let me know.
This project is not mine, so I can't discuss such stuff. I am just a volunteer like you and everyone else who wanted to help with the project. Unfortunately people have limited time for such projects and it affects the development. This is not uncommon for the OSS repositories.
I understand your enthusiasm and drive to help, but please keep in mind that maintaining a project is a responsibility. And the bigger project means bigger responsibility. And I am not talking just for the technical perspective.
So, yes. If you want to raise such issue, go for it. It is always better to have such stuff separate, so they can be addressed individually and the discussions can be on topic.
Updates: