Maintained?

[schveiguy]

I just came here to report a possible bug on ios, and noticed there already is one -- from 2020: #2246

I'm having the same problem, and people have continued to have this problem.

Looking at the project, it hasn't had a release for almost 2 years. 659 open issues, 114 open pull requests.

Is this project still maintained? I find flatpickr to be one of my go-to solutions, as it's self contained, simple, and works pretty much perfectly. this is the first time I've had a bug with it.

If not maintained, is there a fork somewhere that is?

[artur79]

also curious

[opbod]

See also #1646.

From what I understand it's dead for over 2 years, despite @chmln stating big plans for this library in 2021 per #2479 (comment).
Also, I didn't find proper forks.

https://github.com/t1m0n/air-datepicker might be a good alternative library (MIT licensed).

[chmln]

Hey guys, indeed I'm quite short on time these days but I'm looking for maintainers that can review pull requests and release occasionally. Hoping to find a few people to help out with this soon. The codebase is pretty easy to work with and this project is widely used so I don't think it will die anytime soon

[opbod]

Thanks for your reply @chmln!

Quite some people have volunteered on #1646. Would be great if you could screen who you think makes sense to add as a maintainer as there are 110+ pull request to review 😅

[schveiguy]

@chmln I would suggest you post more solid guidelines for what you expect from new maintainers. That is, are new features OK to merge? What kind of new features? Is it just bug fixes? Would there be anything that you don't want to see happen here?

Handing over the reins can be daunting, and it would also suck to become a new manager to find out the owner doesn't like what you are doing. There are 116 pull requests, and I'm guessing many of them need further attention and directional guidance.

The other option is to let someone else fully take over.

I personally don't think I have the skills nor the time to help out here, unfortunately.

But I will close this, and direct people to continue discussion on #1646.

And thank you for responding!