Description
Open Community Working Meeting 2024-04-22 - 14:00 PT
Agenda:
| Topic | Owner | Decision/NextStep |
|---|---|---|
| Review last call's action items | [facilitator] | |
| SDLC commentary | @egekorkan | The group agreed on continuing the discussion in some weeks. |
Action items:
- No actions items captured.
Notes:
Office Hours
The group discussed about the Office Hours proposal #575 providing positive feedback to the idea of adding APAC/America friendly timezones to the Office Hours.
Specifying development lifecycle
@egekorkan raised discussions on formalizing the spec development process. Key topics included feature readiness criteria, expiring proposals lacking implementations, and stability requirements. Greg outlined a draft process and sought consensus by a deadline.
Choosing a URI for meta schemas
The group discussed around identifier schemes for meta schemas. @jdesrosiers analyzed options while @gregsdennis favored non-URL URIs to clarify identifiers are not locators. @bhavukkalra felt this would reduce confusion for new users.
Proposing new features to the spec
The group discussed changing from core team proposals to taking proposals from implementations. This would better vet features through real-world use before standardizing them.
Defining annotations
@bhavukkalra sought clarity on annotation definitions. @gregsdennis explained annotations can provide both documentation and instructions for applications, like specifying interface elements. Formats illustrate this beyond simple documentation.
Improving getting started examples
@bhavukkalra proposed highlighting code blocks in examples to better guide users. Most supported this to more clearly show progress. Implementation requires customization of code block rendering.
Agenda Items rolling over:
- list
Attendees:
| Account |
|---|
| @gregsdennis |
| @benjagm |
| @jviotti |
| @bhavukkalra |
| @Relequestual |
| @egekorkan |
| @DhairyaMajmudar |
| @Era-cell |