re-introduce 'Acceptance Criteria' as part of the issue template

cardano-foundation · Mar 4, 2019 · 1f7a79b · 1f7a79b
1 parent fa43f1f
commit 1f7a79b
Showing 1 changed file with 13 additions and 2 deletions.
diff --git a/.github/ISSUE_TEMPLATE/task.md b/.github/ISSUE_TEMPLATE/task.md
@@ -6,7 +6,7 @@ about: Create a new Task
 
 # Context
 
-<!-- WHEN PROPOSED
+<!-- WHEN CREATED
 What is the issue that we are seeing that is motivating this decision or change. 
 Give any elements that help understanding where this issue comes from. Leave no 
 room for suggestions or implicit deduction.
@@ -15,13 +15,24 @@ room for suggestions or implicit deduction.
 
 # Decision
 
-<!-- WHEN PROPOSED
+<!-- WHEN CREATED
 Give details about the architectural decision and what it is doing. Be
 extensive: use schemas and references when possible; do not hesitate to use
 schemas and references when possible.
 -->
 
 
+# Acceptance Criteria
+
+<!-- WHEN CREATED
+Use standard vocabulary to describe requirement levels RFC-2119: Must-Should-May.
+
+e.g. 
+
+1. The API _must_ support creation of wallets through a dedicated endpoint.
+-->
+
+
 
 ---