public-design-tokens-log@w3.org from January 2022 by date

Saturday, 29 January 2022

• Re: [community-group] Optional "tags" property on tokens (#109) Travis Spomer via GitHub

Friday, 28 January 2022

• Re: [community-group] Optional "tags" property on tokens (#109) Ward Meremans via GitHub

Thursday, 27 January 2022

• Re: [community-group] Typography type feedback (#102) Drew Powers via GitHub
• Re: [community-group] Optional "tags" property on tokens (#109) Travis Spomer via GitHub
• Re: [community-group] Optional "tags" property on tokens (#109) Drew Powers via GitHub

Wednesday, 26 January 2022

• [community-group] Optional "tags" property on tokens (#109) Ward Meremans via GitHub

Tuesday, 25 January 2022

• Re: [community-group] Can extensions be applied on the group level? (#106) James Nash via GitHub
• Re: [community-group] Reserve top-level `$schema` property? (#107) James Nash via GitHub
• Re: [community-group] WIP: Add data model section (#93) James Nash via GitHub
• Re: [community-group] Typography type feedback (#102) Travis Spomer via GitHub
• Re: [community-group] Typography type feedback (#102) Matthew Ström via GitHub
• [community-group] Final revisions before next draft (#108) Kevin Powell via GitHub
• [community-group] Closed Pull Request: Moves group properties into a metadata property Kevin Powell via GitHub
• Re: [community-group] Group & file level properties (#72) Kevin Powell via GitHub
• Closed: [community-group] Group & file level properties (#72) Kevin Powell via GitHub
• Re: [community-group] Group & file level properties (#72) Kevin Powell via GitHub
• Re: [community-group] Token name - reserved words (#61) Kevin Powell via GitHub
• Closed: [community-group] Token name - reserved words (#61) Kevin Powell via GitHub
• [community-group] Merged Pull Request: Capitalize RFC 2119 keywords when appropriate Kaelig Deloumeau-Prigent via GitHub
• Closed: [community-group] Disambiguate RFC 2119 keywords where appropriate (#77) Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] Capitalize RFC 2119 keywords when appropriate (#94) James Nash via GitHub

Monday, 24 January 2022

• Re: [community-group] Reserve top-level `$schema` property? (#107) Travis Spomer via GitHub
• Re: [community-group] Capitalize RFC 2119 keywords when appropriate (#94) Kevin Powell via GitHub
• Re: [community-group] WIP: Add data model section (#93) Kevin Powell via GitHub

Friday, 21 January 2022

• Re: [community-group] Reserve top-level `$schema` property? (#107) Nate Moore via GitHub
• [community-group] Reserve top-level `$schema` property? (#107) Nate Moore via GitHub
• [community-group] Can extensions be applied on the group level? (#106) Nate Moore via GitHub
• Re: [community-group] Should the spec include more semantic types? (#104) Nate Moore via GitHub
• Re: [community-group] Shadow type feedback (#100) Nate Moore via GitHub

Thursday, 20 January 2022

• Re: [community-group] Loosen up the color type (#79) Louis Chenais via GitHub
• Closed: [community-group] Token types - optional or required (#63) James Nash via GitHub
• Re: [community-group] Token types - optional or required (#63) James Nash via GitHub

Wednesday, 19 January 2022

• Re: [community-group] Token name - reserved words (#61) Ivan Maksimovic via GitHub

Tuesday, 18 January 2022

• Re: [community-group] Group format (#105) Drew Powers via GitHub
• [community-group] Group format (#105) Matthew Ström via GitHub
• Re: [community-group] How to do tokens that share a name with a group (#97) Matthew Ström via GitHub
• Re: [community-group] Token name - reserved words (#61) Matthew Ström via GitHub
• Re: [community-group] Should the spec include more semantic types? (#104) James Nash via GitHub
• Re: [community-group] Should the spec include more semantic types? (#104) Michael Fitzgerald via GitHub

Monday, 17 January 2022

• Re: [community-group] Should the spec include more semantic types? (#104) James Nash via GitHub
• Re: [community-group] Token name - reserved words (#61) James Nash via GitHub
• Re: [community-group] How to do tokens that share a name with a group (#97) James Nash via GitHub
• Re: [community-group] How to do tokens that share a name with a group (#97) James Nash via GitHub

Saturday, 15 January 2022

• Re: [community-group] Example json files? (#82) Drew Powers via GitHub

Friday, 14 January 2022

• Re: [community-group] How to do tokens that share a name with a group (#97) Matthew Ström via GitHub
• Re: [community-group] Token name - reserved words (#61) Travis Spomer via GitHub
• Re: [community-group] Token name - reserved words (#61) Ivan Maksimovic via GitHub
• Re: [community-group] How to do tokens that share a name with a group (#97) Travis Spomer via GitHub
• [community-group] Should the spec include more semantic types? (#104) Michael Fitzgerald via GitHub

Thursday, 13 January 2022

• Re: [community-group] How to do tokens that share a name with a group (#97) James Nash via GitHub
• Re: [community-group] How to do tokens that share a name with a group (#97) James Nash via GitHub
• Re: [community-group] Typography type feedback (#102) Michael Fitzgerald via GitHub
• Re: [community-group] How to do tokens that share a name with a group (#97) James Nash via GitHub
• Re: [community-group] How to do tokens that share a name with a group (#97) James Nash via GitHub
• Re: [community-group] [RFC] Theming (#2) Drew Powers via GitHub
• Re: [community-group] WIP: Update composite types chapter to reflect decision made on issue #63 (#86) James Nash via GitHub
• [community-group] Transition type feedback (#103) James Nash via GitHub
• Re: [community-group] Gradient type feedback (#101) Drew Powers via GitHub
• Re: [community-group] Shadow type feedback (#100) Drew Powers via GitHub
• [community-group] Typography type feedback (#102) James Nash via GitHub
• [community-group] Gradient type feedback (#101) James Nash via GitHub
• [community-group] Shadow type (#100) James Nash via GitHub
• [community-group] Border type (#99) James Nash via GitHub
• [community-group] Stroke style type (#98) James Nash via GitHub
• Re: [community-group] How to do tokens that share a name with a group (#97) Travis Spomer via GitHub
• Re: [community-group] [RFC] Theming (#2) Matthew Ström via GitHub
• Re: [community-group] Token name - reserved words (#61) nesquarx via GitHub
• Re: [community-group] Token name - reserved words (#61) Matthew Ström via GitHub
• Re: [community-group] How to do tokens that share a name with a group (#97) Matthew Ström via GitHub

Wednesday, 12 January 2022

• Re: [community-group] How to do tokens that share a name with a group (#97) Drew Powers via GitHub
• Re: [community-group] [RFC] Theming (#2) Drew Powers via GitHub
• Re: [community-group] Token name - reserved words (#61) James Nash via GitHub
• Re: [community-group] How to do tokens that share a name with a group (#97) James Nash via GitHub
• [community-group] How to do tokens that share a name with a group (#97) James Nash via GitHub
• Re: [community-group] [RFC] Theming (#2) Matthew Ström via GitHub
• Re: [community-group] High contrast colors (#91) Matthew Ström via GitHub

Tuesday, 11 January 2022

• Re: [community-group] High contrast colors (#91) Travis Spomer via GitHub
• Re: [community-group] High contrast colors (#91) Matthew Ström via GitHub
• Re: [community-group] Should composites be part of the MVP specification? (#54) Matthew Ström via GitHub
• Re: [community-group] High contrast colors (#91) Travis Spomer via GitHub
• Re: [community-group] High contrast colors (#91) Matthew Ström via GitHub
• Re: [community-group] Token name - reserved words (#61) Donna Vitan via GitHub
• Re: [community-group] Disambiguate RFC 2119 keywords where appropriate (#77) Donna Vitan via GitHub

Monday, 10 January 2022

• Re: [community-group] Capitalize RFC 2119 keywords when appropriate [redux] (#96) Kaelig Deloumeau-Prigent via GitHub
• [community-group] Closed Pull Request: Capitalize RFC 2119 keywords when appropriate [redux] Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] Capitalize RFC 2119 keywords when appropriate [redux] (#96) netlify[bot] via GitHub
• [community-group] Pull Request: Capitalize RFC 2119 keywords when appropriate [redux] Kaelig Deloumeau-Prigent via GitHub
• [community-group] Merged Pull Request: Update dependencies and override colors version to the latest good one Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] Update dependencies and override colors version to the latest good one (#95) netlify[bot] via GitHub
• [community-group] Pull Request: Update dependencies and override colors version to the latest good one Kaelig Deloumeau-Prigent via GitHub
• Re: [community-group] Capitalize RFC 2119 keywords when appropriate (#94) netlify[bot] via GitHub
• [community-group] Pull Request: Capitalize RFC 2119 keywords when appropriate Kaelig Deloumeau-Prigent via GitHub

Saturday, 8 January 2022

• Closed: [community-group] YAML as an alternate format (#92) Drew Powers via GitHub
• Re: [community-group] YAML as an alternate format (#92) Drew Powers via GitHub
• Re: [community-group] Token name - reserved words (#61) James Nash via GitHub
• Re: [community-group] WIP: Add data model section (#93) netlify[bot] via GitHub
• [community-group] Pull Request: WIP: Add data model section James Nash via GitHub
• Re: [community-group] YAML as an alternate format (#92) James Nash via GitHub
• Re: [community-group] High contrast colors (#91) James Nash via GitHub

Friday, 7 January 2022

• Re: [community-group] High contrast colors (#91) Travis Spomer via GitHub
• Re: [community-group] High contrast colors (#91) Drew Powers via GitHub
• Re: [community-group] High contrast colors (#91) Travis Spomer via GitHub
• Re: [community-group] High contrast colors (#91) Drew Powers via GitHub
• [community-group] YAML as an alternate format (#92) Drew Powers via GitHub
• Re: [community-group] Token name - reserved words (#61) Louis Chenais via GitHub
• Re: [community-group] Group & file level properties (#72) Louis Chenais via GitHub
• Re: [community-group] Moves group properties into a metadata property (#89) Louis Chenais via GitHub
• Re: [community-group] Disambiguate RFC 2119 keywords where appropriate (#77) Danny Banks via GitHub
• Re: [community-group] Token name - reserved words (#61) Danny Banks via GitHub
• Re: [community-group] Group & file level properties (#72) Danny Banks via GitHub

Wednesday, 5 January 2022

• [community-group] Merged Pull Request: Remove `Duration` from types to do list James Nash via GitHub
• Re: [community-group] Remove `Duration` from types to do list (#90) W3C Bot via GitHub
• [community-group] High contrast colors (#91) Travis Spomer via GitHub
• Re: [community-group] Pre-defined composite type for refering color modifications (e.g. rgba) (#88) Travis Spomer via GitHub

Tuesday, 4 January 2022

• Re: [community-group] Remove `Duration` from types to do list (#90) netlify[bot] via GitHub
• [community-group] Pull Request: Remove `Duration` from types to do list Bjørn Madsen via GitHub

Monday, 3 January 2022

• Re: [community-group] Group & file level properties (#72) James Nash via GitHub
• Re: [community-group] Moves group properties into a metadata property (#89) netlify[bot] via GitHub
• [community-group] Pull Request: Moves group properties into a metadata property James Nash via GitHub
• Re: [community-group] WIP: Update composite types chapter to reflect decision made on issue #63 (#86) James Nash via GitHub
• Re: [community-group] update(spec): Add `type` property to file and group levels (#87) Louis Chenais via GitHub
• [community-group] Merged Pull Request: update(spec): Add `type` property to file and group levels Louis Chenais via GitHub
• Re: [community-group] update(spec): Add `type` property to file and group levels (#87) Kevin Powell via GitHub
• Re: [community-group] Disambiguate RFC 2119 keywords where appropriate (#77) Kevin Powell via GitHub
• Re: [community-group] Group & file level properties (#72) Kevin Powell via GitHub
• Re: [community-group] Token name - reserved words (#61) Kevin Powell via GitHub

Last message date: Saturday, 29 January 2022 02:57:36 UTC