A monthly meeting sounds like a good idea. It will allow project members to get to know each other, and should help build momentum.
Monthly meetings of this kind are fairly common in Apache projects. However, the projects need to be careful that the meeting doesn't exclude people from the decision-making process, such as people who are in a different time zone, or who have other responsibilities at the time of the meeting. A few suggestions for mitigating this: * Have discussions during the meeting, but if there are significant decisions to be made, make them on the dev list. * Send out minutes after each meeting. * Poll the community for preferred times and if there is no single time that works for everyone consider varying the time of the meeting. For example, if you read through the minutes of the Arrow sync call [1] there are several good habits in evidence: they speak of 'coming to a consensus' but decisions are 'pending a vote'; there is a proposal, but one of the action items is for someone to start a discussion of that proposal on the mailing list. Julian [1] https://lists.apache.org/thread/cmt59phs7tzd5dcdqnr7qn66womd1odx On Wed, Nov 30, 2022 at 4:34 PM Nga Chung <nch...@apache.org> wrote: > > Hi all, > > I'm not sure if there is any official guidance on hosting public monthly > project meetings. This could be a good venue for PMC > members/committers/users/etc. to discuss project roadmap, releases, usage, > etc. Thoughts? > > Thanks, > Nga
