Skip to content
This repository has been archived by the owner on Oct 28, 2024. It is now read-only.

Commit

Permalink
Updated governance to cover general decision-making process
Browse files Browse the repository at this point in the history
  • Loading branch information
roll committed May 7, 2024
1 parent 6d14837 commit e7b5b4a
Showing 1 changed file with 29 additions and 4 deletions.
33 changes: 29 additions & 4 deletions content/docs/standard/governance.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,15 +4,40 @@ sidebar:
order: 7
---

The Data Package Standard is governed by a working group made of [Frictionless](https://frictionlessdata.io/) community members coming from different disciplines. The composition of the working group is [publicly accessible on GitHub](https://github.com/orgs/frictionlessdata/teams/data-package-working-group/members?query=).
The Data Package Standard is governed by a working group made of [Frictionless](https://frictionlessdata.io/) community members coming from different disciplines.

The working group works asynchronously, using a review model for any changes in the specifications. We also hold [monthly update calls](https://forms.gle/UEqGnYKESqqw1LeW7) for the working group, which are of course not compulsory, and which are also open to the broader community.

## How we decide
## Working Group

For every GitHub issue on the specs submitted by the community throughout the years, a working group member will propose a recommended action to the working group. The action proposed will be accepted if consensus with the working group is reached, meaning we have arrived at a decision, or at least a compromise, that everyone can live with.
The composition of the working group:

The working group will be invited to share their view in a devoted GitHub issue. If a broader conversation is needed, the proposal discussion can be elevated to the monthly call for deliberation. The working group will be given a reasonable amount of time to review the proposed action.
### Vetoing Members

- **Evgeny Karev** (on-behalf of Open Knowledge Foundation)
- **Peter Desmet** (Research Institute for Nature and Forest (INBO))

### Voting Members

- **Phil Schumm** (CTDS - University of Chicago)
- **Kyle Husmann** (Pennsylvania State University)
- **Keith Hughitt** (National Institutes of Health)
- **Jakob Voß** (Verbundzentrale des GBV (VZG))
- **Ethan Welty** (Falling Fruit)
- **Paul Walsh** (Link Digital)
- **Pieter Huybrechts** (Research Institute for Nature and Forest (INBO))

## Advisory Members

- **Martin Durant** (Anaconda, inc.)
- **Adam Kariv** (The Public Knowledge Workshop)
- **Johan Richer** (Coopérative pour un numérique d'intérêt général)

## Decision Making

A proposed change to the specifications, that can be initiated by any community or working group member using a GitHub pull request, will be accepted if consensus with the working group is reached, meaning we have arrived at a decision, or at least a compromise, that everyone can live with.

The working group will be invited to share their view in a devoted GitHub pull request. If a broader conversation is needed, the proposal discussion can be elevated to the monthly call for deliberation. The working group will be given a reasonable amount of time to review the proposed action.

Consensus is reached and the issue is closed if at least ⅔ of the working group members participate in the discussion and express their favourable opinion. In case of serious and explicitly stated concerns, working group members who are core library investors (at the moment: [Open Knowledge Foundation (OKFN)](https://okfn.org/), the [Research Institute for Nature and Forest (INBO)](https://www.vlaanderen.be/inbo/en-gb/homepage/), [Datopian](https://www.datopian.com/)) may veto a proposed action.

Expand Down

0 comments on commit e7b5b4a

Please sign in to comment.