Hi JB, Thanks for bringing this up. It’s a good problem to have as the community grows :-)!
My only concern is that the set of people who can answer most questions are mainly on the dev list today. Splitting into two lists might risk some fragmentation, duplicated answers, and less participation overall. Right now Slack already works well for quick user questions, and we also have GitHub Discussions as another channel. Maybe once the community grows larger, it would make sense to revisit the idea of a dedicated user list. Just my two cents. Yufei On Fri, Sep 26, 2025 at 12:15 PM Dmitri Bourlatchkov <[email protected]> wrote: > Hi JB, > > Adding a users mailing list would be good from my POV. I imagine we could > leave slack for more informal user-to-user discussions, while treating the > users ML as a means for requesting information from Polaris developers / > maintainers. > > I imagine if something new or unusual but affecting many users were to come > up in slack, it would not be unreasonable to move such a conversation to > the users ML so that responses and advice would be archived for future > reference. > > That said, I see some overlap with GH discussions, so I wonder if we may > want to make GH discussion read-only if we enable the new ML (in order to > direct all questions to one system). > > My personal preference is with users ML over GH discussions. > > Cheers, > Dmitri. > > On Fri, Sep 26, 2025 at 2:55 PM Jean-Baptiste Onofré <[email protected]> > wrote: > > > Hi everyone, > > > > It’s great to see more and more users asking questions on Slack. > > To give a voice to anyone and a way to ask questions, I wonder if we > should > > not create a user mailing list. > > Dev will be used to discuss technical details, changes, proposals, > > decisions (as we do today). User will be dedicated to users about > > questions, help requests, etc. > > > > Thoughts ? > > > > Regards > > JB > > >
