- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Jul 2022 10:05:47 +0000
- To: public-design-tokens-log@w3.org
> it's useful to know when and why a decision was made. Seeing a simple history allows us to have context for a value but also allow any given tool to write to it and have that shared understanding in a way we haven't to date. I see a connection with this issue : https://github.com/design-tokens/community-group/issues/157 This change log could include changes made by tools. If a tool must change a value to make processable it could record this. ---- At the same time I wonder if tracking changes should be done externally? git exists and a service like GitHub is really successful in providing a nicer UX to expose a git history for source code. Someone can make a service to provide something similar for design tokens. ---- If a change log should be part of the specification I still think it should be separate from the deprecated/state property. A change log should encompass all aspects of a token (including deprecated/state). @hereinthehive Maybe you can open a separate issue for this concept? -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/118#issuecomment-1196528727 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 27 July 2022 10:05:49 UTC