Hi everyone, OK, let's keep the Community Meetings on a bi-weekly schedule.
However, I would like to emphasize a few points: - Release Synchronization: Release management, preparation, and content should be initiated and handled primarily on the mailing list. While we can discuss updates during Community Meetings, the mailing list remains the official platform for these processes. - Primary Channel: The mailing list is our primary channel for communication, especially for welcoming and engaging newcomers. - Accessibility and Inclusion: Not everyone can or wants to attend synchronous meetings. The mailing list is the most inclusive way to engage the entire community due to its asynchronous nature, searchable archives, and consideration for different time zones. The goal of this discussion is to remind everyone that the mailing list is always the preferred channel for official community business. Regards, JB On Wed, Feb 4, 2026 at 11:24 PM Yufei Gu <[email protected]> wrote: > While I prefer fewer meetings, a monthly cadence feels too infrequent for > our needs. For example, it would make it difficult to coordinate our > monthly release cycle effectively. More frequent syncs also create natural > touchpoints for welcoming new contributors into the community. I'd suggest > moving to a biweekly cadence. I'm also open to meeting every three weeks if > others prefer a middle ground. > > Yufei > > > On Wed, Feb 4, 2026 at 1:02 PM Adnan Hemani via dev < > [email protected]> > wrote: > > > Hi JB, > > > > I'm okay with this either way - but I've added it to tomorrow's agenda > as a > > discussion item! > > > > Best, > > Adnan Hemani > > > > On Wed, Feb 4, 2026 at 6:37 AM Jean-Baptiste Onofré <[email protected]> > > wrote: > > > > > Hi everyone, > > > > > > Currently, our community meetings are held every two weeks. To better > > serve > > > the community, I propose rescheduling these meetings to a monthly > cadence > > > with a focus on the following: > > > > > > - Highlights and Updates: Keeping the community informed of major > changes > > > and new features. > > > - Important Proposals and Discussions: Providing brief abstracts or > > > introductions to topics, followed by a call for review on the dev > mailing > > > list (or in dedicated meetings, if necessary). > > > > > > Please note that no decisions are made during these meetings; all > > official > > > decisions must take place on the dev mailing list. > > > > > > The community meetings should serve as a "hook" to highlight active PRs > > and > > > mailing list discussions. > > > > > > Thoughts? > > > > > > Regards, > > > JB > > > > > >
