...
The purpose of this document is to describe the GitHub roles used by the FIO protocol and how each role can be obtained by community members.
Assumptions:
Dispute resolution will be performed by airing of grievances first to the organisation owners on the GitHub and the last resort is open discussions with the fio steering committee during its scheduled meetings.
Roles:
GIT Organization
Owner – This 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 – 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)fio protocol can be requested of GitHub members by asking an existing member via social media. Membership may be requested directly of any GitHub account by the organisation owners. Membership will be granted based upon the perceived merits of the individual to the fio protocol by the organisation owners. Any disagreement in membership can be brought first to other members to convince them to advocate for the new member.
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.
...