-
BackgroundAs far as I remember, we used to have two working group sessions - one on Wednesdays and one on Thursdays. Around March 2021, we decided to change the format of the working group meetings on Thursdays and we renamed them to “office hours”. According to the office hours document:
A few weeks ago, in the middle of June 2021, we decided to move the working group meetings to be on Thursdays morning EST. In the past few weeks, I've noticed that the office hours were mostly used to continue reviewing RFCs (as we’re doing during most of each the working group meeting). QuestionWhat is the current difference between the working group and the office hour meetings? ThoughtsPersonally (and also from what I heard from other community members), I don’t think that we should have two meetings to discuss RFCs since most of the discussions should happen on Github. The working group meetings should be used to discuss topics that are harder or takes much longer to have on Github. We expect that after the meeting, the main part of the discussion will be written to the RFC, so people that weren’t able to join the meeting, will be able to review it and be part of it. I think it would be great if we could use the office hours as a safe forum for people to ask questions, share their thoughts, show some code, etc., as we planned to do when we created it. If we decide to change the format back to two working group meetings every week, it might influence this PR that is discussing the agenda of the working group meetings. Would love to get your thoughts. |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments
-
I agree very much with this sentiment! |
Beta Was this translation helpful? Give feedback.
-
I fully agree :-) |
Beta Was this translation helpful? Give feedback.
-
I agree with @yaelharel, because both meetings are in the same day I think we can make them different so people can see the value of joining one or the other and also for keeping the interest of the community and provide the slot of time for people to join and share. |
Beta Was this translation helpful? Give feedback.
-
I think it's okay if office hours become "whatever the participants for that day want it to be". But I think we should be mindful that whenever there's synchronous discussion happening, people who might still be interested in the topic are inevitably not going to be able to participate. We should aim to capture the salient points from what was discussed in the RFC (preferable I think to notes in the meeting Google doc). |
Beta Was this translation helpful? Give feedback.
-
To play devil's advocate, the doc also says:
I don't think discussing RFCs is an anti-goal of the Office Hours. What we can try to do is prioritize RFC discussions to the bottom of the agenda and leave new members/conversations be first. That said, it does require new members / conversations to be added to the agenda. EDIT: Note that I'm only talking about topics that go on the agenda and not how conversations about RFCs are "archived". That problem seems seperate to me given that it also applies to WG. |
Beta Was this translation helpful? Give feedback.
-
Thanks to the changes that happened following #106 and the new core team sync (https://buildpacks.io/community/), I think that the last office hour meetings agenda changed in a good way and their agenda is different than the working group meeting. |
Beta Was this translation helpful? Give feedback.
Thanks to the changes that happened following #106 and the new core team sync (https://buildpacks.io/community/), I think that the last office hour meetings agenda changed in a good way and their agenda is different than the working group meeting.
I'm going to close this discussion for now.
Thank you for your feedback!