Because Whoosh development was already stalled in 2018, and its original developer (Matt Chaput) was not responding to inquiries, a few developers cloned it to
whoosh-community/whoosh on GitHub, and even migrated and triaged the issues from BitBucket. The developers were quite active for a while. Matt Chaput then showed up
in #544 and expressed his intent to work in the new repository as well. I think this was great news to everyone. But apparently he had trouble merging a new development branch he had been working on. He later created a parallel
mchaput/whoosh repository on GitHub, perhaps as a temporary measure when the BitBucket repo became unavailable, but AFAIK no explanation was communicated. It is also unclear (at least to me) what Matt Chaput's plans are with the new branch, and where any contributions to the current branch would stand with respect to that new branch. From there, things seemed to be left in a state of ambiguity and lack of communications. At this moment, people appear to be posting issues to either repository, possibly not knowing which is the main one, and in neither repository are issues really being attended to.
I am under the impression that no one wants to commit efforts to the whoosh-community/whoosh repo because of the current uncertainties. Matt Chaput did amazing work with Whoosh, and it looks like no one would want to do anything that would interfere with his plans whatever they are. It seems to me that just a tiny bit of direction and communication from Matt Chaput might motivate a community of developers to pick up where things were left in 2020.
I hope I'm not misrepresenting any facts or hurting anyone's sensibilities. I'm a Whoosh user and enthusiast, and this is my understanding of the situation solely from reading this forum and GitHub issues!
David.