mirror of
https://github.com/NixOS/rfcs.git
synced 2025-11-08 11:36:12 +01:00
parent
8f83af7ce0
commit
cff5922776
2 changed files with 121 additions and 6 deletions
41
0000-template.md
Normal file
41
0000-template.md
Normal file
|
|
@ -0,0 +1,41 @@
|
|||
---
|
||||
feature: (fill me in with a unique ident, my_awesome_feature)
|
||||
start-date: (fill me in with today's date, YYYY-MM-DD)
|
||||
author: (name of the main author)
|
||||
co-authors: (find a buddy later to help our with the RFC)
|
||||
related-issues: (will contain links to implementation PRs)
|
||||
---
|
||||
|
||||
# Summary
|
||||
[summary]: #summary
|
||||
|
||||
One paragraph explanation of the feature.
|
||||
|
||||
# Motivation
|
||||
[motivation]: #motivation
|
||||
|
||||
Why are we doing this? What use cases does it support? What is the expected
|
||||
outcome?
|
||||
|
||||
# Detailed design
|
||||
[design]: #detailed-design
|
||||
|
||||
This is the bulk of the RFC. Explain the design in enough detail for somebody
|
||||
familiar with the ecosystem to understand, and implement. This should get
|
||||
into specifics and corner-cases, and include examples of how the feature is
|
||||
used.
|
||||
|
||||
# Drawbacks
|
||||
[drawbacks]: #drawbacks
|
||||
|
||||
Why should we *not* do this?
|
||||
|
||||
# Alternatives
|
||||
[alternatives]: #alternatives
|
||||
|
||||
What other designs have been considered? What is the impact of not doing this?
|
||||
|
||||
# Unresolved questions
|
||||
[unresolved]: #unresolved-questions
|
||||
|
||||
What parts of the design are still TBD or unknowns?
|
||||
Loading…
Add table
Add a link
Reference in a new issue