You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The whoosh-community/whoosh fork has been completely abandoned by the current owner by a long time now (5 years) and the last commit done to the repository was also 5 years ago, excluding the one where the Readme.md was updated recently by @nijel who is one of the few people that still have write access to the repository in a limited way.
Talks about the project status has been done in this issue where we agreed that the project has been abandoned by the existing owner @fortable1999, who's last activity on Github was in August 2020 and nothing since based on their Github profile. I provided there a link to a fork I made to continue maintaining Whoosh under the Sygil-Dev organization, which I am a member of and one of the owners as well as an active developer working on several projects in it.
The Pypi project for the name Whoosh points to the whoosh-community/whoosh repository and so we can not use the same name, I made an attempt to rename the project to Whoosh-Reloaded and published the package under said name in Pypi but most people are not aware of it since it is a fork with a different name and Github as well as other sources seem to give lower priority in search results to forks compared to the main repository. We would like to continue maintaining the Whoosh project and as such we would like to get access to the original package name so we can continue to update it and redirect people to the right repository link in case they want to contribute and report issues or request any feature.
As shown in this issue, we have tried to contact the original owner of the repository and we have mentioned them several times with no answer from them.
Code of Conduct
I agree to follow the PSF Code of Conduct
The text was updated successfully, but these errors were encountered:
Project to be claimed
whoosh
: https://pypi.org/project/whooshYour PyPI username
Tukirito
: https://pypi.org/user/Tukirito/Reasons for the request
The whoosh-community/whoosh fork has been completely abandoned by the current owner by a long time now (5 years) and the last commit done to the repository was also 5 years ago, excluding the one where the Readme.md was updated recently by @nijel who is one of the few people that still have write access to the repository in a limited way.
Talks about the project status has been done in this issue where we agreed that the project has been abandoned by the existing owner @fortable1999, who's last activity on Github was in
August 2020
and nothing since based on their Github profile. I provided there a link to a fork I made to continue maintaining Whoosh under theSygil-Dev
organization, which I am a member of and one of the owners as well as an active developer working on several projects in it.The Pypi project for the name
Whoosh
points to the whoosh-community/whoosh repository and so we can not use the same name, I made an attempt to rename the project to Whoosh-Reloaded and published the package under said name in Pypi but most people are not aware of it since it is a fork with a different name and Github as well as other sources seem to give lower priority in search results to forks compared to the main repository. We would like to continue maintaining the Whoosh project and as such we would like to get access to the original package name so we can continue to update it and redirect people to the right repository link in case they want to contribute and report issues or request any feature.Maintenance or replacement?
Maintenance
Source code repositories URLs
Whoosh: https://github.com/whoosh-community/whoosh
Whoosh-Reloaded: https://github.com/Sygil-Dev/whoosh-reloaded
Contact and additional research
As shown in this issue, we have tried to contact the original owner of the repository and we have mentioned them several times with no answer from them.
Code of Conduct
The text was updated successfully, but these errors were encountered: