Skip to content

docs: Added maintenance information to governance #1109

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
roll wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: Added maintenance information to governance #1109

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion content/docs/overview/governance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,4 +44,13 @@ Consensus is reached and the issue is closed if at least ⅔ of the working grou

The community manager at OKFN will reach out to working group members who did not participate in the discussion to make sure their opinion is also captured. Reminders of your participation will be handled with care. Members of the working group can expect a gentle and considerate approach, such as receiving an email once every two weeks highlighting any issues where your vote is pending. The goal is to keep them informed without causing any unnecessary inconvenience.

Decision-making on the technical maintenance of the specs will be centralised by OKFN.
## Maintenance

The project is maintained by a dedicated subgroup within the working group. The current active maintainers are:

- **Evgeny Karev** ([Datist](https://datist.io/))
- **Peter Desmet** (Research Institute for Nature and Forest (INBO))

## Releasing

Once a new version of the standard is ready with all applicable changes are approved by the working group, all the maintainers need to approve the release to publish it. No working group voting required for the release itself.