Updated timeline on plugins going public?

[Lndsay]

👋 @incanus @1ec5 Wondering where with finishing the initial wave of plugins, open sourcing this repo, and any next actions? Anything I help with to get this moving?

cc: @ericrwolfe

[incanus]

I've not written any plugins yet; I'm unsure if @ericrwolfe has one. The clustering example code here might be able to be adapted, but I've not attempted that yet.

[1ec5]

This is currently behind some navigation work that I’m finishing up and anything that may come up with the map SDK. A rough outline of what needs to happen, in case someone wants to pick up where I’ve left off in the 1ec5-project branch:

• [ ] Figure out a better way to handle loading and unloading plugins – should it be possible to unload them?
• [ ] Integrate with CocoaPods
• [ ] Document workflow for adding new plugins (framework, demo app, CocoaPods) – possibly script the workflow using xcodeproj
• [ ] Add traffic plugin If we’re pressed for time, we can also take some shortcuts like making the plugin files standalone so that they can be dragged into application targets without the accompanying infrastructure. However, that would require a bit of work to remove the dependencies on PluginKit.

[jmkiley]

Would it be okay make this repo public once I land https://github.com/mapbox/mapbox-plugins-ios/pull/5 , or would it be better if I move #5 to its own project?

[1ec5]

Let’s move #5 to a separate project. It isn’t based on the 1ec5-project, which implements the general framework for any plugin. It appears to implement a specialized subclass of MGLMapView rather than a plugin that could be applied to any MGLMapView. Even with a public plugin project, feel free to create separate projects that use the map SDK in novel ways; there’s no pressure to make everything a plugin.

[jmkiley]

Closing, will track work in #7