...
GIT Organization
Owner – This roles role can perform all admin and management of members, repositories, teams and other git information associated with the FIO organization. importantly owners can create and remove repositories within the organization. Owners can invite new members into the GitHub organization.
Member – A An organization member is a pre existing git account that has been invited and accepted the invitation into the FIO organization. Members can be assigned to teams within the FIO protocol. Members can be provided permissions/repository roles (see below). Members can be private or public (this is the choice of the member). Membership on the FIO protocol is held by a small set of individuals in the community (less than 50)
Team – a team is a group of FIO protocol members. Teams can be provided permissions/repository roles (see below). teams can be secret or visible.
...
Branch names for organization repositories
master – current operational baseline.
...
Approver – anyone with read access to the repo can approve or request further changes to a PR.
Code Owner – the repo admin will identify for each repository or groups of associated repositories there will be 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 with write access to the repository 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 owners will decide how many code owner reviewers are required for pull requests to be merged into specific branchesthe above named branches of each repository. it is recommended that for develop this number be at least 1, and for master it be at least 2. All FIO organization repositories should be configured in the same manner. Each 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 GitHub organization administration is the roles of owner, and admin, these will be granted by majority agreement of the present organization owners. duty of a single WP.
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 owner --
organization owners, and repository admin may identify organization members as qualified code reviewers. these individuals can be placed onto teams within the GitHubof this WP team. The combined role (owner/admin) will be assigned to 2 or more people at the discretion of the WP lead. In FIO the accounts serving as owner and admin for all repositories will be the same git accounts in order to ensure consistency of configuration of FIO git repositories.
Code owner --
code owners are experienced engineers in designing testing and implementing of software either on or off of the blockchain. Any organization member with the necessary interest or experience can become a code owner. The granting of the code owner role will be performed by the existing set of code owners.
In order to gain this role, a GitHub account holder must become a member of the FIO organization, then they must request to be granted code ownership permission on the desired team/s. The existing set of code owners will give a thumbs up, thumbs down to approve or deny the request.
Assumptions:
It is assumed that the GitHub FIO organization owners will act in the best interests of the FIO DAO when interacting with the FIO community. If any community member feels that they are not, then issues can be brought up to the FIO steering committee during the normal steering committee WP review and monthly meeting process.