Open Community Working Meeting 2022-05-06

[Relequestual]

📺 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

• Feedback on patch release and process for JSON Schema 2020-12 patch 1 rc-0 Read Here.

• Updates shared regarding progress on website

  • More content is being added

  • Docs section got additions

  • Website is not yet in feedback stage and an appropriate process for the same would be decided at later stage.

  • JSON Schema specific syntax highlighting is being looked into.

• Brief updates regarding staffing.

• Clarification and update on legal query regarding licensing of meta-schemas and test-suites.

Actions

• Review patch release process and branch naming. If need be ratify the same.

• Ask if future releases can have different licensing than past

• Mail out arguments both for and against, seek feedback regarding ambiguity in additionalProperties

• Feedback from community awaited on the patch for another week before merge

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¹. 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.

---

Footnotes

1. https://github.com/json-schema-org/json-schema-spec/issues/1160 ↩

[benjagm]

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

[github-actions]

Hello! 👋

This issue has been automatically marked as stale due to inactivity 😴

It will be closed in 180 days if no further activity occurs. To keep it active, please add a comment with more details.

There can be many reasons why a specific issue has no activity. The most probable cause is a lack of time, not a lack of interest.

Let us figure out together how to push this issue forward. Connect with us through our slack channel : https://json-schema.org/slack

Thank you for your patience ❤️