Conversation
| ```md | ||
| ## Goal Description | ||
|
|
||
| In roughly one paragraph, describe from a high level _what_ this Goal is. Provide just enough to describe to the public and contributors _what_ the bounds of the Goal are. Leave the "why" and "how" to the future **Design Documents**. Avoid dictating implementation or design details whenever possible. |
There was a problem hiding this comment.
I'm not sold on completely leaving the "why" out of this section. One paragraph of motivation would be very useful for potential contributors and curious onlookers.
There was a problem hiding this comment.
My problem with "why" is that it is opinionated, is often rooted in the details of the problem, and risks overly defining the bounds of the Goal. Answering "why" involves building an argument which is in many ways the most important part of a design document. "Why" changes over time, as the engine changes. The "why" is what transitions something from Proposed to Approved, and is the result of a discussion between multiple people. Including "why" up front makes it harder / higher overhead to create Goal proposals.
alice-i-cecile
added
S-Needs-Review
X-Blessed
alice-i-cecile
added
S-Ready-For-Final-Review
3 participants
No description provided.