We often forget why we made some decision in the pipeline. When circumstances change, we are not sure if we are forgetting other factors in our original decision.
Considered Options
Record our decisions via ADRs as GitHub issues
Record our decisions in some other manner
Don't record our decisions
Decision Outcome
Proposed decisions will be submitted via GitHub issues with the "decision" tag. The status will originally be "proposed" and after discussion will be moved to "accepted" or "rejected". Discussion will happen in the comments, as needed. Discussion from meetings must be captured in the issue for the record.
Issues can then be revisited later, keeping its "accepted" status or changing to "deprecated" or even "superseded by ISSUE", where ISSUE would be a link to a new decision issue.
Consequences
Record our decisions via ADRs as GitHub issues
Pros
Easily searchable via the GitHub issue systems.
Can create a template for decision issues.
Cons
We might forget to record decisions. We will need to make a cultural change to do this regularly.
Record our decisions in some other manner
Pros
The information is fairly simple and could be recorded in almost any text-based manner.
Cons
We already use GitHub issues frequently, so if decisions are in some other location, we may not see/use/remember them.
GitHub issues are easily searchable.
Don't record our decisions
Pros
It's faster and easier.
Cons
As described in the problem statement, we forget why we decided something and then have difficulty knowing if we can change our mind about something.
Context and Problem Statement
We often forget why we made some decision in the pipeline. When circumstances change, we are not sure if we are forgetting other factors in our original decision.
Considered Options
Decision Outcome
Proposed decisions will be submitted via GitHub issues with the "decision" tag. The status will originally be "proposed" and after discussion will be moved to "accepted" or "rejected". Discussion will happen in the comments, as needed. Discussion from meetings must be captured in the issue for the record.
Issues can then be revisited later, keeping its "accepted" status or changing to "deprecated" or even "superseded by ISSUE", where ISSUE would be a link to a new decision issue.
Consequences
Record our decisions via ADRs as GitHub issues
Pros
Cons
Record our decisions in some other manner
Pros
Cons
Don't record our decisions
Pros
Cons
More Information