Remove RFC document, and add Trusted Contributor details

not-my-segfault-patch-1
Matt C 2 years ago committed by Michal S
parent 589329a19c
commit c5489d8bb9

@ -17,6 +17,12 @@ In order of descending power:
> See [core_team.md](governance/CORE_TEAM.md)
- **Trusted Contributor**:
A trusted individual who has made multiple contributions to the project (not including financial support).
> See [trusted_contributor.md](governance/TRUSTED_CONTRIBUTOR.md)
- **Team Lead**:
Coordinates a specific team and/or focus on the Project. (e.g., the Web Team Lead would manage progress on the website)

@ -2,7 +2,7 @@
## Powers
* Vote on RFCs (minor vote, unless a consensus agrees)
Same as [Trusted Contributor](TRUSTED_CONTRIBUTOR.md), plus:
* Vote to appoint/remove Team Leads (minor vote)
* Vote to appoint/remove Project Lead (major vote)

@ -0,0 +1,14 @@
# Regarding Trusted Contributors
## Powers
* Vote on RFCs (minor vote, unless a consensus agrees)
## Benefits
* `getcryst.al` email and LDAP for services hosted by the project
## Appointment/Dismissal
* First Trusted Contributor appointments by Core Team. Subsequent appointments are a minor vote by Core Team
* Removed by minor vote of Core Team

@ -1,4 +0,0 @@
# How to get your RFC passed
To approve an RFC, 51%+ of the current Core Team members must vote in favor of the final RFC text.
A vote can be initiated at any time, but if the group determines that more changes are needed, then it can be postponed.
If there should be an even number of team members, and the vote is split, then the current project lead is permitted to vote again to decide the outcome.
Loading…
Cancel
Save