- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Tue, 12 Jul 2022 16:31:44 +0000
- To: public-design-tokens-log@w3.org
> Re: encoding something like Experimental → Active → Deprecated → Sunset → Deleted in the spec: this is brittle because different teams have (sometimes very) different ideas of what the right life cycle states should be. If we go this way, the states will need to be configurable and not fixed. I agree. But this this is only problematic if you can only have one `state` at a time. If you `state` is just a grouping of properties and `deprecated` is part of that I think it can work for everyone. Standardising around a set states will be required as this in turn makes it possible for tools to hook into these. Some of these also don't make much sense imo. - `Active` is no state - `Sunset` is just `Deprecated` but louder? - `Deleted` isn't needed. Just delete the token. If you want a "trash folder" you can create a separate tokens file for this purpose. -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/118#issuecomment-1181989741 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 12 July 2022 16:31:46 UTC