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 2021-10-01 #56

Closed
3 tasks done
Relequestual opened this issue Sep 24, 2021 · 0 comments
Closed
3 tasks done

Open Community Working Meeting 2021-10-01 #56

Relequestual opened this issue Sep 24, 2021 · 0 comments
Labels
Working Meeting Identify working meetings

Comments

@Relequestual
Copy link
Member

Relequestual commented Sep 24, 2021

Open Community Working Meeting 2021-10-01 - 20:00 UTC

Zoom Meeting link: https://postman.zoom.us/j/82037276001

Agenda: Taking suggestions / compiling!
(WIP)

Topic Owner Decision/NextStep
Review last call's action items #45 @Relequestual We tried to get feedback on json-schema-org/json-schema-spec/issues/1120 (HyperSchema meta-schema problems), but had no comments from new individuals.
Agreed to proceed as @jdesrosiers sees fit. It's not clear there IS a general consensus to be had, other than it is broken.
How was API Specification Conference 2021 JSON Schema Open Discussion? #59 @jdesrosiers The most common question was "when will JSON Schema be 'done'?". This is mainly because we still publish to IETF and prefix release versions with "draft".
We discussed and agreed we would prefer to self publish and drop the "draft" versioning, as each release we publish is something we consider production worthy.
Jason also noted the vocabulary repo didn't include the OpenAPI vocabulary, which we agreed should be added.
Final call on PR "Add ADR for Code of Conduct" #41 @Relequestual There were no further comments and the PR was merged.
The meaning of "additionalProperties" has changed (draft-07 to 2019-09) #57 @Relequestual / @marksparkza We agreed that a strict reading of 2019-09 did not align with the intent, and was a bug. We agreed that fixing the bug would be a change, but only one that provides clarification. @karenetheridge suggested that the clarification/change would most likely align with how implementations work, and they likely would be not strictly following as written in 2020-12.
@jdesrosiers's implementation handles situation as intended using a different interpretation to that outlined in the issue, so we can justify a clarification change. @jdesrosiers agreed to write up an explanation for how his implementation handles this situation.
We did not reach consensus, so we need to revisit this at a future meeting after Jason has provided his write up.
Is anyone willing to take ownership over Issues and PRs in the 2020-12 draft-patch milestone? @Relequestual @jdesrosiers felt he was already too busy. @karenetheridge saw she was already assigned to one item, and would look to review it.
This agenda item will be recurring till resolved.

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:

Notes: None

Agenda Items rolling over: None

Sticky agenda items:

Full recording link - Highlights link
(Or use the first link, and click the "highlights" toggle in the bottom left of the video player. There is an issue where the highlights only video does not show the speakers name on the transcript.)

@Relequestual Relequestual pinned this issue Oct 1, 2021
@Relequestual Relequestual unpinned this issue Oct 12, 2021
@Relequestual Relequestual added the Working Meeting Identify working meetings label Oct 12, 2021
@Relequestual Relequestual changed the title Open Community Working Meeting 2021-10-01 - 20:00 UTC Open Community Working Meeting 2021-10-01 Oct 12, 2021
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

1 participant