search

whoosh-community / whoosh

Whoosh is a fast, featureful full-text indexing and searching library implemented in pure Python.
Other
240 stars 36 forks source link

Current state of this project #561

Open benzkji opened 4 years ago

benzkji commented 4 years ago

hi there. I use woosh together with django haystack in almost all my projects where an indexed search is needed. Instead of configuring services like elastic or solr, just drop in woosh, define indexes, done.

but, I wonder if there are plans keeping this project alive? I could help on the maintainer side, but are not experienced enough for the more advanced technical details...

thank you for your work!

benzkji commented 4 years ago

also, a release would be nice, has there been done some work in this direction: https://www.python.org/dev/peps/pep-0541/#how-to-request-a-name-transfer

nijel commented 4 years ago

See https://github.com/whoosh-community/whoosh/issues/544 for the discussion, but things are not really moving since then. I'm not sure if any progress was done on https://github.com/whoosh-community/whoosh/issues/559

nijel commented 6 months ago

@fortable1999 Perhaps it's time to archive this repository so that we don't waste contributors' effort to create pull requests that will not be reviewed?

ZeroCool940711 commented 6 months ago

Hi there @nijel ,not sure if it is okay for me to say this here but I plan to revive this repo since I use whoosh for several private projects and I like it quite a lot. I made a fork of mchaput/whoosh repo, which seems to be a little bit ahead of whoosh-community/whoosh and I made it available at Sygil-Dev/whoosh-reloaded. I plan to incorporate all the pending PRs and changes from both repositories into my fork. I welcome any contributors that want to help with the revival of Whoosh, so, feel free to do PRs in there. I was also considering the idea of asking @fortable1999 to transfer the ownership of the whoosh-community/whoosh repo to me or someone else so we can maintain it but since they seem to have no activity on GitHub for more than a year I think it's safe to say that it is something unlikely to happen.

nijel commented 6 months ago

I think it's okay to point people to an active fork. This was a community-driven effort when @mchaput was not responsive on Bitbucket. We've merged some pending fixes, but I have no clue how this fork compares to https://github.com/mchaput/whoosh which was created later.

I no longer use Whoosh and I don't have enough privileges to make any changes to this organization, repository or PyPI package.

nijel commented 4 months ago

I've just asked GitHub is there is some way to get controlling of this organization. If it is possible, I'm happy to include @ZeroCool940711, and he can make this repository back alive. If not, I think the best approach is to abandon this organization.

ZeroCool940711 commented 4 months ago

@nijel let me know what GitHub tells you, I will gladly help with whatever I can to revive Whoosh. I think it would be better to get access to this organization and repo to continue working on it instead of working on a fork since we would be able to keep everything it has like stars, fork network and other things, it's not the same as starting from scratch on a fork of a fork since forks have way less visibility on GitHub and Google, a fork of a fork has even less visibility, from what I see the Sygil-Dev/whoosh-reloaded fork doesn't even show on GitHub if you search for it by name, even on Google I can find the Sygil-Dev organization profile and the repo is mentioned on some results but the repository itself is not showing on Google.

nijel commented 4 months ago

Okay, the only thing they can do is contacting the current owner. Unless there is somebody besides @fortable1999, this will not really bring us anywhere.

Therefore, I've updated the README in https://github.com/whoosh-community/whoosh/commit/baa4d577fdb34bfcf30547c8c6bf853fffeb7fe0 to reflect the current situation.

You can claim the package on PyPI, there is an existing workflow for that: https://peps.python.org/pep-0541/#continue-maintenance

ZeroCool940711 commented 4 months ago

Thanks @nijel for the time and effort put into helping with this. I have gone and submitted an issue on the Pypi repository to request a transfer for the Whoosh project to my Pypi account so I can continue to maintain Whoosh, if it is approved I will be renaming the Sygil-Dev/whoosh-reloaded repository to just Sygil-Dev/whoosh and publish the new releases to Pypi while keeping the old versions. I also went and invited you to the Sygil-Dev/whoosh-reloaded repository and gave you write access to it in case you want to contribute to it. You can also contact me on discord if you want to discuss anything. Any contributor that want to contribute to the Sygil-Dev/whoosh-reloaded can contact me or mention me here, previous contributors that had write access here or were actively contributing to the project in the past can request for write access to the Sygil-Dev/whoosh-reloaded but I think just opening a PR on the repository will be enough in most cases since I accept all kind of contributions and I usually accept most PRs (except those that are spam or broken).

nijel commented 4 months ago

Thanks for inviting me, but I'm not really interested in contributing to Whoosh. I already have enough of Python modules to take care of, and these are the ones I actually use.