You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The team reviewed the action items from the previous meeting and discussed topics such as the specification scope, the specification contribution guidelines, and the creating new channels for the technical steering committee.
The team continued the discussion of identifying the scope of the next Spec release. While @gregsdennis provided his comments in the issue #415, @jdesrosiers committed to add his comments in the upcoming days.
@Relequestual suggested updating the contributing document of the Specification repository and remove some of the outdated information issue #1414. @jdesrosiers mentioned that we need to clarify the spec development process yet. @benjagm committed to make the changes as part of Refine the contributor journey - issue Refine the contributor journey #410.
@benjagm asked for feedback on how to better proceed with archiving #collaborators channel when creating the new tsc channels ( See Add tsc-discussion Slack channel to list of channels #416 ). @Relequestual suggested linking to the relevant issue before archiving the channel and the team agreed on giving a week of warning before doing so.
I just opened a PR with a new version of the contributing guidelines of the Spec. I am marking as completed that action item. json-schema-org/json-schema-spec#1416
Open Community Working Meeting 2023-06-19 - 14:00 PT
📺 See Recording
⏪ Go To Previous Meeting
Agenda:
@jdesrosiers
@benjagm
Action items:
#collaborators
channel one week in advance to allow everyone to share concerns.Notes:
#collaborators
channel when creating the new tsc channels ( See Add tsc-discussion Slack channel to list of channels #416 ). @Relequestual suggested linking to the relevant issue before archiving the channel and the team agreed on giving a week of warning before doing so.Attendees
The text was updated successfully, but these errors were encountered: