search

flutter-mapbox-gl / maps

A Mapbox GL flutter package for creating custom maps
Other
1.04k stars 503 forks source link

Help with repository #1312

Closed srmncnk closed 1 year ago

srmncnk commented 1 year ago

Hi @tobrun, @AAverin,

I feel that this repository has had a lack in activity regarding PR reviews and merges. Given that Mapbox's new repository still lacks stability and web support, I think this repository should and will stay alive for a long time. It should be supported properly.

Would you consider adding additional people to handle the workload? Probably stricter workflow would apply as well. I would be most interested in helping.

Let's talk.

AAverin commented 1 year ago

@srmanc Hi Simon. I think all the work kind of stopped with the anticipation of the new official mapbox plugin. As this repository is based on the mapbox libraries that are effectively deprecated and won't get any support, if you are staying within Mapbox ecosystem it will probably make more sense to migrate to the new official plugin. I understand that it might not yet have all the functionality, but maybe @tobrun will be able to shed some light on the development roadmap there?

For my personal project I am considering to leave Mapbox ecosystem and instead switch to Maplibre as new official Mapbox Flutter plugin didn't reach my expectations and I am not ready to wait too long for it to evolve. In this light, I was suggesting to this repository maintainers to switch to https://github.com/maplibre/flutter-maplibre-gl. Repo is effectively a mirror of this repo codebase, but based on the mapblire native implementations, supported by @m0nac0.

felix-ht commented 1 year ago

Currently only @tobrun can help with that - he is also the only one that can do releases. In the light of his work at mapbox and the release of their own plugin, it is questionable how free he is to keep his involvement with this plugin going.

It would be fantastic if someone else could step in as the maintainer.

I worked a lot on it for sometime to get is feature complete enough to work for my usecase. The plugin is currently working well enough tho - (after fixing the crash also with 3.x) - so i have a hard time to justify spending large amounts of time on this repo. Especially with the offical plugin beeing on the "horizon", however long that might take.

In general - sorry for my/our sluggishness with the PRs @srmanc

I am not super concerned with the lack of support for the native mapbox modules tho. They seem stable and i expect their api to stay stable enough so that the old native code keeps working. So i tend to agree that this plugin will stay active for at least a few years.

AAverin commented 1 year ago

Maplibre native libraries are essentially copies of Mapbox v9. So for the codebase there shouldn't be any change.

What working with maplibre will bring is:

I honestly don't see any reasons to continue development against old mapbox v9 libraries when we have same libraries open-source and supported by the community of maplibre.

Any cons that I am missing here?

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.