Thanks Mark, that makes sense. I agree that the mailing list should remain the source of truth for community discussions and decisions. My intention was not to move decision-making out of the mailing list, but to provide an optional forum for real-time discussion, clarification, and brainstorming around open proposals or issues.
Any concrete decisions, conclusions, or follow-up actions from the sync should be summarized back to the dev mailing list, and formal decisions would still happen on the mailing list as usual. I should have made that clearer in the original proposal. Thanks, Huaxin On Fri, May 15, 2026 at 3:20 PM Mark Hamstra <[email protected]> wrote: > That's not really a good fit with the Apache notion that "if it didn't > happen on the mailing list, then it didn't happen". > > On Fri, May 15, 2026 at 3:03 PM huaxin gao <[email protected]> wrote: > > > > Hi everyone, > > > > I’d like to propose starting a monthly Spark community sync to discuss > open issues, ongoing proposals, and design topics that would benefit from > real-time discussion. > > > > The idea is similar to the current Iceberg community sync: a one-hour > recurring meeting with a shared agenda doc where people can add topics > ahead of time. This could help us make progress on larger design > discussions, clarify open questions earlier, and make it easier for > contributors and reviewers to align across different areas of Spark. > > > > The sync would be open to the community, and the agenda doc could be > used to track topics, notes, and follow-ups. Topics could include SPIPs, > larger PRs, release-related discussions, cross-project integration work, or > any other issues where live discussion would be useful. > > > > Would others be interested in this? If there is enough interest, I’m > happy to help set up the agenda doc and propose an initial monthly time > slot. > > > > Thanks, > > Huaxin > > --------------------------------------------------------------------- > To unsubscribe e-mail: [email protected] > >
