If we can bring GitHub Discussions threads to dev@ or users@ (by categorized), it won't affect workflow based on mailing list.
Basically, you can discuss via GitHub Discussion by emails. Best, tison. Dianjin Wang <djw...@streamnative.io.invalid> 于2022年4月21日周四 21:43写道： > Agreed with @Enrico. If enabling the GitHub discussions, it's confusing for > community members to recognize issues or discussions. If too many > platforms, it's also hard for people to be focused. > > Best, > Dianjin Wang > > > On Thu, Apr 21, 2022 at 8:49 PM Enrico Olivelli <eolive...@gmail.com> > wrote: > > > I believe that we should stick as much as possible to the mailing > > list, this is the common way of running the community in the ASF. > > > > We already have a Slack space that is hard to follow. > > > > Enrico > > > > Il giorno gio 21 apr 2022 alle ore 14:47 tison <wander4...@gmail.com> > > ha scritto: > > > > > > You can ask for ASF INFRA to see whether there is a way to bring all > > activities of GitHub Discussion to a mailing list. Just like development > > activities to commits@. > > > > > > Best, > > > tison. > > > > > > > > > Niclas Hedhman <nic...@hedhman.org> 于2022年4月21日周四 20:16写道： > > >> > > >> > > >> If/when GitHub disappears, will the community suffer from missing > > >> information? If so, need to solve the "back to ASF"-path, so it isn't > > >> lost. > > >> > > >> Niclas > > >> > > >> On 2022-04-21 11:00, Yu wrote: > > >> > Hi Pulsarers, > > >> > > > >> > Recently, we've found that many open source communities use GitHub > > >> > Discussions to facilitate effective communication, such as users can > > >> > ask questions, share ideas, and build connections with each other > > >> > easily [1]. > > >> > > > >> > GitHub Discussions is designed to: > > >> > > > >> > - Provide centralized community space for conversations and > questions > > >> > (and make the lives of maintainers easier when it comes to issues > and > > >> > pull requests). > > >> > > > >> > - Create a place for newcomers and non-code collaborators to > > >> > participate in a larger community. > > >> > > > >> > - Highlight project contributors to help develop the next generation > > >> > of maintainers. > > >> > > > >> > And it is different from GitHub Issue by providing more functions > for > > >> > conversations, questions, and community engagement. You can check > all > > >> > details here [2]. > > >> > > > >> > ~~~~~~~~~~~~~~~~ > > >> > > > >> > Do we want to enable the GitHub Discussions in Pulsar? > > >> > > > >> > Feel free to comment, thank you! > > >> > > > >> > [1] > > >> > > > > https://github.blog/2022-01-13-how-five-open-source-communities-are-using-github-discussions/ > > >> > [2] > https://resources.github.com/devops/process/planning/discussions/ > > >> > > > >> > Anonymitaet > > >
