+1 from me as well. I think the social aspect is critical (community over code) will be beneficial. and keeping the dev list the source of truth should be a net win. We might want to explore alternating the time so more folks can participate, but that’s something we can explore as it develops.
Twitter: https://twitter.com/holdenkarau Fight Health Insurance: https://www.fighthealthinsurance.com/ <https://www.fighthealthinsurance.com/?q=hk_email> Books (Learning Spark, High Performance Spark, etc.): https://amzn.to/2MaRAG9 <https://amzn.to/2MaRAG9> YouTube Live Streams: https://www.youtube.com/user/holdenkarau Pronouns: she/her On Sat, May 16, 2026 at 8:19 AM Ángel Álvarez Pascua < [email protected]> wrote: > Hi everyone, > > +1 from me. I think a monthly sync could be useful, especially for larger > design discussions and open proposals. > > Having a shared agenda ahead of time would be important so people can add > topics and follow along even if they cannot attend. A short summary back to > the dev list after each sync would also help keep everyone aligned. > > Regards, > Ángel > > El sáb, 16 may 2026, 1:09, huaxin gao <[email protected]> escribió: > >> Thanks Mark, agreed. We should make sure any concrete action items are >> brought back to the dev list for discussion before anything is acted on. >> >> On Fri, May 15, 2026 at 3:48 PM Mark Hamstra <[email protected]> >> wrote: >> >>> Yes, that's more on the right track. If summaries are making it back >>> to the mailing list and any actions are only taken after the relevant >>> issues have also been opened to mailing list discussion, then the >>> off-list discussions may be acceptable. >>> >>> On Fri, May 15, 2026 at 3:30 PM huaxin gao <[email protected]> >>> wrote: >>> > >>> > 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] >>> >> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe e-mail: [email protected] >>> >>>
