Skip to content
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

Closed
benjagm opened this issue Apr 16, 2024 · 6 comments
Closed

Open Community Working Meeting 2024-04-22 - 14:00 PT #699

benjagm opened this issue Apr 16, 2024 · 6 comments
Labels
Working Meeting Identify working meetings

Comments

@benjagm
Copy link
Collaborator

benjagm commented Apr 16, 2024

Open Community Working Meeting 2024-04-22 - 14:00 PT

📺 See Recording

Go To Previous Meeting

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
@benjagm benjagm added the Working Meeting Identify working meetings label Apr 16, 2024
@egekorkan
Copy link

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.

@egekorkan
Copy link

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.

@benjagm
Copy link
Collaborator Author

benjagm commented Apr 22, 2024

@bhavukkalra Wanted to add this issue to the agenda and get some insights - json-schema-org/website#658

@bhavukkalra
Copy link

bhavukkalra commented Apr 22, 2024

Also, Wanted to get more insights on what Annotation and Annotation (Keywords) means. Relating to it this PR - json-schema-org/website#668

@benjagm
Copy link
Collaborator Author

benjagm commented Apr 25, 2024

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.

This is the PR to add this to the issue template: #705

@benjagm
Copy link
Collaborator Author

benjagm commented Apr 28, 2024

Closing this issue as all tasks are completed. Thanks for your contributions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Working Meeting Identify working meetings
Projects
None yet
Development

No branches or pull requests

3 participants