On Wed, 16 Dec 2020 at 10:50, Luke Seelenbinder
wrote:
>
> > Does the MapLibre initiative plan to fork the related projects from
> > the mapbox/mapbox-gl-* ecosystem?
>
> We do plan to fork Mapbox GL Native. It's not our initial focus, and we don't
> have the resources to manage it just yet, but
Hi Mateusz,
> Does the MapLibre initiative plan to fork the related projects from
> the mapbox/mapbox-gl-* ecosystem?
We do plan to fork Mapbox GL Native. It's not our initial focus, and we don't
have the resources to manage it just yet, but it's definitely in the works.
MapTiler is already
On Tue, 15 Dec 2020 at 22:41, Tom Chadwin wrote:
>
> > Does the MapLibre initiative plan to fork the related projects from
> > the mapbox/mapbox-gl-* ecosystem?
>
> As I understand it, no, only Mapbox GL JS.
I see.
> Mapbox Native went proprietary a few months ago.
I'm late to the party and
> Does the MapLibre initiative plan to fork the related projects from
the mapbox/mapbox-gl-* ecosystem?
As I understand it, no, only Mapbox GL JS. Mapbox Native went proprietary a
few months ago.
Tom
Tom Chadwin, ICT Manager
Telephone: 01434 611530 Mob:
Web:
On Wed, 9 Dec 2020 at 21:38, Jorge Sanz wrote:
>
> Hello OSGeo,
>
> Some of you may have heard about yesterday's announcement regarding Mapbox GL
> JS v2 having a license change[1] from BSD into a closed license. Since Mapbox
> GL JS v1.13 is still Open Source (BSD), several people forked the
Hi Jorge and Luke
Thanks for the activity and welcome MapLibre!
OSGeo is always open to new community projects, please see how you can
apply here:
https://wiki.osgeo.org/wiki/OSGeo_Community_Projects
Please reach out to the board or the incubation committee if you need
more information.
Hi List,
Thanks, Jorge.
> Today, a few community members met to coordinate those initiatives and agreed
> to use the "MapLibre" name as the Github and NPM namespaces to host the
> library's future development.
I'm one of the people that's been working especially to coordinate a unified
