summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authoruser <user@localhost.localdomain>2019-04-10 14:41:10 +0200
committeruser <user@localhost.localdomain>2019-04-10 14:41:10 +0200
commit32393e137f01beebdad64567dcb2f627127f8d68 (patch)
treed62510ce8b73a8e0bb9d1a4e42048be06e18a87d
parent138600bd7843f5590cd989b2534f38111a4b644e (diff)
Copy template
-rw-r--r--rfcs/0043-nixpkgs-workflow.md47
1 files changed, 47 insertions, 0 deletions
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?