First off, I'm a huge fan of the project. It does exactly what I need it to do, and much better than other libraries I've tried. It's strictly better than many larger and more active JS search projects in simplicity, speed, and intuitiveness.
I just want to clarify what users of the library should do to get access to updated code - there haven't been any code updates in ~4 years, despite multiple open+unaddressed pull requests in that time span (#91, #84, #74, #72, etc). It seems like there's sufficient community interest in keeping this thing going and growing it, but without the ability to merge code we're kinda at a loss.
So this brings up two paths forward, only one of which we need to bother going down:
- Is it possible to add new maintainers to the project? If so, who is interested and what should that process look like?
- If that's not an option, is there a preferred fork the community can/should use instead? And if there isn't, is there interest in creating one? And if we take this path, is it possible to link directly to the preferred fork from this repo?
( Currently there are 144 forks, and no indication as far as I can see that any of them are intended/ready to take on the maintenance burden: https://techgaun.github.io/active-forks/index.html#farzher/fuzzysort )
Between the two, I personally would prefer the first. Losing the domain expertise and vision, along with introducing a split-brain scenario, seems like a worse outcome to me.
And just to be extra clear, @farzher @kyuwoo-choi - I'm really thankful for all the work you've put in on this. Just want to find a solution where those of us using the project are able to contribute and build on what's here.
First off, I'm a huge fan of the project. It does exactly what I need it to do, and much better than other libraries I've tried. It's strictly better than many larger and more active JS search projects in simplicity, speed, and intuitiveness.
I just want to clarify what users of the library should do to get access to updated code - there haven't been any code updates in ~4 years, despite multiple open+unaddressed pull requests in that time span (#91, #84, #74, #72, etc). It seems like there's sufficient community interest in keeping this thing going and growing it, but without the ability to merge code we're kinda at a loss.
So this brings up two paths forward, only one of which we need to bother going down:
( Currently there are 144 forks, and no indication as far as I can see that any of them are intended/ready to take on the maintenance burden: https://techgaun.github.io/active-forks/index.html#farzher/fuzzysort )
Between the two, I personally would prefer the first. Losing the domain expertise and vision, along with introducing a split-brain scenario, seems like a worse outcome to me.
And just to be extra clear, @farzher @kyuwoo-choi - I'm really thankful for all the work you've put in on this. Just want to find a solution where those of us using the project are able to contribute and build on what's here.