-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this project still upkept? #174
Comments
There are 30 pull requests solving several issues of this package, none of which have been even review. For that reason, most people forks the project (there are 206 different forks) and changes whatever suits their needs. It would be nice if @ljagis reviewed those PRs or at least assign someone as project admin, so the repo can still be alive. |
@AdrianCarreno is any of the forks stable and maintained? |
We at @ljagis are no longer actively working with Leaflet, and have had little time to keep this project maintained. I am happy to transfer ownership of the repo and NPM package to a more motivated maintainer. When I am able, I can advertise the open request for a new owner in the README. Until then, if anyone on this issue would like that responsibility, let me know. |
@brandoncopeland can you edit the README then? |
I'll happy to take responsibility on this project |
Since leaflet updated to v1.8.0 (4 months ago) this project does not work correctly any more out of the box (#171).
The last edit seems to have happened 4 years ago.
Would a pull request be accepted or would someone have to fork the project?
The text was updated successfully, but these errors were encountered: