-
Notifications
You must be signed in to change notification settings - Fork 56
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
Rename to avoid confusion with Leaflet, the mapping library #75
Comments
We picked the current name as we ran a contest back then on twitter for the community to choose the name. They proposed some candidates and then proceeded to vote for the one they liked the most and Leaflet (which was a proposal not made by me, you can find the credits on the app) won the overall poll. Now, i knew about the maps project that was named the same way and considered even changing it another time but i avoided because of some specific reasons:
I can still consider changing it but i'd need community approval, a new name and new branding overall |
@HrX03 thanks for the response! I understand how you want to respect comminity's choice, but they might have not been aware of the existing project, and duplicating the name, opposite to the goal of making it more appealing, now hurts both projects. It's not about copyright of course — but recognition in the open source community matters a lot. |
I agree by that, and of course it kinda hurts the project too as searching "leaflet" on google doesn't bring up the app but the obviously more famous library. I'll see what i can figure out and will keep you updated in case |
Hi @HrX03, can you explain why you picked the name Leaflet for an open source project when there's already a widely popular open source project with the same name, a library for interactive maps that existed for 11 years now?
Please consider renaming the project to avoid confusing users and search engines.
The text was updated successfully, but these errors were encountered: