Meeting Notes - March 1, 2023

[shiroinegai]

Attendees:

• @Balastrong (Leonardo)
• @fabiobiondi (Fabio)
• @gederer (Greg)
• @gilf (Gil)
• @gioboa (Giorgio)
• @nnelgxorz (Glenn)
• @Obvio (Amit)
• @shairez (Shai)
• @shiroinegai (Marcus)

Qwik Updates:

• Giorgio's JSWORLD 2023 talk is released, watch it!
• Shai has been speaking to companies about Qwik and Qwik UI and continuing work on component testing.
• Gil wrote a blog post on authentication for Qwik, read it too!
• Gil has also been busy with constructing a Qwik workshop.
• Greg is making steady progress with the Qwik Tutorial and would like to integrate Qwik UI with it.

Qwik UI Updates:

• Giorgio mentions that he has been more lenient with code reviews to reduce friction for new contributors and because the style guide has not been formalized.
• Giorgio has proposed adding danger package and codeowners-action after speaking with a React Native maintainer to improve the code review process. PR linter: add danger pkg #220 PR flow: add codeowners-action #221
• Gil added the headless Slider component. feat(component): added a new headless slider component #169
• With recent components from various contributors, Marcus observed recurring logic and behaviors and has been working on extracting them into a package like React Aria.
• Amit fixed Tooltip flickering and added the headless Menu component. Headless menu #158 [Bug-Fix:Tooltip-Flicker] Debounce showing/hiding the tooltip and css animation fix #159
• Leonardo submitted a PR regarding coding standards. docs(coding standards): define a coding standard for exposing components' props #173

Meeting Highlights:

• Shai encourages all contributors to start a squad on the task they are working on within the Qwikifiers discord server and to periodically update their progress there. Starting a squad isn't necessarily about leading the effort on a particular task but to provide visibility on its progress and to scope discussions surrounding it.
• Qwik UI design decisions should be driven by active consumers of it. Greg's Qwik Tutorial effort and Qwik UI's website and documentation will be the first use cases.
• A11y efforts need to be standardized and Greg offered to reach out to the community to look for a11y experts.
• Giorgio mentions having a template with a checklist which will help reviewers assess and approve PRs. Giorgio will also be leading a squad to formalize the style guide.
• Shai will be writing examples of testing with both Cypress and Storybook to decide which testing solution will be used for Qwik UI in the next meeting.
• Components should be classified into Primitives and Headless with Primitives extracted into its own package. add primitive package #223 Primitives could also include layout primitives and Amit will be experimenting with a grid-based one to begin with.
• A Behaviors package could also be introduced to share logic and behaviors for Headless components.
• Qwik UI website will be a fully custom one which also serves to provide a need-based direction for the implementation of more Qwik UI components. It will also provide a link to a live Storybook version to facilitate users consuming it as a design system.