Open Community Working Meeting 2024-01-08 - 14:00 PT

[benjagm]

Open Community Working Meeting 2024-01-08 - 14:00 PT

📺 See Recording

⏪ Go To Previous Meeting

Agenda:

Topic	Owner	Decision/NextStep
Review last call's action items	[facilitator]
Should we host 2 different working sessions to work separately about Spec and Community? e.g. AsyncAPI is using this approach.	@benjagm	Ask for feedback about adding more Community content to the Office Hours session and survey meeting new joiners and the whole community about what worked and how to improve the experience for Open Community and Office Hours meetings.
#521 - Let's define together what we understand by "critical" JSON Schema projects.	@benjagm	Start a discussion about top priorities and pain points for new Community projects that address real community requirements.

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: (processing)

• @benjagm to survey meeting new joiners and the whole community about what worked and how to improve the experience for Open Community and Office Hours meetings.
• @benjagm to start a discussion to asking for feedback about adding more Community content to the Office Hours session.
• @benjagm to start a discussion to quick start the conversation about top priorities and pain points to have a place for inspiration for the community to create projects that solve those issues.

Notes:

• The session started with @benjagm sharing his thoughts about the need of a Community meeting with focus on Community, but the team suggested to think about using the monthly Office Hours meeting with more Community topics.

• The team discussed how to make meetings more engaging for new participants, such as clarifying goals because we noticed that new joiners to Open Community Working Meetings rarely jain another session and the decision was to survey new joiners and the community about what worked and how to improve the experience for both meetings. @benjagm will start a discussion to asking for feedback about adding more Community content to the Office Hours session.

• The meeting continued with a discussion on Let's define together what we understand by "critical" JSON Schema projects #521 . @benjagm raised the need of transparency around support for projects like Bowtie and Learn JSON Schema and @jviotti suggested a shift to focus on community needs and encourage discussion to identify top priorities and pain points to guide new projects that address real community requirements and define a program with incentives to support Contributors building solutions for those pain points. @benjagm will start a discussion to quick start the conversation about top priorities and pain points to have a place for inspiration for the community to create projects that solve those issues.

Attendees

Account
@Relequestual
John McBride
@benjagm
@Julian
@jviotti

[benjagm]

The discussion about the scope of the Office Hours session has been created: #575

[benjagm]

Hi Team, this is the discussion to identify critical projects within the JSON Schema Ecosystem: #578

[benjagm]

Closed as completed.