Open Community Working Meeting 2023-07-10 - 14:00 PT

[benjagm]

Open Community Working Meeting 2023-07-10 - 14:00 PT

📺 See Recording

⏪ Go To Previous Meeting

Agenda:

Topic	Owner	Decision/NextStep
Review last call's action items	[facilitator]
Let's define "compatible releases" - Discussion #404	@jdesrosiers	@jdesrosiers will write up a proposed resolution for this discussion.
Proposal : Conflict resolution, CoC violation reporting and CoC enforcement - Discussion #319	@benjagm	@benjagm will send the PR related to #319.
#418 - Research of existing implementations by language	@Julian	Use the term recommended implementation vs high quality implementation. Adopt existing oss metrics frameworks but make sure we combine it with subjective judgement.
#435 - Dialect URIs for stable spec	@jdesrosiers	We need to remove /schema as was agreed years ago.

Action items:

• @jdesrosiers will write up a proposed resolution for this discussion Let's define "compatible releases" #404.
• @benjagm will send the PR related to Proposal : Conflict resolution, CoC violation reporting and CoC enforcement #319.

Notes:

• The team reviewed the action items of past session and the only pending action was to decide the approach to Convert the spec to Markdown #1335. @gregsdennis and @jdesrosiers reviewed different approaches. @gregsdennis preferred the simple markdown approach due to its ease of use and potential for accepting more contributions. @jdesrosiers suggested to run a POC to make sure simple markdown has the capabilities we need.
• The team reviewed the Discussion Let's define "compatible releases" #404 - Let's define "compatible releases" and Jason shared a preview of his definition of compatible release. @jdesrosiers will write up a proposed resolution for this discussion.
• The team reviewed the Discussion Proposal : Conflict resolution, CoC violation reporting and CoC enforcement #319 to improve CoC violation reporting and CoC enforcement and @benjagm committed to send a PR with the proposed changes.
• The team discussed the updates on the issue Research of existing implementations by language #418 , which involved researching existing implementations by language to determine what constitutes a high-quality implementation. The team discussed the challenges of evaluating the quality of different implementations and suggested existing metrics' frameworks to measure healthy open source projects as a standard approach. They also considered using shields.io to summarize information such as open issues and bug reports.
• @jdesrosiers suggested using recommended implementation vs high quality implementation to reinforce a positive message and everyone agreed. The team also considered the importance of human evaluation and subjective judgment in addition to automated checks.
• The session ended discussion Dialect URIs for stable spec #435 - Dialect URIs for stable spec. @Relequestual suggested getting rid of /schema, but it was revealed that it was still present despite a decision made years ago. The team discussed the need to remove a certain URI from their website due to high traffic and the possibility of incorporating the change into the new website. They also considered reaching out to people maintaining the code and visual studio for assistance and gathering more detailed data on direct downloads of schemas.

Attendees

Account
@jdesrosiers
@Relequestual
@benjagm
@gregsdennis
@jviotti

[benjagm]

I am updating as completed the action item with the resolution for the discussion #404.

See:
https://github.com/orgs/json-schema-org/discussions/404#discussioncomment-6420349

[benjagm]

Completed.