Remove RFC document, and add Trusted Contributor details
parent
589329a19c
commit
c5489d8bb9
@ -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…
Reference in New Issue