Open Community Working Meeting 2023-03-06 - 14:00 PT

[benjagm]

Open Community Working Meeting 2023-03-06 - 14:00 PT

📺 See Recording

⏪ Go To Previous Meeting

Agenda:

Topic	Owner	Decision/NextStep
Review last call's action items	[facilitator]
GSoC 2023 projects as part of Postman Organization	@benjagm	Update contributors with the process and timelines in Slack and Github and schedule a quick off session
Update on the charter discussion #286	@benjagm	More feedback is required for section 1.1 Scope, 4 Roles and 4.2 Decision Making in PR #325. We agreed in the benefits of not extending the roles beyond the TSC at this point because that information can be included in the future when we are more clear about how the best way to engage with the implementers' ecosystem.
Update on not supporting unknown keywords discussion and alternatives #329	@gregsdennis	To launch a survey to ask the community what symbol is better to use as prefix and to create an issue with a formal proposal

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.

Action items:

• @benjagm will check with the Postman team if having multiple contributors per project will be possible.
• @Relequestual will continue working on The JSON Schema Charter #325 and more feedback will be required.
• @gregsdennis will start drafting a formal proposal for replacing unknown keywords. Related PR
• @benjagm will run a survey within the community to ask what is the preferred symbol to use as a prefix.

Notes:

• We reviewed the process and next steps for GSoC Contributors' applications. The channel for program coordination within JSON Schema is #gsoc-2023-core, whereas the channel for Q&A and broader discussions will be #gsoc-2023.
• @Relequestual provided a great update about the charter discussion Let's write a Charter! #286 . The open items still seeking for feedback are 1.1 Scope, 4 Roles and 4.2 Decision Making. Regarding Roles, we agreed on keeping the scope at TSC level and describing other future roles in a future governance.md document.
• @gregsdennis provided a great update about the feedback received on Github and Hacker News regarding alternatives for removing unknown keywords and seems that using a prefix is the preferred choice. During the meeting we discussed the benefits of using a special character and now we have to prepare a formal proposal with HASH symbol.

Agenda Items rolling over:

• list

Attendees

Account
@jdesrosiers
@gregsdennis
@jviotti
@Relequestual
@benjagm
Jeremy Fiel
Agnivesh Chaubey

[benjagm]

Closing this issue as all tasks are completed. Thanks for your contributions!

[benjagm]

The survey was created in Reform in this link: https://forms.reform.app/BFFNaO/jsonschema-feedback/keFJCY

The survey has been promoted in Slack and social media, however I didn't promoted it properly in a separated issue.