From 32393e137f01beebdad64567dcb2f627127f8d68 Mon Sep 17 00:00:00 2001 From: user Date: Wed, 10 Apr 2019 14:41:10 +0200 Subject: Copy template --- rfcs/0043-nixpkgs-workflow.md | 47 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 47 insertions(+) create mode 100644 rfcs/0043-nixpkgs-workflow.md diff --git a/rfcs/0043-nixpkgs-workflow.md b/rfcs/0043-nixpkgs-workflow.md new file mode 100644 index 0000000..f2707da --- /dev/null +++ b/rfcs/0043-nixpkgs-workflow.md @@ -0,0 +1,47 @@ +--- +feature: nixpkgs-workflow +start-date: (fill me in with today's date, YYYY-MM-DD) +author: Matthias Beyer (@matthiasbeyer) +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? + +# Future work +[future]: #future-work + +What future work, if any, would be implied or impacted by this feature +without being directly part of the work? -- cgit v1.2.3