Skip to content

Latest commit

 

History

History
45 lines (26 loc) · 1.43 KB

File metadata and controls

45 lines (26 loc) · 1.43 KB
  • Start Date: (fill me in with today's date, DD-MM-YYYY)
  • Status: (One of Proposed, Accepted or Rejected)

(RFC title goes here)

Summary

One paragraph explanation of the change.

Motivation

Why are we doing this? What use cases does it support? What is the expected outcome?

Design Detail

This is the bulk of the RFC.

Explain the design in enough detail for somebody familiar with the infrastructure to understand. This should get into specifics and corner-cases, and include examples of how the service is used. Any new terminology should be defined here.

Drawbacks

Why should we not do this? Please consider the impact on users, on the integration of this change with other existing and planned features etc.

There are tradeoffs to choosing any path, please attempt to identify them here.

Rationale and Alternatives

Why is this design the best in the space of possible designs?

What other designs have been considered and what is the rationale for not choosing them?

What is the impact of not doing this?

Unresolved questions

What parts of the design do you expect to resolve through the RFC process before this gets merged?

What parts of the design do you expect to resolve through the implementation of this feature before stabilisation?

What related issues do you consider out of scope for this RFC that could be addressed in the future independently of the solution that comes out of this RFC?