Description
Open Community Working Meeting 2023-11-27 - 14:00 PT
Agenda:
| Topic | Owner | Decision/NextStep |
|---|---|---|
| Review last call's action items | [facilitator] | |
| json-schema-org/website#222 - Add a proposed mechanism for tracking known "quality" implementations. | @Julian | The team decided that the Community repo will suit better for this type of content. |
| json-schema-org/website#197 - Section on managing schema versions? | @benjagm | This will be added to a future FAQ page. |
| json-schema-org/website#133 - Add the typescript definitions generator to the list of implementations | @benjagm | Implementations will be added just with the implementers permission so Implementers should be the ones submitting the PR. |
Action items:
- Add a proposed mechanism for tracking known "quality" implementations. website#222 will be moved to the community repo. @Julian
- Section on managing schema versions? website#197 will be closed clarifying that versioning is an engineering concept, no JSON Schema concept. The recommendation is schemas to stay immutable, and incase of need versioning create a new file with a new id. This will be added as FAQ.
- We'll add old implementations to the source datamodel of the new implementers page so we have everything in one single database and we can better tune the data shown in the implementers page. Issue Re-build the JSON Schema Implementations page - (Design) website#160
Notes:
-
The meeting started with a conversation about JSON-e, the project @gregsdennis has been contributing with.
-
@benjagm shared some reminders including the presence of JSON Schema with a booth at API Days Paris 2023. This will be a collaboration with AsynAPI and OpenAPI and we are excited about it!
-
The team discussed whether a proposed mechanism for tracking quality implementations should be on the website or in the community repository. They concluded that it would be more suitable for the community repository as it is intended for internal use and further work based on the document.
-
The team discussed issue #197 regarding schema versioning. This has been asked many times and it's a great candidate for FAQ. This is a software engineering topic, not JSON Schema. They recommended that schemas should be immutable and new versions should be released as new files with new IDs, leaving the decision of how to manage it up to the users.
-
The team discussed issue #133. @benjagm asked for feedback about what to do in cases when we suggest an implementer to add the implementation to our page and we don'r receive response. The feedback was, Implementations will be added just with the implementers permission so Implementers should be the ones submitting the PR.
-
The team also considered the idea of including actively maintained implementations even if they are based on older versions of JSON schema, but acknowledged the challenge of determining which implementations are actively maintained. The decision was to add all the implementations to the datamodel of the new implementers page so we'll just decide what data will be shown: e.g. draft 07 and onwards.
Attendees
| Account |
|---|
| @gregsdennis |
| @Relequestual |
| @jdesrosiers |
| @benjagm |
| @Julian |
| @jviotti |