Open Community Working Meeting 2021-10-15

[Relequestual]

Open Community Working Meeting 2021-10-15 - 14:00 UTC

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

Agenda: Compiling!

Topic	Owner	Decision/NextStep
Review last call's action items #56	@Relequestual	All now complete. PRs pending for json-schema-org/json-schema-spec#1120
The cost of Slack is $792 mothly (previous action)	@Relequestual	Agreed it was too expensive. @jdesrosiers noted that we didn't have to be limited to one channel, and some do not like Slack. @Relequestual commented we should revisit this when/if we have staff to handle community management.
IDL Vocabulary SIG update	@jonaslagoni @jdesrosiers	Trying to work out the right approach. @jonaslagoni mostly wants convention based on existing JSON Schemas. @jonaslagoni shared some examples via screen share. @jdesrosiers suggested that convention only covers the most basic use case and "be boring", and if you want anything such as inheritance, you'll need to use new keywords to specify what you need.
Anyone want to write a blog post?	@Relequestual	@jdesrosiers would love to but is too busy. @jonaslagoni suggested there could be a cross post from the AsyncAPI blog.
What would our ideal AJV inheritance look like?	@Relequestual	We are still largly unsure about the best approach. We did agree if it is taken over, doing nothing with it would likely result in a community fork. @jdesrosiers suggested JTD isn't in active development so is likely not to cost much in terms of development. @Relequestual mentioned there would likely be a support cost. @jdesrosiers strongly believes that the JSON Schema org should not maintain any implementations, and just maintain the specification, not having an official implementation or picking favourites. @jonaslagoni suggested we should have an official tooling. @jonaslagoni mentioned he looks for tooling in a specifications organisation, but others dissagreed. @Relequestual noted that AsyncAPI is privilidged to have several full time staff and this is unusual for a specification. @jonaslagoni suggested that the tooling could be owned by the community but hosted under the org. @Relequestual argued that even if you tried to make it clear it was "community owned" tooling, there would be expectations attached if hosted under the JSON Schema org. Additionally that including in the org is endorsement, unless you have a separate "communty org". @jonaslagoni understood but dissagreed. Ultimatly @jdesrosiers would like to see AJV stay in its own org, and @Relequestual agreed

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.

Sticky agenda items:

Is anyone willing to take ownership over Issues and PRs in the 2020-12 draft-patch milestone? - @Relequestual

Action items:

• Check in with OpenJSF regarding Consider self publishing specifications and dropping "draft" prefix #69 - Legal advice?
• Follow up with @jonaslagoni regarding blog post cross posting from AsyncAPI blog (https://www.asyncapi.com/blog/json-schema-beyond-validation)

Notes:
AJV inheritance? There's a chance we may be able to "take over" AJV to some extent.
There has been some limited discussion about this internally. It may be JSON Schema org or Postman.
If we had full time staff, what would our ideal handover result look like?
Considerations include: Other AJV org repos, JDT, Community, OpenJS Foundation status, funds and sponsors.

Agenda Items rolling over / items for next meeting:

• Check in on The meaning of "additionalProperties" has changed #57

Recording: Meeting recording and transcript

[jonaslagoni]

Most of the updates around the IDL Vocabulary SIG update will revolve around discussing json-schema-org/vocab-idl#8 (comment) and come to an agreement (If we have time 😄)

[Relequestual]

Regarding...

Check in with OpenJSF regarding Consider self publishing specifications and dropping "draft" prefix #69 - Legal advice?

It would seem they are unable to issue legal advice in this capacity until we join them.
Understandable.

We have time to start the joining process before our planned publication date, so I'll get to work!

[Relequestual]

Next meeting: #71