Revisiting the scope of the JSON Schema Office Hours #575
Replies: 3 comments 1 reply
-
I think the current format of Office Hours is great for Q&A and I suggest having a different monthly session just for community topics/updates. |
Beta Was this translation helpful? Give feedback.
-
As discussed in the last OCWM #688, we'll start a monthly Community session the third week of the month using a timezone friendly with US/LATAM/APAC. |
Beta Was this translation helpful? Give feedback.
-
We discussed again about this in the OCWM of past 2024-04-15 #695 we the team suggested to keep the Office Hours scope consistent in both timezones so my next proposal is:
This will require volunteers to act as facilitators for different timezones. |
Beta Was this translation helpful? Give feedback.
-
ℹ️ Context:
In the last Open Community Working Meeting I suggested an idea of having 2 different Open Community Meetings:
And my argument is I strongly feel that we need more spaces 100% Community driven where implementers, adopters and Schema designers can share their knowledge and engage in insightful discussions. As part of the discussion @jviotti and others reminded my about the Office Hours session which actually doesn't have agenda and the goal is Q&A and open discussions and seems to be the right place to add more Community drive content.
In addition I shared this survey with the Community to capture insights about what is the Community perception about the scope and engagement of the Open Community Working Meetings and the Office Hours Sessions so we can know better what is working and what is not working. (The survey is still open)
💬 Discussion:
The goal is to discuss how do we feel about adding a bit more of structure and community content to the monthly office hours sessions. I personally would like to:
🚀 Let's discuss:
We'd love to get your thoughts and feedback:
Thanks everyone!
Beta Was this translation helpful? Give feedback.
All reactions