RFC processes
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
run a request-for-comments process with scope, reviewers, and a deadline.
Planned topics
- An RFC states the problem, options, recommendation, trade-offs, and what feedback is needed.
- Name required reviewers (affected teams, security if relevant) and optional ones; state the decision owner.
- Set a comment deadline and a decision date; after the deadline the owner decides.
- Outcomes are recorded: accepted, accepted with changes, rejected, or withdrawn, with reasons.
- Keep RFCs short; a long document hides the decision.
Draft outline details
Demonstration
RFC template headings: context, goals and non-goals, options, recommendation, risks, rollout, open questions, reviewers, decision deadline. Add a status line: draft, in review, decided.
Check your understanding
What happens at the decision deadline?
Show answer
The named owner decides and records the outcome, even if some comments remain.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.