Hiero technical governance

This repository contains the config.yaml file that is used to configure all GitHub repositories of the organisation. https://clowarden.io is used as tool to manage the GitHub ressources and the changelist for all Hiero repos can be found here.

Definition of groups

The config.yaml file defines several groups that all have different usecases:

• github-maintainers: The group is responsible for maintaining our GitHub environment and infrastructure (including GitHub Action runners, ...).
• github-committers:
• community: A group that contains all people that are currently not part of any other group. We use this temporarly to invite people to the Hiero org.
• tsc: The group that contains all members of the technical steering committee (TSC) as defined here.
• lf-staff: The group contains all Linux Foundation and LF Decentralized Trust members that needs (mostly ADMIN) rights on the org.
• REPO-maintainers: For each repository/project we have a group that defines the maintainers of that repository/project.
• REPO-committers: For each repository/project we have a group that defines the committers of that repository/project.
• voting-candidates: A temporary group that contains all people that did contributions to Hashgraph repositories in the past and therefore are allowed to vote on TAC votings.

Definitions of roles

For each project the following roles should be defined for the groups that work on the repository. All roles are based on the GitHub role defintions.

• github-maintainers: ADMIN
• github-committers: WRITE
• tsc: ADMIN
• REPO-maintainers: MAINTAIN
• REPO-committers: WRITE

Difference between committers and maintainers

As said we have a REPO-maintainers and REPO-committers group per project. The idea is that the REPO-maintainers group contains 1-3 people that will manage/lead the development of that project. The people in the group have some additional rights next to the people in the REPO-committers group. All differences can be found in the GitHub role defintions but some concrete examples are the management of labels for the repository or the mutation of the project description that is only allowed by people in the REPO-maintainers group.