Open Community Working Meeting 2021-09-03

[Relequestual]

Open Community Working Meeting 2021-09-03 - 20:00 UTC

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

Agenda:

Topic	Owner	Decision/NextStep
Issue and PR templates PR review #36	@Relequestual	After merge, we should review in 6 months to see if it was helpful or not. - @jdesrosiers Others to look at PR outside of meeting.
draft-patch Milestone 9 - Our 3 month over due patch release?	@handrews ? / @Relequestual	Continue this work without waiting for Henry. @Relequestual will drive this work.
Minimal Hyper-Schema support json-schema-org/json-schema-spec#1120	@jdesrosiers	Agreed this sounds OK to do. @jdesrosiers to create new meta-schema for Hyper-Schema
Any thoughts on how to collect issues for discussion? Tagging and GitHub actions?	@Relequestual	@jdesrosiers is happy with manual agenda creation. @rjmill suggested we make clear how people request things be added to the agenda.
Remove $dynamicRef bookending requirement json-schema-org/json-schema-spec#1064	@jdesrosiers	Struggle to remember details, but we seemed to agree this would be a good change. General commitment to go back and review the proposal. @Relequestual @karenetheridge
How could/should we spend our OpenCollective funds?	@Relequestual	@Relequestual suggested sponsoring implementers. @jdesrosiers agreed, and suggested sponsoring spec authors too, but unsure how it might be done fairly.
JSON Schema GitHub badges (shields.io)?	@Relequestual	Not discussed.

AOB?
Please add a comment if you have any other business.

Action items:

• Set reminder to review Issue and PR templates in 6 months time - @Relequestual #46
• Review Add Issue and Pull Request templates, mainly for ADRs #36 - @karenetheridge
• Make clear @Relequestual owns https://github.com/json-schema-org/json-schema-spec/milestone/9 (Maybe use org level "Projects") - @Relequestual
• Review the discussion on patch/release cycle (Patch release process (fixes without changing meta-schema or test compliance) and branch usage #7) and comment/confirm if the patch release will keep it's "draft [date]" identifier - @Relequestual
• Create Discussion about meta-schema release strategy between spec releases - @jdesrosiers
• Create PR for updated Hyper-Schema meta-schema JSON Hyper-Schema Needs Schema Version Parity json-schema-spec#1120 - @jdesrosiers
• Create discussion with a suggestion on how to organise and collect agenda items - @Relequestual
• Review proposal regarding removing $dynamicRef bookending Remove $dynamicRef bookending requirement json-schema-spec#1064 - @Relequestual @karenetheridge
• Set up regular task to move advertising income from advert system to our Open Collective fund - @Relequestual
• Find out how other groups/projects distribute money between maintainers/contributors (OpenJSF and Open Collective) - @Relequestual
• Determine how much it would cost to unlock Slack history and create Discussion - @Relequestual

Notes:

• As part of looking at the spec patch release process, we discussed our current meta-schema release process, and if we should consider a different approach
• @jdesrosiers mentioned that we did a "patch draft" release for draft-07. We can see this here: https://json-schema.org/specification-links.html
• Regarding spending of funds, @jdesrosiers suggested a web designer. @Relequestual asked if there was enough funds for that, but @jdesrosiers suggested someone from the community might want to contribute, and we could give something for their efforts. @rjmill suggested they might need tools paid for. @rjmill suggested we might be able to pay for slack history access, but @Relequestual isn't sure this would be viable or a good use of funds. @Relequestual hopes we can re-apply for open source access once we join the OpenJS Foundation. @ssilverman has tried to back-channel for Slack, but no luck.

Agenda Items rolling over:

• Add propertyDependencies keyword Proposal: Add propertyDependencies keyword (aka discriminator) json-schema-spec#1082 - @jdesrosiers
• Add optional keyword Suggestion: optional keyword to complement required json-schema-spec#1112 - @jdesrosiers

I decided not to roll over discussing "JSON Schema GitHub badges".

Recording: https://postman.zoom.us/rec/share/gnlMftNX8x8wLX_sYEBrPJ9Eu_Lw9Q2y9r8WTR5ZgZTEQY2mIFsHYBIxjzq0-31z.CumKsx6VZpHGVHOC

[jdesrosiers]

Here are some issues that would benefit from some discussion.

Minimal Hyper-Schema support: json-schema-org/json-schema-spec#1120
Remove $dynamicRef bookending requirement json-schema-org/json-schema-spec#1064
Add propertyDependencies keyword json-schema-org/json-schema-spec#1082
Add optional keyword json-schema-org/json-schema-spec#1112

[karenetheridge]

I would suggest adding a GH label for "working meeting" (perhaps including a specific meeting date? or leave it open) and then others can tag issues and PRs for review as appropriate.

[jdesrosiers]

Here's the link to the discussion about meta-schema release strategy. (It was unreasonably hard to find)

json-schema-org/json-schema-spec#1089 (comment)

[Relequestual]

Here's the link to the discussion about meta-schema release strategy. (It was unreasonably hard to find)

json-schema-org/json-schema-spec#1089 (comment) - @jdesrosiers

Thanks for digging that up!
It looks like there's more discussion needed to work out how we feel meta-schema releases should work.
Can you create a new Discussion on the community repo please @jdesrosiers ?

After reading the linked issue, what you were saying makes things a lot clearer.

[Relequestual]

Today, it would cost us $792 monthly or $7,920 yearly to unlock slack history... yikes.
I've found we DO for some reason have $54.90 credit. No idea where from. Maybe someone put some money in the bank so to speak. It says in the settings that any member can pay for slack, and there's a "bitcoin" in the address 🤷‍♂️