Open Community Working Meeting 2022-09-26

[Relequestual]

Open Community Working Meeting 2022-09-26 - 14:00 PT

Zoom Meeting link: https://postman.zoom.us/j/89562933116?pwd=OWlsQ0RrcDY4S1JQU2d2Q2M0aFFlZz09

Agenda:

Topic	Owner	Decision/NextStep
Review last call's action items	[facilitator]

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.

Actions and Minutes

Go To Previous Meeting

Hightlights

• ADR decoupling from IETF and updates made to PR 1277
• Should specification be a living document with snapshots ?
• Use of normative language like IETF's RFC 2119¹ and its update on keyword capitalization RFC 8174.²
• How to better prioritize issues, PRs, discussions as an organizational practice, methods touched upon were dedicated slack channel, pinned posts, notifications and labelling.
• Discussion on SDLC (Specification Development Life Cycle) was deferred for later. Follow the Discussion.

Actions

• Decide on specification document governance model
• Decide on use of normative language
• Discuss SDLC
• Have some place to highlight current areas of focus or interest #248
• @relequestual's thoughts to PR 1277 regarding W3C. Read
• PR 1277 closed

Attendees

Name	Account
Ben Hutton	@relequestual
Greg Dennis	@gregsdennis
Henry Andrews	@handrews
Jason Desrosiers	@jdesrosiers

Details

Prioritization and Organizational Practices

Labels were suggested, so that they can be used to generate a list based on WG meetings. The issues, PRs etc.
discussed can then be triaged based on the discussion. At present, use of labels have the following issues

• Have not been rolled out to all repositories
• There is no standard triage process in place
• Labels and notification not conceptually mapped, making it difficult to set priority and to follow activity at a glance
• Use of label, sorting by label and tagging by contributers not the most efficient or relevant and at times ignored

Nominating and Pinning a few things based on a consensus on their priority. The issues raised with the technique was that
members involved may have conflicting priorities and a consensus might be difficult to reach.

To triage an hour each day can be handled by someone dedicatedly. Those can be used to assess critical, high priority things which
can help set agenda for WG meetings. Along with issues, PRs and discussions carrying a dedicated label to be decided which can be used to
add those items to meeting agenda otherwise to be left out of meetings.

A dedicated slack channel which has some automation to deal with prioritaztion was also discussed. Although administering it would be a task in itself,
hence the idea was dropped.

Method of consensus and priority was agreed upon, which can be a markdown file in the community repo whose notifications can then be posted to slack channel.
The issue raised in this regard was that people spend more time in test suite and spec repo than the community repo, to which the solution suggested was
notifying priorities to a slack channel.

Specification Document Governance Model

Specification document snapshot with every release, like the ECMAScript.³ Although there is backward compatibility in living specs
and future feature can be tagged to be ignored the advantage of snapshots is that they set a bound to material
that one has to deal with for a software that was written based on a specific spec.

The disadvantage of snapshots and an advantage for the spec as a living document pointed out was that clarifications, bug fixes etc.
may quickly desynchronize understanding thereby people running into issues which were easily avoidable.

A solution suggested was to add an errata to snapshots which would require least effort and modifying the spec text will not be necessary.

Also, a spec standard is suggested to use normative language so as to not confuse between types of requirements.¹²

(FYI: The above minutes and actions are the first test of our new minutes and actions contract work!)

Recording: link

Footnotes

1. https://datatracker.ietf.org/doc/rfc2119/ ↩ ↩²

2. https://datatracker.ietf.org/doc/rfc8174/ ↩ ↩²

3. https://arai-a.github.io/ecma262-compare/ ↩

[handrews]

Agenda item:

• Discuss the dependency order of major topics that need resolution. We are stuck in some deadlocks right now due to differing views on this.

[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 ❤️

[github-actions]

This issue did not get any activity in the past 180 days and thus has been closed. Please check if the main branch has fixed it. Please, create a new issue if the issue is not fixed.