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-03-18 - 14:00 PT #672

Closed
benjagm opened this issue Mar 12, 2024 · 2 comments
Closed

Open Community Working Meeting 2024-03-18 - 14:00 PT #672

benjagm opened this issue Mar 12, 2024 · 2 comments
Labels
Working Meeting Identify working meetings

Comments

@benjagm
Copy link
Collaborator

benjagm commented Mar 12, 2024

Open Community Working Meeting 2024-03-18 - 14:00 PT

📺 See Recording

Go To Previous Meeting

Agenda:

Topic Owner Decision/NextStep
Review last call's action items [facilitator]
I would like to hear the current status of the stable spec proposal that @gregsdennis and @jdesrosiers have been working on https://github.com/orgs/json-schema-org/discussions/671 @Relequestual Continue the proposal discussion.

Notes:

  • @gregsdennis presented the new spec development process including adding version numbers and a feature lifecycle model to minimize breaking changes. Questions were raised on terminology and next steps.

  • Feature lifecycle proposal: Greg proposed a detailed feature lifecycle model with stages from concept to removal. @miqui and @benjagm praised the work but sought clarification on applying existing issues and versioning experimental proposals.

  • Extracting incomplete features: Property dependencies and vocabularies will enter the proposal stage as incomplete features while output formats become a separate specification to improve human readability.

  • Implementation support requirements: Supporting a release requires all stable features, while experimental support is optional. Documentation must clarify support for proposals and deprecated features may remain required for some time.

  • Questions: Questions were raised on terminology, stalled proposals, versioning proposals, deprecated feature handling, and incentivizing experimental support. Clarification and discussion of these details will be important.

  • Next steps for documentation: Benjamin emphasized starting work on documentation for new extensibility features. The existing documentation strategy issue can be used to coordinate improving docs step-by-step based on feedback as the proposals progress.

Agenda Items rolling over:

Attendees:

Account
@gregsdennis
@jdesrosiers
@Julian
@miqui
@benjagm
@Relequestual
@jviotti
@benjagm benjagm added the Working Meeting Identify working meetings label Mar 12, 2024
@egekorkan
Copy link
Contributor

I would be interested in discussing a topic but I am not sure if I can join due to some travels I am doing that day and that it is a bit late in my time zone. The topic is how a specification or standardisation body can manage their resources given to users. Those resources include JSON Schemas among other things like ontologies, examples, test cases. Management means packaging, versioning and serving while maintaining consistency between the resources. This is coming from the W3C Web of Things but I really think that it is relatable to others and I want to get as many opinions as possible :)

@benjagm
Copy link
Collaborator Author

benjagm commented Mar 24, 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

2 participants