Template for writing technical RFC docs

submited by
Style Pass
2023-11-19 10:00:02

At the top of the template, you should have a clear title of the proposal. I usually prefix it with RFC - <title> to make it easier to search later in Google Drive.

The first three states are used during the review of the RFC, and once approved we proceed to the next two states which refer to its implementation and rollout.

Note: In Google Docs, make sure you “refresh” the table of contents widget after adding/removing sections in the document because it doesn’t auto-update. You can refresh it by clicking anywhere inside the table of contents, and clicking the “refresh” icon at its left side that will appear.

In this section you should describe the problem the RFC is addressing, and provide necessary context so that people unfamiliar with it can understand the benefits of implementing the RFC. There can be sub-sections to give more detailed information.

Provide rough estimates and track key milestones for the RFC and its implementation, including its rollout. This section is to be updated over time as the RFC progresses from review, to approval, to implementation, and to its rollout.

Leave a Comment