Skip to content

Latest commit

 

History

History
37 lines (22 loc) · 2.81 KB

GOVERNANCE.md

File metadata and controls

37 lines (22 loc) · 2.81 KB

OSPOlogy Repo Governance

This document defines the governance process for the OSPOlogy repo. This doc outlines the various responsibilities of contributor roles in OSPOlogy, and clarifies how people can make their way up the OSPOlogy contributor ladder.

Role Responsibilities Requirements Defined by
OSPOlogy Contributor Active contributor in the community One successful merge of significant pull requests within the OSPOlogy repo OSPOlogy contributors GH team
OSPOlogy Maintainer See "Expectations from Maintainers" bellow
  • 5-10 successful merges of significant pull requests in two or more initiatives within the repo
  • Fulfill the "Expectations from Maintainers"
  • 2/3 majority thumbs up on the PR within settings.yml from existing maintainers.
settings.yml file

Changes in Maintainership

5-10 successful merges of significant pull requests in two or more initiatives within the repo within the OSPOlogy repo, any current maintainer can reach the author behind the pull requests and ask them if they are willing to become a maintainer. They can also send a PR to settings.yml file and request the existing maintainers to vote them in. Majority thumbs up on the PR within settings.yml from existing maintainers will be required for a person to become an OSPOlogy maintainer.

If a maintainer feels they can not fulfill the "Expectations from Maintainers", they are free to step down.

Existing maintainers can remove maintainers who become inactive or are not acting in the best interests of the TODO Group on a 2/3 majority vote from existing maintainers. If people step down or are removed, they will be added to the OSPOlogy emeritus list (TBD)

Voting process

Existing maintainers vote a new maintainer. All voting is done via a simple majority of maintainers. In case of conflict resolution, the TODO Steering Committee will have the final oversight.

Expectations from Maintainers

Every one carries water and helps out!

Every maintainer is listed in the settings.yml file

Making community work requires input and effort from everyone.

Maintainers should:

  • (1) Actively participate in PR reviews and respond in a timely fashion
  • (2) Be ready to moderate OSPOlogy meetings and/or regional TODO calls, if necessary.
  • (3) Review / approve / decline contributions from other contributors

The OSPOlogy repo governance also falls under the overall TODO Group governance.