Hi Generally speaking, that's the purpose of Community Meeting: discuss about what's going on and new proposals, populating the roadmap. The GitHub Discussion is one vision/proposal from some of us and anyone can add new features to it. In Apache projects, it's also just proposals, because any contributor can propose new stuff (not really anticipated).
That said, I think having one Community Meeting dedicated to "roadmap discussion" is a good idea. We just need to clearly state a Community Meeting will focus on roadmap discussion in the agenda. I would suggest updating https://polaris.apache.org/community/meetings/ to "tag" meetings dedicated to Roadmap Discussion. Regards JB On Mon, Jul 14, 2025 at 5:49 PM Adam Christian <adam.christ...@dremio.com.invalid> wrote: > > Howdy Polaris Community, > > Now that 1.0 has shipped, I think it might be nice to have a dedicated > community meeting where we discuss what large Polaris enhancements we want > to work on in the next few months. > > From what I've learned from folks, back in February, the community came > together and had a rough idea of what would be on the "Polaris backlog" for > the next few releases: https://github.com/apache/polaris/discussions/1028 > > I know that Yufei has done a good job at updating this as we have shipped > large enhancements, but I believe it would be nice to have the whole > community at the table, so we can iterate together. Just to be clear, I'm > not saying that anything generated from these talks would be considered a > "fixed" commitment and I don't want to tie specific enhancements to > specific releases, but I do think it would be helpful to speak about where > this project is going. > > What do y'all think? > > Go team, > > Adam Christian
