From d26d5e7fc892c3ae79370a7e8aa58023e2b114d5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Stefan=20=C3=85lund?= <alund@spotify.com>
Date: Sat, 5 Sep 2020 12:20:14 +0200
Subject: [PATCH] Add issue template for RFCs (#2290)

* Add issue template for RFCs

* Update rfc_template.md

* Update rfc_template.md
---
 .github/ISSUE_TEMPLATE/rfc_template.md | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/rfc_template.md

diff --git a/.github/ISSUE_TEMPLATE/rfc_template.md b/.github/ISSUE_TEMPLATE/rfc_template.md
new file mode 100644
index 0000000000..c4990ee5d6
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/rfc_template.md
@@ -0,0 +1,26 @@
+---
+name: 'RFC'
+about: 'Request For Comments (RFC) from the community'
+labels: rfc
+title: '[RFC] <name>'
+---
+
+**Status:** Open for comments
+
+<!--- Open for comments |Closed for comments (RFC no longer maintained) --->
+
+## Need
+
+<!--- Why are we proposing this change? Why is this the problem we’re trying to address and what benefits/impact do we expect to get from this --->
+
+## Proposal
+
+<!--- The proposed approach. Describe the proposal in as much detail as needed for reviewers to give concrete feedback. Take special care in this section to describe any implications on data privacy or security. --->
+
+## Alternatives
+
+<!--- What alternatives to the proposed solution were considered? What criteria/data was used to discard these --->
+
+## Risks
+
+<!--- What other things happening could conflict or compete (for example for resources) with the proposal? What risk are there and how do we plan to handle them --->