[DRIVERS-2142] Document spec writing process from the authors perspective Created: 04/Jan/19 Updated: 31/Mar/22 |
|
| Status: | Backlog |
| Project: | Drivers |
| Component/s: | New Spec |
| Fix Version/s: | None |
| Type: | Spec Change | Priority: | Major - P3 |
| Reporter: | Matt Broadstone | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Driver Changes: | Needed | ||||
| Description |
|
We have a wiki page called How we work which documents our process (currently) for Code Reviews. We also have PM documentation (in the PM repo) documenting the step-by-step process for creating scopes and specs. Neither of these locations help a spec author know the actual collaborative process, expected etiquette and rationale from the drivers team perspective. We should create some documentation and place it on this wiki page or even on the front page of the specifications repo. |