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

[benjagm]

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

📺 See Recording

⏪ Go To Previous Meeting

Agenda:

Topic	Owner	Decision/NextStep
Review last call's action items	[facilitator]
#691 - Proposal to formalize the processes for Working Groups	@benjagm
#678 - Ambassadors Program - Requisites and budget	@benjagm
#690 - JSON Schema Conf 2024	@benjagm
#575 - Revisiting the scope of the JSON Schema Office Hours	@benjagm

Action items:

• Trial the the working groups approach to organize the JSON Schema conference.
• Start the voting process to approve the Swag budget for Ambassadors Program - Requisites and budget #678 .
• Start a monthly Community session the third week of the month using a timezone friendly with US/LATAM/APAC.

Notes:

• Proposal to formalize the processes for Working Groups #691
  While a process could help transparency, the group felt formalizing working groups was premature given limited prior success attracting external help. It was agreed to trial the approach with a working group to organize the JSON Schema conference.

• Ambassadors Program - Requisites and budget #678
  A proposal for a swag-supported ambassador and contributor recognition program was well-received pending TC approval. Increased transparency on finances and goals was seen as important to attract more sponsors.

• JSON Schema Conf 2024 #690
  The group learned their track was accepted for API Days Paris in December, requiring paper submissions and organization. They discussed the conference name and scheduling their day with OpenAPI and AsyncAPI.

• Revisiting the scope of the JSON Schema Office Hours #575
  Adding a monthly community session in the third week was proposed to share updates and showcase implementations. Rotating times and more moderators were suggested to improve attendance and inclusion from different regions.

Agenda Items rolling over:

Attendees:

Account
@gregsdennis
@jdesrosiers
@benjagm
@jviotti
@jeremyfiel
Suprith Era

[benjagm]

As discussed I just created the voting issue in the TSC repo to approve/reject the swag/online shop budget proposal.

[RacerGirl6]

hello, id like permission to join the phone call as i'm involved in these records, i'm the subject of one that's compromised my apple icloud and gmail account, with all my confidential data going missing. please let me know if you can accept and please contact cve records admin on mitre.org to confirm my input into this please, thank you

[benjagm]

hello, id like permission to join the phone call as i'm involved in these records, i'm the subject of one that's compromised my apple icloud and gmail account

The calls are all open and everyone is free to join. Regarding the compromised apple account it is unrelated to this so please don't add more comments like this. If you have any doubt, feel free to contact us in the email info@json-schema.org

[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]

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.