...
- Dedicated time slot for RFC review (Once every 2 weeks, as needed)
- When submitting new RFCs, it is highly recommended to have a smaller scope. In case of a large scale change, consider breaking up the RFCs into smaller RFCs. This greatly helps the RFC get through the review process quickly.
- When there are exceptional cases that results in a stalemate (when there is no clear path even after extension period for a given review phase), the TC will force a vote to decide on the fate of RFC. TC could negotiate with the stakeholders and strike compromise to keep the RFC moving forward or it could end up rejecting the RFC citing an appropriate reason
- Feedback from anyone interested MUST be taken into consideration by the submitter at any stage during the review process as long as it is appropriately documented in the PR
Resources
- RFC Template
- Slack channel: #tc-rfc
To Do's
Create new Slack Channel- Permissions in the RFC needs to be modified to allow users to resolve, create PRs
- Add CODEOWNERS file that includes all members of the TC. We have TC group in Github
...