Documents that span across multiple MapLibre projects
Home Page: https://www.maplibre.org/
License: Creative Commons Zero v1.0 Universal
This repository contains various documents that define the MapLibre Organization such as the Charter, our Code of Conduct, the list of Voting Members, and more.
You also find here the results of past Governing Board elections.
Markdown files in this repo are formatted with markdownlint. If you have formatting problems you can sometimes fix them with:
npx markdownlint-cli *.md --fix
Execution of this - #115
We have a discussion thread for posting messages on social media (Twitter and LinkedIn) at #105, but it is a bit unclear if a post requires an approval and if yes, by whom.
Define some rules for social media posts.
#33 started some documentation of our secrets. I wonder if we should have something like a key manager for MapLibre. The Governing Board members could all have access to that key manager.
In native, the situation is worrying me because we don't have any documentation on how secrets are managed and we will likely not be able to make releases with under the old accounts if something breaks. maplibre/maplibre-native#312
We are going to change permissions to the MapLibre GitHub repos. The new model is repo-centered with at least one admin per repo. The admins have full control over a repo and can invite collaborators and give them write access.
The MapLibre GitHub org will be owned by the members of the MapLibre Governing Board:
All org owners are automatically also repo admins.
For each repo, the Governing Board defines at least one admin. For example, @HarelM might be a good admin for GL JS.
MapLibre's GitHub teams like @maplibre/dev and @maplibre/core will be deleted. This might mean that you loose permissions.
If you have any problems due to the new permissions model, please ping me here or on Slack.
Idea - introduce new plans.
Tasks:
The new plans:
This is just a test of RoadMap under Projects in maplibre repo.
There is a mistake in your map: Crimea is an ukrainian territory, not a russian
Out of nearly 20 repositories, we still have 3 repos that for historical reasons use master branch instead of the main. I would like to coordinate renaming with the active participants. Note that renaming in github already does many things automatically for us.
Once renamed, run these commands locally (assuming you use origin as the remote name):
git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a
git remote prune originif you have a two remotes setup (upstream pointing to the main repo, and origin pointing to your own fork from which you create pull requests), it is a bit different. You should also rename your own fork's default branch (navigate to it in github, and see the notification github will show you)
git branch -m master main
git fetch upstream
git branch -u upstream/main main
git remote set-head upstream -a
git remote prune upstreamcc: last active participants of those repos:
@Brammos @Joxit @OlexandrStepanov @atierian @birkskyum @frankkienl @jutaz @kiibimees @matkoniecz @ntadej @nunojpg @petr-pokorny-1 @rinigus @roblabs @rubenmx @srcejon @thirstycoda @xabbu42
Propose board the bounty system.
Perhaps something like:
Direction with quarterly budget - to be approved by board.
Coordinator approves bounties - and suggest budgets
Maintainers suggest bounties
Fix bounties size ($100, $250, $500, $1k, $2k, $3k)??
Collect who is using bounties how.
Prepare a budget for the months Dec 2022, Jan 2023, Feb 2023. Follows the same logic as the financial report, but instead of looking back into the past, projects the future income and expenses.
Update README in JS + Native + wesite.
Align it to latest plans and discussion.
Voting Members can nominate other people to become Voting Members as well by posting their GitHub handles in this thread until Thursday, August 11th, 2022. The existing Voting Member will then decide online if they grant the nominated people Voting Membership on Thursday, August 18th, 2022 via an online vote.
Set up clockify for time tracking. Tasks shall be used for Native, GL JS, etc, and Projects shall be used for "Maintenance, community, etc".
If you want to get write access to a repo, contact the repo admin. If repo admins give write access to new people, they should:
urbica/martin → maplibre/martin
Martin is one of the most well known tile servers with 83 forks and 741 stars. Martin was written by @stepankuzmin, who has expressed desire to join MapLibre and continue working on it. This project is fairly up to date with web serving code, and uses PostgreSQL as the only data store.
Moving this project to MapLibre would help us combine it with the maplibre/mbtileserver-rs, as was discussed in #30.
Copied from the last section #30
Copyright (c) <year> MapLibre contributors in license file(s) and in the readme./README.md/LICENSELICENSE-MIT and LICENSE-APACHE/CONTRIBUTING.md/.github dir./.github/FUNDING.yml file copied from maplibre-gl-js/funding/CODE_OF_CONDUCT.md# Contributor Covenant[](https://github.com/maplibre/maplibre/blob/main/CODE_OF_CONDUCT.md)Sponsorships checkbox (see also FUNDING.yaml above).Preserve this repository.squash merge. Disable other merge types if possible.Automatically delete head branches.main.#maplibre OSMUS slack channel.@maplibre twitter.If you want to add a repo to the MapLibre GitHub org, please contact a member of the MapLibre Governing Board and ask if your project can be added.
The board member has to make sure that:
Copyright (c) 2022 MapLibre contributors.admin who is ideally not part of the Governing Board.Prepare an initial board pack
With highlights & alerts
Links to reports (quarterly)
Submitted to board members a week before the board
This is the best practice. We could try to go in that direction
The quarterly reports are going to be helpful also for review by sponsors on advisory council
Move the tiers discussion on the maplibre projects (core, supported, hosted) forward and finish it.
https://github.com/birkskyum/maplibre-native-base
The native repo rely on mapbox/mapbox-base, which is abandoned. This is a big problem, because with all our PR's ignore in this upstream repo, we can't maintain the native repo.
Copyright (c) <year> MapLibre contributors in license file(s) and in the readme./README.md/LICENSELICENSE-MIT and LICENSE-APACHE/CONTRIBUTING.md/.github dir./.github/FUNDING.yml file copied from maplibre-gl-js/funding/CODE_OF_CONDUCT.md# Contributor Covenant[](https://github.com/maplibre/maplibre/blob/main/CODE_OF_CONDUCT.md)Sponsorships checkbox (see also FUNDING.yaml above).Preserve this repository.squash merge. Disable other merge types if possible.Automatically delete head branches.main.#maplibre OSMUS slack channel.@maplibre twitter.https://github.com/maplibre/maplibre-rs
MapLibre project is forced to maintain two independent implementations - GL JS (typescript) and Native (C++). This significantly increases the maintenance burden, reduces feature parity, and causes incompatibilities between implementations. The "one code to rule them all" would be an ideal solution to this, but at the moment we do not know if this is possible. MapLibre-rs is an experimental project for community to test a single code-base approach with a long-term potential to overtake the original projects if it can show that it can support all required functionality on all platforms, while also resulting in performance and package-size gains.
Copyright (c) <year> MapLibre contributors in license file(s) and in the readme./README.md/LICENSELICENSE-MIT and LICENSE-APACHE/CONTRIBUTING.md/.github dir./.github/FUNDING.yml file copied from maplibre-gl-js/funding/CODE_OF_CONDUCT.md# Contributor Covenant[](https://github.com/maplibre/maplibre/blob/main/CODE_OF_CONDUCT.md)Sponsorships checkbox (see also FUNDING.yaml above).Preserve this repository.squash merge. Disable other merge types if possible.Automatically delete head branches.main.#maplibre OSMUS slack channel.@maplibre twitter.https://github.com/maplibre/maplibre-react-native (currently at https://github.com/lseelenbinder/maplibre-react-native)
There is no accepted OSS project for using MapLibre in React Native, despite a lot of demand for it. The best option is https://github.com/rnmapbox/maps, but they have formally announced discontinuing support for MapLibre.
This proposal would fork this project, specialize it to MapLibre (and drop support for the Mapbox SDK), and ensure that MapLibre developers using React Native as a solid option going forward.
Relevant Slack discussion: https://osmus.slack.com/archives/C02B2CBSNBU/p1665079311393029
Copyright (c) <year> MapLibre contributors in license file(s) and in the readme./README.md/LICENSELICENSE-MIT and LICENSE-APACHE/CONTRIBUTING.md/.github dir./.github/FUNDING.yml file copied from maplibre-gl-js/funding/CODE_OF_CONDUCT.md# Contributor Covenant[](https://github.com/maplibre/maplibre/blob/main/CODE_OF_CONDUCT.md)Sponsorships checkbox (see also FUNDING.yaml above).Preserve this repository.squash merge. Disable other merge types if possible.Automatically delete head branches.main.#maplibre OSMUS slack channel.@maplibre twitter.We need to set up a private pipeline and process for handling different stages of sponsorship and negotiation, as welll as renewals for the sponsorship.
Process must be documented.
To keep overview of progress - handled by project coordinator who is going to be responsible for that.
At the moment, we take the notes of meetings together in a google doc, then after the meeting I take these notes, edit them a bit, and copy them to GitHub. This requires that I convert them from google doc to markdown which is always a bit painful.
I would like to implement a process which removes the need for conversion from google doc to markdown, or automates it better.
Announce hiring - publish questionary form to collect contact of interested people.
Link the roles.
Mention bounties - for developers.
Message is - this project is stable, we have money to distribute to the community - apply. :-)
I would like to create two pipelines, one for fundraising and one for hiring. Hubspot has deals which can be used for this.
Here is a nice outline how to use hubspot for hiring:
https://aptitude8.com/blog/how-we-use-hubspot-for-recruiting
To create two deals pipelines we have to pay USD 20 per month:
The community together has a lot of experience with native mapping development. It would benefit everyone if we had a way of sharing our good and bad experiences. MapLibre seems to be the ideal place to share experiences publicly. We will set up a format with which people can share what worked for them and what didn't.
There are a few companies that might be interested in sponsoring MapLibre. Reach out to one new potential sponsor.
https://github.com/maplibre/qt-geoservices-maplibre-gl
Qt Location is a popular mapping-agnostic library to integrate maps into Qt application. MapBox GL was one of the most feature-complete plugins but is no longer supported due to licensing changes.
While there is an effort to integrate MapLibre into Qt codebase, having the code outside would not bind us to Qt release schedule.
Copyright (c) <year> MapLibre contributors in license file(s) and in the readme./README.md/LICENSELICENSE-MIT and LICENSE-APACHE/CONTRIBUTING.md/.github dir./.github/FUNDING.yml file copied from maplibre-gl-js/funding/CODE_OF_CONDUCT.md# Contributor Covenant[](https://github.com/maplibre/maplibre/blob/main/CODE_OF_CONDUCT.md)Sponsorships checkbox (see also FUNDING.yaml above).Preserve this repository.squash merge. Disable other merge types if possible.Automatically delete head branches.main.#maplibre OSMUS slack channel.@maplibre twitter.We come from different backgrounds and some technical terms might be used differently in different places. We want to implement a common language such that we are sure that we talk about the same things in a discussion. This can be done for example with a dictionary or some definitions for technical terms.
https://github.com/maplibre/maplibre-gl-native
This is one of the fundamental MapLibre libraries targeting non-browser platforms. It was transferred from MapTiler (thanks!), but we should ensure it confirms to all our standarts.
Copyright (c) <year> MapLibre contributors in license file(s) and in the readme./README.md/LICENSELICENSE-MIT and LICENSE-APACHE/CONTRIBUTING.md/.github dir./.github/FUNDING.yml file copied from maplibre-gl-js/funding/CODE_OF_CONDUCT.md# Contributor Covenant[](https://github.com/maplibre/maplibre/blob/main/CODE_OF_CONDUCT.md)Sponsorships checkbox (see also FUNDING.yaml above).Preserve this repository.squash merge. Disable other merge types if possible.Automatically delete head branches.main.#maplibre OSMUS slack channel.@maplibre twitter.We did not have an Android release since December 2021. Would be great to release the improvements that went into the main branch since then.
$100 (Size: S)
To complete this bounty, the following things have to be done:
android-v* is pushed.android-v9.6.0 is published on GitHub Releases and on Graddle.Show your support for this Bounty with a 👍 if you like it...
Read more about Bounties here: https://github.com/maplibre/maplibre/wiki/Bounty-System.
We have a lot of things we would like, i.e., https://roadmap.maplibre.org/tabs/16-overview and many more.
Currently, no resources are allocated for anything to drive development.
With ESRI's recent adoption of MapLibre, it would arguably make a lot of sense to collaborate with that deep expertise on the compatibility with the ArcGIS stack (on our roadmap)
For the next Governing Board meeting, prepare a financial report for the time period since the last Advisory Council which was on Wed, Sep 7th, 2022.
The financial report will be part of the board pack #126.
We need a process to discuss and reach decisions, and then follow the decisions we take. We concluded that we need a process like Request for Comments (RFC) to discuss topics of limited scope and document the decisions we take. We can take inspiration for example from Rust https://github.com/rust-lang/rfcs or GDAL https://gdal.org/development/rfc/index.html.
Document the roles in organization - for defining paid positions - into the wiki
TL;DR: I have two pain points right now:
MapLibre is a cross-platform map renderer:
maplibre-gl-js works on Firefox, Chrome and Safari (on Android, iOS, Windows, macOS and Linux)maplibre-gl-native works on Android, iOS, Windows, macOS and Linuxmaplibre-rs works on all Browsers and OS from above)In order to compile for Apple we can use Github Actions (free). That only supports x86_64 CPUs so far. Current executors in Github CI are rather slow sadly.
In order to test rendering we need either real GPUs or simulated GPUs. For simulated GPUs we can use the Mesa drivers on Linux. On Windows similar libraries are available for DirectX.
On Apple (iOS/macOS) sadly the world looks different.
In order to reliably test rendering we need CI environments which have an Apple GPU available. Historically OpenGL is supported on Apple. Nowadays Metal is state-of-the-art.
In order to run rendering test e.g. on an iPhone using Metal or WebGL in Safari we need real hardware. Note that WebGL on Safari (macOS) can either use OpenGL or Metal in the background.
I think we definitely need some way to execute rendering tests and build for apple architectures.
Right now we use this for the maplibre-gl-native project. Though the other projects actually also need to create apple builds.
Note that compiling for Apple devices is probably possible from Github CI already through cross-compilation. Running rendering tests is not possible right now.
Also in general speeding up the compilation in Github Actions could be beneficial.
https://github.com/maplibre/maplibre-gl-directions
maplibre-gl-directions renders routing information from various routing providers such as OSRM and Mapbox on top of a MapLibre GL JS map.
Copyright (c) <year> MapLibre contributors in license file(s) and in the readme./README.md/LICENSELICENSE-MIT and LICENSE-APACHE/CONTRIBUTING.md/.github dir./.github/FUNDING.yml file copied from maplibre-gl-js/funding/CODE_OF_CONDUCT.md# Contributor Covenant[](https://github.com/maplibre/maplibre/blob/main/CODE_OF_CONDUCT.md)Sponsorships checkbox (see also FUNDING.yaml above).Preserve this repository.squash merge. Disable other merge types if possible.Automatically delete head branches.main.#maplibre OSMUS slack channel.@maplibre twitter.The MapLibre Voting Members participated in a test vote on the platform opavote.com and except for one typo, there were no problems reported.
In the following days, we will have these polls (Firenze time because this is where FOSS4G is this year...):
Vote about adding one more person to the Voting Members. See #71
The MapLibre Voting Members are asked if they approve the MapLibre Charter #74. Note that changes to the pull request will not be accepted after Tuesday, 23rd, 2022 at 5 PM Firenze time (UTC+2).
The Voting Members elect the MapLibre Governing Board. Self-nominations of the candidates can be found at #78.
WIP
https://github.com/birkskyum/gazetteer moved to https://github.com/maplibre/gazetteer
We currently rely on an abandoned mapbox library, with no way to maintain it: https://github.com/mapbox/gazetteer
Copyright (c) <year> MapLibre contributors in license file(s) and in the readme./README.md/LICENSELICENSE-MIT and LICENSE-APACHE/CONTRIBUTING.md/.github dir./.github/FUNDING.yml file copied from maplibre-gl-js/funding/CODE_OF_CONDUCT.md# Contributor Covenant[](https://github.com/maplibre/maplibre/blob/main/CODE_OF_CONDUCT.md)Sponsorships checkbox (see also FUNDING.yaml above).Preserve this repository.squash merge. Disable other merge types if possible.Automatically delete head branches.main.#maplibre OSMUS slack channel.@maplibre twitter.I am very happy to invite the people in the list below to become MapLibre Voting Members. The Governing Board chose you because we (@lseelenbinder @nyurik @klokan and I) think that you made an important and non-trivial contribution to MapLibre. As a Voting Member, you have the right to participate in the Governing Board election which will take place at the time of FOSS4G, i.e., end of August.
If you accept our invitation and would like to become part of the MapLibre Voting Members, please file a pull request to VOTING_MEMBERS.md where you add your GitHub handle to the existing list. You find instructions on how to file a pull request here.
If you did not get invited but would like to be a Voting Member, please write it into this issue. We most likely missed some people and I apologize for that in advance...
So, thanks for supporting MapLibre and I am looking forward to your pull requests.
@ambientlight 👍 ✉️
@astridx
@atierian 👍 ✉️
@bchapuis 👍 ✉️
@bdon 👍 ✉️
@birkskyum 👍 ✉️
@boldtrn
@brendan-ward 👍 ✉️
@chippieTV 👍 ✉️
@dayjournal 👍 ✉️
@drwestco 👍 ✉️
@fredj 👍 ✉️
@HarelM 👍 ✉️
@hoeflehner 👍 ✉️
@JannikGM 👍 ✉️
@Joxit 👍 ✉️
@jutaz 👍 ✉️
@Kanahiro 👍 ✉️
@kylebarron
@Malvoz
@marcelnormann
@maxammann 👍 ✉️
@METACEO 👍
@migurski
@mnutt 👍 ✉️
@mojodna 👍 ✉️
@msbarry 👍 ✉️
@muesliq 👍 ✉️
@nreese 👍 ✉️
@ntadej 👍 ✉️
@nvanfleet 👍 ✉️
@OlexandrStepanov 👍 ✉️
@petr-pokorny-1 👍
@petrsloup 👍 ✉️
@prozessor13 👍 ✉️
@rbrundritt 👍 ✉️
@roblabs 👍 ✉️
@rubenmx
@SjoerdPerfors 👍 ✉️
@smellyshovel 👍 ✉️
@stepankuzmin
@sulewicz 👍 ✉️
@thaddmt 👍 ✉️
@TomPohys 👍 ✉️
@webberig
@xabbu42 👍 ✉️
@ZeLonewolf 👍 ✉️
@zstadler 👍 ✉️
Legend: 👍 means the person accepted the invitation and sent a pull request. ✉️ means the person shared their email address for the voting system.
The Governing Board elections will take place online on Thursday, August 25th, 2022 which coincides in time with FOSS4G.
Candidates for the Governing Board can nominate themselves up to two weeks before the election, i.e., until Thursday, August 11th, 2022 by posting in this thread that they are interested in serving on the Board. Please include a description of your involvement in the MapLibre Project and disclose if you are paid for working on MapLibre or have a vested interested in the Project.
Some people have applied to https://maplibre.org/jobs. Screen to see who would be suited for the roles.
https://github.com/birkskyum/unassert-rollup-plugin/tree/maplibre-onboarding-files
https://www.npmjs.com/package/unassert-rollup-plugin
maplibre-gl-js already rely on this repository to remove node assert from the source code for release builds - for development builds the assert is not removed but bundled using browserify. It's only used at maplibre, and might as well be under the organisation, both in terms of npm and github. I made a branch that contains the changes needed for this onboarding, but I'd like to know if you think it belongs here of if I should keep it on my personal account.
Copyright (c) <year> MapLibre contributors in license file(s) and in the readme./README.md/LICENSELICENSE-MIT and LICENSE-APACHE/CONTRIBUTING.md/.github dir./.github/FUNDING.yml file copied from maplibre-gl-js/funding/CODE_OF_CONDUCT.md# Contributor Covenant[](https://github.com/maplibre/maplibre/blob/main/CODE_OF_CONDUCT.md)Sponsorships checkbox (see also FUNDING.yaml above).Preserve this repository.squash merge. Disable other merge types if possible.Automatically delete head branches.main.#maplibre OSMUS slack channel.@maplibre twitter.https://github.com/maplibre/maplibre-gl
This repository is what has started the MapLibre organization, and thus is a motivation in of itself :). That said, we still need to ensure it confirms to our standards.
Copyright (c) <year> MapLibre contributors in license file(s) and in the readme./README.md/LICENSELICENSE-MIT and LICENSE-APACHE/CONTRIBUTING.md/.github dir./.github/FUNDING.yml file copied from maplibre-gl-js/funding/CODE_OF_CONDUCT.md# Contributor Covenant[](https://github.com/maplibre/maplibre/blob/main/CODE_OF_CONDUCT.md)Sponsorships checkbox (see also FUNDING.yaml above).Preserve this repository.squash merge. Disable other merge types if possible.Automatically delete head branches.main.#maplibre OSMUS slack channel.@maplibre twitter.Switch to organizational controlled system.
Additional benefits wanted:
Zoom or Google Meet ?
https://github.com/maplibre/mbtileserver-rs
Mbtileserver offers community an actively maintained tool to serve tiles optimized for MapLibre GL & native. In addition, having this project as part of MapLibre will allow community to prototype new experimental features:
Copyright (c) <year> MapLibre contributors in license file(s) and in the readme./README.md/LICENSELICENSE-MIT and LICENSE-APACHE/CONTRIBUTING.md/.github dir./.github/FUNDING.yml file copied from maplibre-gl-js/funding/CODE_OF_CONDUCT.md# Contributor Covenant[](https://github.com/maplibre/maplibre/blob/main/CODE_OF_CONDUCT.md)Sponsorships checkbox (see also FUNDING.yaml above).Preserve this repository.squash merge. Disable other merge types if possible.Automatically delete head branches.main.#maplibre OSMUS slack channel.@maplibre twitter.WIP
https://github.com/birkskyum/geojsonhint moved to https://github.com/maplibre/geojsonhint
We currently rely on an abandoned mapbox library, with no way to maintain it: https://github.com/mapbox/geojsonhint
Copyright (c) <year> MapLibre contributors in license file(s) and in the readme./README.md/LICENSELICENSE-MIT and LICENSE-APACHE/CONTRIBUTING.md/.github dir./.github/FUNDING.yml file copied from maplibre-gl-js/funding/CODE_OF_CONDUCT.md# Contributor Covenant[](https://github.com/maplibre/maplibre/blob/main/CODE_OF_CONDUCT.md)Sponsorships checkbox (see also FUNDING.yaml above).Preserve this repository.squash merge. Disable other merge types if possible.Automatically delete head branches.main.#maplibre OSMUS slack channel.@maplibre twitter.Different users of MapLibre GL Native have different goals and priorities. We concluded that we need to have a written list of goals that our community has for MapLibre GL Native. This will help us in discussions and in reaching decisions.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.