Closed
Description
Open Community Working Meeting 2022-03-18 - 12:00 PT (In your time zone)
Zoom Meeting link: https://postman.zoom.us/meeting/register/tZYtfuqurD4tGNR1mNO01r171rLCylRbDYEu
Agenda: Compiling!
| Topic | Owner | Decision/NextStep |
|---|---|---|
| Review last call's action items | @Relequestual | |
| "ambiguous behaviour of additionalProperties when invalid" - json-schema-spec/#1172 | @Relequestual | @jdesrosiers the minimum we could do right now for the patch release is to acknowledge and accept that two approaches and results are allowable @Relequestual I don't want to push through a far reaching change without giving plenty of time to review. We don't have time to review implications of such a change for the overdue patch release. Most people: It would be easier to make changes with confidence if we had test suite for the Output format @jdesrosiers I wonder what if we defined the output format as a separate specification? This would allow people to use tools linked to a specific output format version and not be locked to a specific version of JSON Schema (assuming the implementation provided valid Output). @Relequestual |
| Getting started in Node.js article draft json-schema-org/blog#9 | @Relequestual | Everyone was invited to review the PR. |
AOB?
If you want to discuss any other business not on the agenda, please add comments during the meeting.
If we do not complete the agenda, your discussion item will likely be rolled over to the next call.
Action items:
- Update #1172 on discussion here (done)
- Chat with @gregsdennis about the prospect of making the Output format its own spec
- Find out if Linux Foundation (or OpenJSF) if they have any templates of processes for awarding grants for work
Notes:
@Relequestual - We should have our Technical Community Manager onboard first before investing much time on investigating the options and prior art for running a grant system.
Agenda Items rolling over: None
Recording: link