Projects under the MapLibre umbrella are run by a meritocratic governance model. The overall governance across the projects starts with a lazy/self-elected board and will be replaced by a board elected by contributors. Deadline for implementing the electoral process is the Foss4G conference 2022 (the timespan before this deadline is referred to as the “initial phase”).
Role | Range | Description | Duties | Privileges | Authority | Change Procedure | Election Procedure |
---|---|---|---|---|---|---|---|
MapLibre Board Member (“steering committee”) | Overall | Similar to “PMC”, but elected after the initial phase. | Provide servant leadership and facilitation in any possible way to the overall project. Implement democratic election process to the board that represents the technical projects and their individual impact. Handling organizational assets like accounts. | Representing the overall project. | Last say on expenses and cross-project technical decisions if no consensus between the projects is possible. | TBD, see “duties”. | TBD. See “duties”. Initial: Signed the first maplibre-gl-js memorandum and contributed to the overall project progress afterwards (Luke, Marcel. Petr, Yuri). Additional members can be invited, unanimous voting by all other board members needed. |
User | Per technical project | Described in “User” | |||||
Contributor | Per technical project | See “Contributor” | Votes on MapLibre Board Members after initial phase. | ||||
Committer | Per technical project | See “Committer” |