Skip to content

Latest commit

 

History

History
90 lines (56 loc) · 2.96 KB

GOVERNANCE.md

File metadata and controls

90 lines (56 loc) · 2.96 KB
Raw

Roles, People, and Processes for Maintaining the Tagging Schema

This document outlines how this project is maintained.

Roles & People

Maintainer Role

Martin maintains this project as part of his work on the iD Editor project.

The maintainer role includes:

  • Having the final say in decisions for the tagging schema.
  • Creating releases.
  • Updating dependencies.
  • Assign roles.

and all the following roles.

Github shows a (Member) label next to users with full access to this repository and the organisation.

Co-Maintainer Role

  • Kyle contributes to this project as a volunteer.
  • Tobias contributes to this project as a volunteer.

The co-maintainer role includes:

  • Reviewing PRs.
  • Merging "clear-cut" PRs by others.

and all the following roles.

Github shows a (Collaborator) label next to users with any permission on this repository.

Triage Role

(No one has the triage role at the moment. Please reach out if you want to help.)

The triage role includes:

  • Proactively helping to clarify issues and PRs.
  • Closing issues as duplicates or not planned.
  • Assigning labels to issues and PRs.

Github shows a (Collaborator) label next to users with any permission on this repository.

Contributors

To all contributors, thank you so much for your support! ❤ Especially for:

  • Suggesting new presets and fields or updates to the repository.
  • Researching and helping with issues and PRs.
  • Translating the tagging schema.

Code contributions: Check this complete list of contributors on GitHub.

Github shows a (Contributor) label next to users that previously committed to this repository.

Processes

PR Reviews and Merges

  • PRs need approval from two people: the author and one or more (co-)maintainers before being merged.
  • Non-"clear-cut" changes need to be merged by the maintainer.
  • We might revert merges later if necessary.

What is a clear-cut change?

  • No or minimal controversial discussion on the change.
  • Coding and contribution guidelines are met.

How to merge…

  • Usually squash merge PRs to make the history simpler
  • Give the merge a meaningful description of the change
  • Add labels to the PR to simplify creating the changelog: new-*, add-*, bug

Releases

There is no set release schedule at the moment, but releases usually occur every other month. After this project is released, the projects that rely on the data need to update and release as well.

Assigning roles

  • The maintainer of the iD editor has traditionally and continues to maintain this project.
  • Co-maintainer and triage roles are assigned by the current maintainer of the repository.

Previous Maintainers

Many thanks to all previous maintainers! ❤