---
# System prepended metadata

title: Governance infrastructures

---

# Governance infrastructures
Who: MM, PN, AM, GR



## Potential problems
* A lot of different projects working together *(rendering toolchain ~ 12 people, other parts just a couple).*
* If maintainer goes to different direction than community (e.g. iD).
* No means of exerting pressure on many pieces of software.
* Not making maintainers feeling forced into something.

## Suggestions
* Have possibility of community overide for decisions of maintainers.
* Structure that resolves disputes - not having just one person.
* Look at other projects governance.
--
* Limit scope.
* Find people behind / stakeholders.
--
* Start with tagging.

### On tagging
* Lack of need for approval contributed to OSM success.
* Difference with software projects.
--
**Suggestion:** Recommendation of best practices
** Demand for strong recommendations.

#### Governance structure 
**Liquid democracy** (vote delegation)

* Broadest pool: OSMF membership (individual/corporate).
* Ensuring experts involved.

## iD
* Establishing governance structure independent from board.

## Other points mentioned during discussion
* Not burdening maintainers with decisions.
* Roadmaps of projects.
* Concern regarding software that are maintaining / affecting content of the database.

## Action items
* Allan to initiate board discussion with other people about iD governance.
* Allan to talk to Quincy and Andy Allan about liquid democracy.