public-design-tokens-log@w3.org from September 2021 by author

Alexander Vassbotn Røyne-Helgesen via GitHub

• Re: [community-group] The Designer’s Workflow (#43) (Sunday, 26 September)
• Re: [community-group] The Designer’s Workflow (#43) (Sunday, 26 September)
• Re: [community-group] [RFC] Glossary (#32) (Sunday, 26 September)
• Re: [community-group] [RFC] Glossary (#32) (Sunday, 26 September)
• Re: [community-group] [RFC] Design Token authoring tools (#36) (Saturday, 25 September)
• Re: [community-group] [RFC] Design Token authoring tools (#36) (Saturday, 25 September)
• Re: [community-group] Defining "design token" from a "technical" perspective (#42) (Saturday, 25 September)
• Re: [community-group] The Designer’s Workflow (#43) (Saturday, 25 September)
• Re: [community-group] The Designer’s Workflow (#43) (Saturday, 25 September)

Christian Martin Nies via GitHub

• Re: [community-group] Are token descriptions optional or required? (#62) (Tuesday, 28 September)
• Re: [community-group] Consider using grammarly or hemingway to make language more understandable/inclusive (#66) (Tuesday, 28 September)
• Re: [community-group] Are token descriptions optional or required? (#62) (Tuesday, 28 September)

Dale Sande / @anotheruiguy via GitHub

• Re: [community-group] [Format] Token types - optional or required (#63) (Thursday, 9 September)
• Re: [community-group] [Format] Token types - optional or required (#63) (Thursday, 9 September)
• Re: [community-group] [Format] Token name - reserved words (#61) (Thursday, 9 September)
• Re: [community-group] [Format] Token types - optional or required (#63) (Thursday, 9 September)
• Re: [community-group] [Format] Token types - optional or required (#63) (Thursday, 9 September)

Danny Banks via GitHub

• Re: [community-group] Prettier pre-commit hook (#57) (Tuesday, 14 September)
• [community-group] Closed Pull Request: Prettier pre-commit hook (Tuesday, 14 September)
• Re: [community-group] [Format] Token types - optional or required (#63) (Friday, 10 September)
• [community-group] Pull Request: Prettier pre-commit hook (Wednesday, 8 September)
• [community-group] Closed Pull Request: Adding prettier pre-commit hook (Wednesday, 8 September)
• [community-group] Pull Request: Adding prettier pre-commit hook (Wednesday, 8 September)
• Re: [community-group] Add composite types section (#52) (Wednesday, 8 September)
• [community-group] [Format] Object vs Array (#55) (Wednesday, 8 September)
• [community-group] [Format] Should composites be part of the MVP specification? (#54) (Wednesday, 8 September)

David Booth via GitHub

• Re: [community-group] Improve readability of RFC 2119 keywords (MUST, SHOULD…) (#65) (Tuesday, 21 September)
• Re: [community-group] Improve readability of RFC 2119 keywords (#68) (Tuesday, 21 September)

dom1n1k via GitHub

• Re: [community-group] Are token descriptions optional or required? (#62) (Monday, 27 September)

Fernando Poe Bellentani via GitHub

• Re: [community-group] Are token descriptions optional or required? (#62) (Tuesday, 28 September)

Ivan Maksimovic via GitHub

• Re: [community-group] Object vs Array (#55) (Thursday, 23 September)
• Re: [community-group] [Format] Object vs Array (#55) (Tuesday, 14 September)

James Nash via GitHub

• Re: [community-group] [Format] Token name character restrictions (#60) (Thursday, 16 September)
• [community-group] Merged Pull Request: Setup and editing instructions for technical reports (Tuesday, 14 September)
• Re: [community-group] Setup and editing instructions for technical reports (#75) (Tuesday, 14 September)
• Re: [community-group] [Format] Object vs Array (#55) (Tuesday, 14 September)
• Re: [community-group] [Format] Object vs Array (#55) (Tuesday, 14 September)
• [community-group] Pull Request: Setup and editing instructions for technical reports (Tuesday, 14 September)
• Re: [community-group] [Format] Group & file level properties (#72) (Tuesday, 14 September)
• Re: [community-group] [Format] Token value - string, number, array, object? (#58) (Monday, 13 September)
• Re: [community-group] Improve readability of RFC 2119 keywords (MUST, SHOULD…) (#65) (Monday, 13 September)
• Re: [community-group] [Format] Token name - reserved words (#61) (Monday, 13 September)
• Re: [community-group] [Format] Token types - optional or required (#63) (Monday, 13 September)
• Re: [community-group] Let's favor `strong` element over all caps for emphasis. (#65) (Monday, 13 September)
• Re: [community-group] [Format] Object vs Array (#55) (Wednesday, 8 September)
• [community-group] Closed Pull Request: Testing workflow (Tuesday, 7 September)
• [community-group] Merged Pull Request: Renamed vendor attribute to extensions (Tuesday, 7 September)
• [community-group] Pull Request: Renamed vendor attribute to extensions (Tuesday, 7 September)

Jina Anne via GitHub

• Re: [community-group] [RFC] Glossary (#32) (Sunday, 26 September)
• Re: [community-group] [RFC] Glossary (#32) (Sunday, 26 September)
• Closed: [community-group] [RFC] Glossary (#32) (Sunday, 26 September)
• Closed: [community-group] Defining "design token" from a "technical" perspective (#42) (Sunday, 26 September)
• Re: [community-group] Defining "design token" from a "technical" perspective (#42) (Sunday, 26 September)
• Re: [community-group] The Designer’s Workflow (#43) (Sunday, 26 September)
• Re: [community-group] Are token descriptions optional or required? (#62) (Sunday, 26 September)
• Re: [community-group] Consider using grammarly or hemingway to make language more understandable/inclusive (#66) (Sunday, 19 September)
• Re: [community-group] Improve readability of RFC 2119 keywords (#68) (Thursday, 16 September)
• Re: [community-group] Improve readability of RFC 2119 keywords (MUST, SHOULD…) (#65) (Tuesday, 14 September)
• Re: [community-group] [Format] Token name - reserved words (#61) (Tuesday, 14 September)
• Re: [community-group] [Format] Token name - reserved words (#61) (Monday, 13 September)
• Re: [community-group] Let's favor `strong` element over all caps for emphasis. (#65) (Monday, 13 September)
• Re: [community-group] [Format] Token types - optional or required (#63) (Thursday, 9 September)
• Re: [community-group] [Format] Token types - optional or required (#63) (Thursday, 9 September)
• Re: [community-group] [Format] Token name - reserved words (#61) (Thursday, 9 September)
• Re: [community-group] [Format] Token types - optional or required (#63) (Thursday, 9 September)
• Re: [community-group] Synchronize with latest version of google doc (#64) (Thursday, 9 September)
• [community-group] Consider using grammarly or hemingway to make language more understandable/inclusive (#66) (Thursday, 9 September)
• [community-group] Let's favor `strong` element over all caps for emphasis. (#65) (Thursday, 9 September)

Kaelig Deloumeau-Prigent via GitHub

• [community-group] [Format] Disambiguate RFC 2119 keywords where appropriate (#77) (Tuesday, 21 September)
• [community-group] Merged Pull Request: Remove stale roadmap (Monday, 20 September)
• Re: [community-group] Remove stale roadmap (#47) (Monday, 20 September)
• Re: [community-group] Consider using grammarly or hemingway to make language more understandable/inclusive (#66) (Friday, 17 September)
• Re: [community-group] Fix/intro grammar (#76) (Friday, 17 September)
• Closed: [community-group] Improve readability of RFC 2119 keywords (MUST, SHOULD…) (#65) (Thursday, 16 September)
• Re: [community-group] Improve readability of RFC 2119 keywords (MUST, SHOULD…) (#65) (Thursday, 16 September)
• [community-group] Merged Pull Request: Improve readability of RFC 2119 keywords (Thursday, 16 September)
• Re: [community-group] Improve readability of RFC 2119 keywords (#68) (Thursday, 16 September)
• [community-group] Merged Pull Request: Add Prettier pre-commit hook (#57 redux) (Tuesday, 14 September)
• [community-group] Pull Request: Add Prettier pre-commit hook (Monday, 13 September)
• Re: [community-group] Improve readability of RFC 2119 keywords (MUST, SHOULD…) (#65) (Monday, 13 September)
• [community-group] Merged Pull Request: Maintenance: add `validate` script, switch from `yarn` to `npm`, set default formatter for VS Code (Monday, 13 September)
• [community-group] Pull Request: Add `validate` script to check specs are valid (Monday, 13 September)
• [community-group] Pull Request: Test RFC-2119 styling (Monday, 13 September)
• Re: [community-group] Let's favor `strong` element over all caps for emphasis. (#65) (Monday, 13 September)
• [community-group] Merged Pull Request: Add composite types section (Saturday, 11 September)
• Re: [community-group] Prettier pre-commit hook (#57) (Thursday, 9 September)
• Closed: [community-group] [RFC] Format specification (#1) (Wednesday, 8 September)
• Re: [community-group] [RFC] Format specification (#1) (Wednesday, 8 September)
• Re: [community-group] Add composite types section (#52) (Wednesday, 8 September)
• [community-group] [Format] Type: font name (#53) (Tuesday, 7 September)
• [community-group] Pull Request: Add composite types section (Tuesday, 7 September)
• [community-group] Pull Request: Testing workflow (Tuesday, 7 September)

Kevin Powell via GitHub

• Re: [community-group] Fix/intro grammar (#76) (Monday, 20 September)
• [community-group] Closed Pull Request: Fix/intro grammar (Monday, 20 September)
• [community-group] Pull Request: Fix/intro grammar (Friday, 17 September)
• Re: [community-group] Consider using grammarly or hemingway to make language more understandable/inclusive (#66) (Friday, 17 September)
• Closed: [community-group] [Format] Token value - string, number, array, object? (#58) (Friday, 17 September)
• [community-group] Merged Pull Request: feat: add specificity to token types. closes #58 (Friday, 17 September)
• [community-group] Merged Pull Request: fix formatting issues in groups and types (Tuesday, 14 September)
• Closed: [community-group] Fix formatting issues (#67) (Tuesday, 14 September)
• [community-group] Pull Request: fix formatting issues in groups and types (Tuesday, 14 September)
• [community-group] Merged Pull Request: feat: link #72 to the spec (Tuesday, 14 September)
• [community-group] Pull Request: feat: link #72 to the spec (Tuesday, 14 September)
• Re: [community-group] [Format] Token types - optional or required (#63) (Tuesday, 14 September)
• Re: [community-group] [Format] Object vs Array (#55) (Tuesday, 14 September)
• [community-group] [Format] Group & file level properties (#72) (Tuesday, 14 September)
• Re: [community-group] [Format] Should composites be part of the MVP specification? (#54) (Tuesday, 14 September)
• [community-group] Pull Request: feat: add specificity to token types. closes #58 (Tuesday, 14 September)
• Re: [community-group] [Format] Token value - string, number, array, object? (#58) (Tuesday, 14 September)
• Re: [community-group] [Format] Token name - reserved words (#61) (Monday, 13 September)
• [community-group] Merged Pull Request: Synchronize with latest version of google doc (Thursday, 9 September)
• Re: [community-group] Synchronize with latest version of google doc (#64) (Thursday, 9 September)
• [community-group] Fix formatting issues noted on https://github.com/design-tokens/community-group/pull/64 (#67) (Thursday, 9 September)
• [community-group] Pull Request: Synchronize with latest version of google doc (Thursday, 9 September)
• [community-group] [Format] Token types - optional or required (#63) (Thursday, 9 September)
• Re: [community-group] [Format] Are token descriptions optional or required? (#62) (Thursday, 9 September)
• [community-group] [Format] Are token descriptions optional or required? (#62) (Thursday, 9 September)
• [community-group] [Format] Token name - reserved words (#61) (Thursday, 9 September)
• [community-group] [Format] Token name character restrictions (#60) (Thursday, 9 September)
• [community-group] [Format] Token name case sensitivity (#59) (Thursday, 9 September)
• [community-group] [Format] Token value - string, number, array, object? (#58) (Thursday, 9 September)
• Re: [community-group] [RFC] Format specification (#1) (Friday, 3 September)
• Re: [community-group] [RFC] Format specification (#1) (Friday, 3 September)
• Re: [community-group] [RFC] Format specification (#1) (Friday, 3 September)

Lucas Arundell via GitHub

• Re: [community-group] [Format] Type: font name (#53) (Tuesday, 7 September)

Lukas Oppermann via GitHub

• Re: [community-group] [Format] Should composites be part of the MVP specification? (#54) (Tuesday, 14 September)
• Re: [community-group] [Format] Should composites be part of the MVP specification? (#54) (Wednesday, 8 September)
• Re: [community-group] [RFC] Format specification (#1) (Friday, 3 September)
• Re: [community-group] [RFC] Format specification (#1) (Friday, 3 September)
• Re: [community-group] [RFC] Format specification (#1) (Friday, 3 September)

Matt Felten via GitHub

• Re: [community-group] [Format] Token types - optional or required (#63) (Thursday, 9 September)
• Re: [community-group] [Format] Token types - optional or required (#63) (Thursday, 9 September)
• Re: [community-group] [Format] Token name case sensitivity (#59) (Thursday, 9 September)

Nate Baldwin via GitHub

• Re: [community-group] The Designer’s Workflow (#43) (Saturday, 25 September)

netlify[bot] via GitHub

• Re: [community-group] Fix/intro grammar (#76) (Friday, 17 September)
• Re: [community-group] Setup and editing instructions for technical reports (#75) (Tuesday, 14 September)
• Re: [community-group] fix formatting issues in groups and types (#74) (Tuesday, 14 September)
• Re: [community-group] feat: link #72 to the spec (#73) (Tuesday, 14 September)
• Re: [community-group] feat: add specificity to token types. closes #58 (#71) (Tuesday, 14 September)
• Re: [community-group] Add Prettier pre-commit hook (#70) (Monday, 13 September)
• Re: [community-group] Add `validate` script to check specs are valid (#69) (Monday, 13 September)
• Re: [community-group] Test RFC-2119 styling (#68) (Monday, 13 September)
• Re: [community-group] Synchronize with latest version of google doc (#64) (Thursday, 9 September)
• Re: [community-group] Prettier pre-commit hook (#57) (Wednesday, 8 September)
• Re: [community-group] Adding prettier pre-commit hook (#56) (Wednesday, 8 September)
• Re: [community-group] Add composite types section (#52) (Tuesday, 7 September)
• Re: [community-group] Renamed vendor attribute to extensions (#51) (Tuesday, 7 September)
• Re: [community-group] Testing workflow (#50) (Tuesday, 7 September)

Nicolas Hoizey via GitHub

• Re: [community-group] [Format] Token types - optional or required (#63) (Thursday, 9 September)

Simon Bächler via GitHub

• [community-group] Loosen up the color type (#79) (Saturday, 25 September)
• Re: [community-group] Group & file level properties (#72) (Saturday, 25 September)

Sofi Valitova via GitHub

• [community-group] Value Definition Syntax for a tokens type (#78) (Friday, 24 September)
• Re: [community-group] Are token descriptions optional or required? (#62) (Friday, 24 September)
• Re: [community-group] Token name case sensitivity (#59) (Friday, 24 September)

Thomas Gossmann via GitHub

• Re: [community-group] Group & file level properties (#72) (Saturday, 25 September)
• Re: [community-group] Are token descriptions optional or required? (#62) (Saturday, 25 September)
• Re: [community-group] Should composites be part of the MVP specification? (#54) (Friday, 24 September)

Trevor Burnham via GitHub

• Re: [community-group] Group & file level properties (#72) (Monday, 27 September)

Zhao Lei via GitHub

• Re: [community-group] Group & file level properties (#72) (Wednesday, 22 September)

Last message date: Tuesday, 28 September 2021 12:13:15 UTC