-
-
Notifications
You must be signed in to change notification settings - Fork 27
Closed
Description
- Add text about revisiting the values frequently (each year?)
- Should we have rules/guidelines to how changes to the doc should land? For example, does it require TSC approval (similar to collaborator guide changes and semver major)?
- Add section about how the document should be interpreted, and how ambiguity should be handled
- Add text explaining it is a living doc
- More line items
- Clarify if the current doc reflects the current state of the project or what we envision that the technical values should be
- Should we remove the priorities?
(living issue, will keep writing on it until the meeting is over)
Metadata
Metadata
Assignees
Labels
No labels