-
Type:
Epic
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Component/s: Cross Spec Consistency
-
None
-
CONTRIBUTING.md spec standard updates
-
None
-
-
To Do
-
0
-
0
-
0
-
100
-
None
-
None
-
None
-
Not Needed
-
None
-
None
-
None
-
None
-
None
-
None
Summary
What is the problem or use case, what are we trying to achieve?
Update all specifications to match the new CONTRIBUTING.md guidelines.
Motivation
Who is the affected end user?
Who are the stakeholders?
All specification maintainers and readers.
How does this affect the end user?
Are they blocked? Are they annoyed? Are they confused?
Inconsistency across specifications causing confusion, drift, and conflicts.
How likely is it that this problem or use case will occur?
Main path? Edge case?
Every specification is not 100% compliant with the new guidelines.
If the problem does occur, what are the consequences and how severe are they?
Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?
Inconsistent specification structure and language.
Is this issue urgent?
Does this ticket have a required timeline? What is it?
No. General cleanup only.
Is this ticket required by a downstream team?
Needed by e.g. Atlas, Shell, Compass?
No.
Is this ticket only for tests?
Is this ticket have any functional impact, or is it just test improvements?
Neither functional or test improvements.
Cast of Characters
Engineering Lead:
Document Author:
POCers:
Product Owner:
Program Manager:
Stakeholders: