blob: 69dc4117459a4d427ae0966c7a1d8a369201ae1a (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
Status: Undefined (as of YYYY-MM-DD)
Type: (Standard or Process)
Github PR: (add HTTPS link here after PR is opened)
Short Name: (number and shortname here, like `0000-my-proposal`)
# Summary
[summary]: #summary
One paragraph explanation of what this is about.
# Motivation
[motivation]: #motivation
Why are we doing this? What use cases does it support? What is the expected outcome?
# Usage Documentation
[usage-documentation]: #usage-documentation
Document new features or processes as if this proposal has already been accepted and implemented. This section should introduce new concepts and terms, describe use cases or situations, and provide examples. If a user-facing feature is added, this should also include user-accessible documentation.
# Reference Documentation
[reference-documentation]: #reference-documentation
This section is a more formal description of the proposal, written as if it was a sub-section of the standard (for techincal proposals) or a formal process or "fine print" for process proposals.
It should be unambiguous and cover all known corner-cases. Formal language (such as protobuf schemas or binary header diagrams) are appropriate here.
# Drawbacks
[drawbacks]: #drawbacks
Why should we *not* do this?
# Rationale and alternatives
[alternatives]: #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
[unresolved]: #unresolved-questions
- What parts of the design do you expect to resolve through the RFC consensus process before this gets merged?
- What parts of the design do you expect to resolve through implementation and code review, or are left to independent library or application developers?
- 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?
# Changelog
[changelog]: #changelog
A brief statemnt about current status can go here, follow by a list of dates
when the status line of this RFC changed (in most-recent-last order).
- YYYY-MM-DD: First complete draft submitted for review
|
