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

Bjørn Madsen via GitHub

• [community-group] Pull Request: Remove `Duration` from types to do list (Tuesday, 4 January)

Danny Banks via GitHub

• Re: [community-group] Disambiguate RFC 2119 keywords where appropriate (#77) (Friday, 7 January)
• Re: [community-group] Token name - reserved words (#61) (Friday, 7 January)
• Re: [community-group] Group & file level properties (#72) (Friday, 7 January)

Donna Vitan via GitHub

• Re: [community-group] Token name - reserved words (#61) (Tuesday, 11 January)
• Re: [community-group] Disambiguate RFC 2119 keywords where appropriate (#77) (Tuesday, 11 January)

Drew Powers via GitHub

• Re: [community-group] Typography type feedback (#102) (Thursday, 27 January)
• Re: [community-group] Optional "tags" property on tokens (#109) (Thursday, 27 January)
• Re: [community-group] Group format (#105) (Tuesday, 18 January)
• Re: [community-group] Example json files? (#82) (Saturday, 15 January)
• Re: [community-group] [RFC] Theming (#2) (Thursday, 13 January)
• Re: [community-group] Gradient type feedback (#101) (Thursday, 13 January)
• Re: [community-group] Shadow type feedback (#100) (Thursday, 13 January)
• Re: [community-group] How to do tokens that share a name with a group (#97) (Wednesday, 12 January)
• Re: [community-group] [RFC] Theming (#2) (Wednesday, 12 January)
• Closed: [community-group] YAML as an alternate format (#92) (Saturday, 8 January)
• Re: [community-group] YAML as an alternate format (#92) (Saturday, 8 January)
• Re: [community-group] High contrast colors (#91) (Friday, 7 January)
• Re: [community-group] High contrast colors (#91) (Friday, 7 January)
• [community-group] YAML as an alternate format (#92) (Friday, 7 January)

Ivan Maksimovic via GitHub

• Re: [community-group] Token name - reserved words (#61) (Wednesday, 19 January)
• Re: [community-group] Token name - reserved words (#61) (Friday, 14 January)

James Nash via GitHub

• Re: [community-group] Can extensions be applied on the group level? (#106) (Tuesday, 25 January)
• Re: [community-group] Reserve top-level `$schema` property? (#107) (Tuesday, 25 January)
• Re: [community-group] WIP: Add data model section (#93) (Tuesday, 25 January)
• Re: [community-group] Capitalize RFC 2119 keywords when appropriate (#94) (Tuesday, 25 January)
• Closed: [community-group] Token types - optional or required (#63) (Thursday, 20 January)
• Re: [community-group] Token types - optional or required (#63) (Thursday, 20 January)
• Re: [community-group] Should the spec include more semantic types? (#104) (Tuesday, 18 January)
• Re: [community-group] Should the spec include more semantic types? (#104) (Monday, 17 January)
• Re: [community-group] Token name - reserved words (#61) (Monday, 17 January)
• Re: [community-group] How to do tokens that share a name with a group (#97) (Monday, 17 January)
• Re: [community-group] How to do tokens that share a name with a group (#97) (Monday, 17 January)
• Re: [community-group] How to do tokens that share a name with a group (#97) (Thursday, 13 January)
• Re: [community-group] How to do tokens that share a name with a group (#97) (Thursday, 13 January)
• Re: [community-group] How to do tokens that share a name with a group (#97) (Thursday, 13 January)
• Re: [community-group] How to do tokens that share a name with a group (#97) (Thursday, 13 January)
• Re: [community-group] WIP: Update composite types chapter to reflect decision made on issue #63 (#86) (Thursday, 13 January)
• [community-group] Transition type feedback (#103) (Thursday, 13 January)
• [community-group] Typography type feedback (#102) (Thursday, 13 January)
• [community-group] Gradient type feedback (#101) (Thursday, 13 January)
• [community-group] Shadow type (#100) (Thursday, 13 January)
• [community-group] Border type (#99) (Thursday, 13 January)
• [community-group] Stroke style type (#98) (Thursday, 13 January)
• Re: [community-group] Token name - reserved words (#61) (Wednesday, 12 January)
• Re: [community-group] How to do tokens that share a name with a group (#97) (Wednesday, 12 January)
• [community-group] How to do tokens that share a name with a group (#97) (Wednesday, 12 January)
• Re: [community-group] Token name - reserved words (#61) (Saturday, 8 January)
• [community-group] Pull Request: WIP: Add data model section (Saturday, 8 January)
• Re: [community-group] YAML as an alternate format (#92) (Saturday, 8 January)
• Re: [community-group] High contrast colors (#91) (Saturday, 8 January)
• [community-group] Merged Pull Request: Remove `Duration` from types to do list (Wednesday, 5 January)
• Re: [community-group] Group & file level properties (#72) (Monday, 3 January)
• [community-group] Pull Request: Moves group properties into a metadata property (Monday, 3 January)
• Re: [community-group] WIP: Update composite types chapter to reflect decision made on issue #63 (#86) (Monday, 3 January)

Kaelig Deloumeau-Prigent via GitHub

• [community-group] Merged Pull Request: Capitalize RFC 2119 keywords when appropriate (Tuesday, 25 January)
• Closed: [community-group] Disambiguate RFC 2119 keywords where appropriate (#77) (Tuesday, 25 January)
• Re: [community-group] Capitalize RFC 2119 keywords when appropriate [redux] (#96) (Monday, 10 January)
• [community-group] Closed Pull Request: Capitalize RFC 2119 keywords when appropriate [redux] (Monday, 10 January)
• [community-group] Pull Request: Capitalize RFC 2119 keywords when appropriate [redux] (Monday, 10 January)
• [community-group] Merged Pull Request: Update dependencies and override colors version to the latest good one (Monday, 10 January)
• [community-group] Pull Request: Update dependencies and override colors version to the latest good one (Monday, 10 January)
• [community-group] Pull Request: Capitalize RFC 2119 keywords when appropriate (Monday, 10 January)

Kevin Powell via GitHub

• [community-group] Final revisions before next draft (#108) (Tuesday, 25 January)
• [community-group] Closed Pull Request: Moves group properties into a metadata property (Tuesday, 25 January)
• Re: [community-group] Group & file level properties (#72) (Tuesday, 25 January)
• Closed: [community-group] Group & file level properties (#72) (Tuesday, 25 January)
• Re: [community-group] Group & file level properties (#72) (Tuesday, 25 January)
• Re: [community-group] Token name - reserved words (#61) (Tuesday, 25 January)
• Closed: [community-group] Token name - reserved words (#61) (Tuesday, 25 January)
• Re: [community-group] Capitalize RFC 2119 keywords when appropriate (#94) (Monday, 24 January)
• Re: [community-group] WIP: Add data model section (#93) (Monday, 24 January)
• Re: [community-group] update(spec): Add `type` property to file and group levels (#87) (Monday, 3 January)
• Re: [community-group] Disambiguate RFC 2119 keywords where appropriate (#77) (Monday, 3 January)
• Re: [community-group] Group & file level properties (#72) (Monday, 3 January)
• Re: [community-group] Token name - reserved words (#61) (Monday, 3 January)

Louis Chenais via GitHub

• Re: [community-group] Loosen up the color type (#79) (Thursday, 20 January)
• Re: [community-group] Token name - reserved words (#61) (Friday, 7 January)
• Re: [community-group] Group & file level properties (#72) (Friday, 7 January)
• Re: [community-group] Moves group properties into a metadata property (#89) (Friday, 7 January)
• Re: [community-group] update(spec): Add `type` property to file and group levels (#87) (Monday, 3 January)
• [community-group] Merged Pull Request: update(spec): Add `type` property to file and group levels (Monday, 3 January)

Matthew Ström via GitHub

• Re: [community-group] Typography type feedback (#102) (Tuesday, 25 January)
• [community-group] Group format (#105) (Tuesday, 18 January)
• Re: [community-group] How to do tokens that share a name with a group (#97) (Tuesday, 18 January)
• Re: [community-group] Token name - reserved words (#61) (Tuesday, 18 January)
• Re: [community-group] How to do tokens that share a name with a group (#97) (Friday, 14 January)
• Re: [community-group] [RFC] Theming (#2) (Thursday, 13 January)
• Re: [community-group] Token name - reserved words (#61) (Thursday, 13 January)
• Re: [community-group] How to do tokens that share a name with a group (#97) (Thursday, 13 January)
• Re: [community-group] [RFC] Theming (#2) (Wednesday, 12 January)
• Re: [community-group] High contrast colors (#91) (Wednesday, 12 January)
• Re: [community-group] High contrast colors (#91) (Tuesday, 11 January)
• Re: [community-group] Should composites be part of the MVP specification? (#54) (Tuesday, 11 January)
• Re: [community-group] High contrast colors (#91) (Tuesday, 11 January)

Michael Fitzgerald via GitHub

• Re: [community-group] Should the spec include more semantic types? (#104) (Tuesday, 18 January)
• [community-group] Should the spec include more semantic types? (#104) (Friday, 14 January)
• Re: [community-group] Typography type feedback (#102) (Thursday, 13 January)

Nate Moore via GitHub

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

nesquarx via GitHub

• Re: [community-group] Token name - reserved words (#61) (Thursday, 13 January)

netlify[bot] via GitHub

• Re: [community-group] Capitalize RFC 2119 keywords when appropriate [redux] (#96) (Monday, 10 January)
• Re: [community-group] Update dependencies and override colors version to the latest good one (#95) (Monday, 10 January)
• Re: [community-group] Capitalize RFC 2119 keywords when appropriate (#94) (Monday, 10 January)
• Re: [community-group] WIP: Add data model section (#93) (Saturday, 8 January)
• Re: [community-group] Remove `Duration` from types to do list (#90) (Tuesday, 4 January)
• Re: [community-group] Moves group properties into a metadata property (#89) (Monday, 3 January)

Travis Spomer via GitHub

• Re: [community-group] Optional "tags" property on tokens (#109) (Saturday, 29 January)
• Re: [community-group] Optional "tags" property on tokens (#109) (Thursday, 27 January)
• Re: [community-group] Typography type feedback (#102) (Tuesday, 25 January)
• Re: [community-group] Reserve top-level `$schema` property? (#107) (Monday, 24 January)
• Re: [community-group] Token name - reserved words (#61) (Friday, 14 January)
• Re: [community-group] How to do tokens that share a name with a group (#97) (Friday, 14 January)
• Re: [community-group] How to do tokens that share a name with a group (#97) (Thursday, 13 January)
• Re: [community-group] High contrast colors (#91) (Tuesday, 11 January)
• Re: [community-group] High contrast colors (#91) (Tuesday, 11 January)
• Re: [community-group] High contrast colors (#91) (Friday, 7 January)
• Re: [community-group] High contrast colors (#91) (Friday, 7 January)
• [community-group] High contrast colors (#91) (Wednesday, 5 January)
• Re: [community-group] Pre-defined composite type for refering color modifications (e.g. rgba) (#88) (Wednesday, 5 January)

W3C Bot via GitHub

• Re: [community-group] Remove `Duration` from types to do list (#90) (Wednesday, 5 January)

Ward Meremans via GitHub

• Re: [community-group] Optional "tags" property on tokens (#109) (Friday, 28 January)
• [community-group] Optional "tags" property on tokens (#109) (Wednesday, 26 January)

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