NOTE: Use the number and the title to name the document. Follow the
dr-{000}-{DR title}.mdnaming convention. See thedr-002-Traefik_as_an_API_Gateway.mdas na example.
Created on {YYYY-MM-DD} by {name and surname (@Github username)}.
| Name | Description |
|---|---|
| Title | {Provide a brief summary of the decision.} |
| Ultimate decision maker(s) | {Specify who takes the final decision if the SIG/WG cannot reach the consensus.} |
| Due date | {Specify the date by which the SIG or WG members need to make the decision. Use the YYYY-MM-DD date format.} |
| Input provider(s) | {Include those who influence the decision and, if possible, those whom the decision affects.} |
| Group(s) affected by the decision | {Specify whom the decision affects.} |
| Decision type | {Type in Binary, Choice, or Prioritization. The Binary type refers to the yes/no decisions, the Choice type means that the decision involves choosing between many possibilities, such as a name for a new product, and the Prioritization type involves ranking a number of options, such as choosing the next five features to build out of one hundred possible options.} |
| Earliest date to revisit the decision | {Specify the date from which the SIG/WG members can raise an issue to revisit the decision. Use the YYYY-MM-DD date format. The date does not apply to ultimate decision makers who can raise an issue to revisit the decision anytime.} |
Briefly describe what the decision record (DR) is about. Explain the factors for the decision, what are the forces at play, and the reasons why the discussed solution is needed. Remember that this document should be relatively short and concise. If necessary, provide relevant links for more details.
If the decision concerns more solutions, mark them with separate subsections. Use H3 for the subsection headings.
Avoid using personal constructions such as "we." Use impersonal forms instead. For example, The decision is to.... If it is necessary to indicate the subject, use SIG/WG members instead of "we."
The status of the document can be Accepted, Declined or Proposed(when it is waiting for decision of ultimate decision maker). This section should contain one of these two words followed by the date on which the status of the document is agreed on. Follow the YYYY-MM-DD format for the date. For example:
Accepted on 2018-03-23.
Briefly explain the consequences of this decision for the Kyma project. Include both the advantages and disadvantages of the discussed solution.