Define Project Roles

[qu1queee]

Related to #243

Goal

Establish a clear definition of the following roles:

SHP Role
Contributor
Approver
Maintainer
Admin

Establish a relationship of those roles with:

• OWNER's file across repositories

Establish a mapping of those roles with GHE:

As we are now under a GHE account, I think we will benefit of having granular roles in the Shipwright organization. I propose to leverage Repository access for each permission level, so that our documented roles easily translate into user access of our organization.

Github documents:

• Read: Recommended for non-code contributors who want to view or discuss your project
• Triage: Recommended for contributors who need to proactively manage issues, discussions, and pull requests without write access
• Write: Recommended for contributors who actively push to your project
• Maintain: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions
• Admin: Recommended for people who need full access to the project, including sensitive and destructive actions like managing security or deleting a repository

So we can have the following mapping:

SHP Role	Github Role
Contributor	Triage
Approver	Write
Maintainer	Maintain
Admin	Admin

[qu1queee]

We had a meeting on this today (@Adarsh-jaiss , @karanibm6 , @MaheshRKumawat ):

SHP Role	Github Role
Community Participant	Might be not a Github Role or Read role
Contributor	Triage
Reviewer	Customized new Role (part of Owners), without write rights
Approver	Write
Maintainer	Maintain
Admin	Admin

Next steps:

• We are not sure about the scope of the roles(org vs project scope)
• We need a definition of roles. It helps to map them to GHE roles, so we have a tight control in GHE.
• We need a definition of the roles requirements, so basically, what u need to do to be in that role.