...
Code Owner – the repo admin will identify a set of organization members who are qualified to provide an approving review to enable merge of the PR (it is recommended at least 2 of these be identified per repo). it is recommended that GitHub Teams be used to identify code owners for related repositories on the GitHub.
Merger – once a PR has met approval requirements any organization member may merge the PR (this requires write access to the repo).
a process of change request will be used within FIO. By convention the FIO protocol repository admin will decide how many reviewers are required for pull requests to be merged into specific branches. it is recommended that for develop this number be at least 1, and for master it be at least 2. repositories should enable require review by code owners. a code owners file should be established in each repository.
How to obtain a role --
Owner, Admin
For FIO the roles of owner, and admin, these will be granted by majority agreement of the present organization owners. In order to gain these roles, a candidate will need to be a member “in good standing” within the organization. The member needs to request the role from one of the organization owners via any direct communication mechanism. The role of admin can be delegated by an existing owner to another member of their choosing. When delegating the owner should provide transparency of this delegation to the other owners before delegating the role. Owners are responsible to monitor their satisfaction with the performance of admins. When admins fall short of desired performance, owners may remove them from service and put into place a new admin member.
Code Approver owner --
organization owners, and repository admin may identify organization members as qualified code reviewers. these individuals can be placed onto teams within the GitHub.