You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like the last merged PR was almost a year ago. Are you still accepting PRs? Are you no longer maintaining this package?
My workplace could use this quite a bit. We've built a couple demos with it, but recently I started skipping this package altogether and instead using Mapbox on its own.
I'd be happy to contribute code or help manage this repo, if you're not interested anymore, @soal.
The text was updated successfully, but these errors were encountered:
Seems like this project is stalled and I'd be interested in contributing to a fork if someone wants to spearhead it (interested still, @ogdenstudios)? I am using this in production (for a veeery tiny project) and have a couple patches I've made but I keep running into issues. I'm also considering ripping it out and going to straight mapbox as well.
Hello! @gorbypark I'm around and still interested. I've also been working on my own lil library, which is mostly just straight mapbox.
I don't have a strong opinion between forking this project and starting a new one, other than I'd like to get some kind of consensus from the previous maintainers before I fork this one and jump off from their work. But to some degree, considering the lack of response, maybe that's fine enough.
Something else that might be worth looking into is how we can get into the Mapbox organization on GitHub. It looks like other community packages are routed through there as well.
Looks like the last merged PR was almost a year ago. Are you still accepting PRs? Are you no longer maintaining this package?
My workplace could use this quite a bit. We've built a couple demos with it, but recently I started skipping this package altogether and instead using Mapbox on its own.
I'd be happy to contribute code or help manage this repo, if you're not interested anymore, @soal.
The text was updated successfully, but these errors were encountered: