json-schema-org / community

A space to discuss community and organisational related things
81 stars 34 forks source link

Open Community Working Meeting 2022-05-06 #172

Open Relequestual opened 2 years ago

Relequestual commented 2 years ago

📺 See Recording

Go To Previous Meeting

Agenda

Topic Owner Decisions/NextSteps
Review last call's action items @Relequestual The action items were reviewed
JSON Schema 2020-12 patch 1 rc-0 released
Feedback requested. rc-0 feedback closes 2022-05-14.
Is the release process looking ok? Spec Issue #1191
@Relequestual The updates can be found at Spec Issue #1191
Website development progress - Johannes showed progress on the office hours call. @Relequestual Website still in early stages and feedback stage would require setting up a process.
Staffing update #128 - Very likely:
- Two full time developers on JSON Schema
- One cross-specification developer and observer. Not dedicated 100% to JSON Schema
- One Technical Community Manager (TCM) / Developer Relations (DevRel)
Fully employed by Postman, part of Postman Open Technologies
@Relequestual Follow the updates at Community Issue #128 and checklist for 2022 Q1 at Community Issue #134
Legal query update Spec Issue #1160
OpenJS Foundation legal council recommended some clarifications and specifically "BSD 3-clause first, and AFL second".
Happy for anyone to action this. Will ask @karenetheridge first though
@Relequestual Follow Spec Issue #1160 for updates.
@handrews 's comments regarding ambiguous additionalProperties Spec Issue #1172 ? @Relequestual Find updates at Spec Issue #1172

Highlights

Actions

Attendees

Account
@Relequestual
@jdesrosiers
@jviotti

Details

Ambiguity of additionalProperties

In brief, comments by @handrews were summarized as "properties to have annotation regardless of the validation of the schema values."

For updates and clarifications follow this discussion


Legal Query

Members discussed and clarified the query regarding licensing of meta-schemas and test suite. The issue was raised because it was felt the boundaries were fuzzy^is1160. Fortunately, OpenJS Foundation have provided legal counsel and the right questions are being asked along with progress being made on the same.

Furthermore, any changes to future licensing requires a historical trace of all contributions and it is felt that a compelling reason for such a change is yet to be found besides there is nothing in the current licenses that is prohibitive to present work.


benjagm commented 1 year ago

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