-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open Community Working Meeting 2024-04-22 - 14:00 PT #699
Comments
I should be able to join this call and I would like to talk about https://github.com/orgs/json-schema-org/discussions/671 where I have put multiple comments. However, that is relevant only if @gregsdennis and @jdesrosiers are also available. It may be too administrative stuff for community-facing discussions so I am fine to arrange another call. |
Another point I have realized is that it would be nice to have an ics file with these meetings. I keep double-checking the exact time slot in my time zone and need to create a calendar entry anyway. |
@bhavukkalra Wanted to add this issue to the agenda and get some insights - json-schema-org/website#658 |
Also, Wanted to get more insights on what |
This is the PR to add this to the issue template: #705 |
Closing this issue as all tasks are completed. Thanks for your contributions! |
Open Community Working Meeting 2024-04-22 - 14:00 PT
📺 See Recording
⏪ Go To Previous Meeting
Agenda:
Action items:
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:
Attendees:
The text was updated successfully, but these errors were encountered: