JSON Schema
Should we have a regular call like OpenAPI TSC? #23
Replies: 4 comments 25 replies
-
|
This is much needed! Thanks Jason for starting the discussion. 30 minutes is tight, so we would need to be hyper focused, but I believe we can be! I'm happy with a weekly meeting. I'm going to suggest we record and publish these calls. I have created a Youtube channel. Assuming we alternate timezone preferences, my preference would be at least one of the meetings within working hours, and the other after 21:00, but not on Wednesdays. GMT. I have more to say but not the time today. Enough to get us going! =] |
Beta Was this translation helpful? Give feedback.
-
I don't mind you recording the meeting for personal archiving, but if you're going to publish them publicly then I won't be participating. |
Beta Was this translation helpful? Give feedback.
-
|
From my experience with AsyncAPI public meetings:
While I agree, I found out that people who are shy to speak because they're not good at English, usually don't even join the meetings that are not recorded.
What policies do you think people would be worried about? Regarding people ranting in comments, it's easy, disable them. However, I must say nobody ever ranted on our channel.
Well, that's a problem. This is an open-source project. Everything should be happening transparently and in public. If someone doesn't like their participation to be available to everyone they're simply in the wrong place.
What could an employer be concerned about exactly? I'm curious. |
Beta Was this translation helpful? Give feedback.
-
|
We want to be inclusive. We invite people to join and use chat only, while also being able to listen in on discussions, if they so wish. There's no reason anyone has to use either video or audio during the calls to participate. I hope deliberatly making space for people who make those choices for whatever reason is enough to eliviate some level of social phobia. We are however an open organisation as much as possible. Comments will be disabled. As meetings will have an issue, nessecary comments will go there. I don't see how 3 makes a difference if anyone can request to view and download the videos anyway? I don't know how to respond to no. 4. I want to be really clear. Attending these calls is not required to contribute nor to have significant impact on the project. They would be a means for maintainers to check in, review issues, feedback on PRs, and move things forward, at a faster rate than is otherwise possible. Not attending the calls for any reason does not exclude anyone from our community. Those from the community who choose for whatever reason to not join the calls are not going to be given any less consideration. Our Slack server is vibrant, and we have many people from the community ask for and receive help, and contribute to the specification and project. There are several individuals that do not attend the OpenAPI calls and yet have had significant impact on the project. We are not going to suddenly ignore Issues or Pull Requests. If anything, the calls will help us respond and resolve them faster than before. There is an optics aspect to this. I feel very strongly that JSON Schema as a project needs to be seen more if it's going to be effective. I outlined the reasoning in my recent talk on the state of JSON Schema. |
Beta Was this translation helpful? Give feedback.
-
|
While I appreciate your responses, I won't go into further details here. I actually did not expect any responses to any of my points mentioned above. My primary aim was to second Karens point and say that not everyone will be happy with YouTube publishing and thus some attendees such as Karen and me might get excluded. What I'm surprised about is why the alternatives Karen mentioned were not considered/discussed. Out of curiosity, could you link me to any other open-source project that publishes their calls on YouTube or a similar platform? I've never seen any OS project do that before. I never said or meant to say that those calls would take anything away from participation etc. Are you sure that hour-long calls on YouTube are a good way to make JSON Schema much more visible? I don't think so, but that's just my 2ct.
From personal experience in the past: Sometimes it's just about having a low barrier for people to join and then they feel comfortable and get more and more active. Having public YouTube recordings in place could be quite a barrier for some. |
Beta Was this translation helpful? Give feedback.
-
|
From the top of my head, you have: I know some other Linux Foundation and CNCF projects are doing it. In any case, I think it's cool to have them and proved useful for AsyncaPI too. It's not mandatory to join to become a contributor, so those who are not comfortable can simply not join and they're still welcome. The low barrier entry is the Github issues and discussions. |
Beta Was this translation helpful? Give feedback.
-
|
Interesting, I've only been involved in OS projects with written meeting notes or recoded calls that are only available to "members".
I fully disagree, but we won't reach a consensus here it seems (and we don't need to).
Sorry to be not 100% clear here, I meant low barrier for calls. Calls are much more personal and are a different level to become a member of a community than issues and discussions. |
Beta Was this translation helpful? Give feedback.
-
|
It looks like there's a time we might be able to squeeze everyone in at the same time. 08:00 NZST I imagine this is after @Relequestual's kids go to bed, but not too late while hopefully not too early for @gregsdennis and in the middle of the day for those of us in North America. If we have anyone who wants to join at some point from Eastern Europe, it will be pretty late, but hopefully not too unreasonable. It would be really late for someone from India to join, but we don't have anyone from that region right now. Let's start negotiations there. If we can make that time work, it would be best because everyone can be there. |
Beta Was this translation helpful? Give feedback.
-
|
Saturday is actually probably better as I won't be on a bus or walking to the office. I can't take time from work to do this. |
Beta Was this translation helpful? Give feedback.
-
|
Friday works for me. |
Beta Was this translation helpful? Give feedback.
-
|
Given @gregsdennis has recently declared a step back, I'm guessing regular meeting calls might be off the table for him. |
Beta Was this translation helpful? Give feedback.
-
|
4 EST working days would normally be a decent time for me too. |
Beta Was this translation helpful? Give feedback.
-
|
In case it helps, at AsyncAPI we're alternating the meetings between APAC and AMER-friendly times each week. This is working well because we never take decisions during the meeting but we rather use this time for the community to chime in. or explain things in a video format to support the written form. This way, we don't need everybody to be in the meeting at the same time. |
Beta Was this translation helpful? Give feedback.
-
|
OK, so I think what I want to propose is a twice monthly rotating timezone schedule. First Friday of the month (US/NZ friendly): Third Friday of the month (UK/EU friendly): Please thumbs up or thumbs down and/or leave a reply comment. |
Beta Was this translation helpful? Give feedback.
-
|
This was formalised in UTC https://twitter.com/jsonschema/status/1427214613439975424?s=20 Spiral calendar padClock face three oclock Twice monthly |
Beta Was this translation helpful? Give feedback.
-
I've been semi-regularly attending the OpenAPI TSC weekly calls recently and I think it's something that would be beneficial for us to do as well. I think there are several benefits.
It will help us be more organized. There are constantly things that slip through the cracks because we are all volunteers working asynchronously. If we have a time to regularly get together synchronously, we can more easily set goals, get updates on progress, identify things that still need to be done, and advocate for the issues important to us. For example, what's happening with the patch release we decided to do? Is anyone actively working on that? What still needs to be done?
It gives us a space to discuss contentious issues. Sometimes a conversation is the best way to come to an agreement or resolve a misunderstanding.
Many of us have been working together for years, but we've never met. It would be nice to get together every so often and talk about something we are all passionate about, JSON Schema. I think it can help us work together better as well. I think Henry and I would have had a better working relationship if we had ever met. I think we would have even been friends.
It could help build our community by giving people another avenue to contribute and advocate for their issues.
Assuming others think this is a good idea, we would need to decide the time, duration, and frequency for these calls. My preference would be for short (~30m) relatively frequent (weekly) calls. The time is the hard part because we have so many timezones involved. If we don't come up with a time that works for everyone, we can try two different times that we alternate between. That way everyone can at least make some of the calls. These calls would have no required participants and be open to anyone who has something to say or just wants to listen in.
Beta Was this translation helpful? Give feedback.
All reactions