Thanks all! I understand that we need to follow the Apache way (If it didn’t happen on the mailing list, it didn’t happen) to *make final decisions*, but we can find a better place to *discuss issues and reuse information effectively* [1].
~~~~~~~~ # Current issues We have a lot of work in various places, but the information is not organized and reused effectively. ## Slack - Information is not publicly accessible. You need to upgrade to paid plans or else you can see just the 10,000 most recent messages. - Information is scattered and not categorized. # StackOveflow - Inactive. Only 24 results after searching "apachepulsar". # Mailing List - Information is scattered and not categorized. - User experience is terrible. Plain text format decreases email readability. Search function is hard to use. ~~~~~~~~ # Why try GitHub Discussions? Compared with the platforms above and GitHub Issue, GitHub Discussions make collaboration more efficient by: # Making it easier to categorize, archive, and search information - It has categories (Announcements, General, Ideas, Polls, Q&A, Show and Tell, etc) and labels to categorize and filter information quickly. - Information is permanently saved. - Search is easy to use. # Providing a centralized community space for conversations and questions - As instructed by GitHub, we can use GitHub Discussions to *discuss things*, and use GitHub Issues to *catalog the work* we need to do after we’ve reached a decision about how to move forward. # Boosting community engagement and encouraging people to make contributions - It highlights project contributors and shows Most Helpful Ranking of Contributors. - It creates a place for newcomers and non-code collaborators to participate in a larger community. # Calling users' attention to important issues or events - Important discussions can be pinned to home pages for easy reference. ~~~~~~~~ Feel free to share your thoughts. This vote will be open for 72 hrs. Then we can ask Infra to do the needed GitHub Admin tasks if we reach a consensus on enabling it, thank you! [1] http://theapacheway.com/on-list/ Anonymitaet On Fri, Apr 22, 2022 at 2:34 AM Dave Fisher <w...@apache.org> wrote: > I asked Infra. GitHub Discussions are not synchronized into ASF > Infrastructure's GitBox. That means that there is not ability to change the > notification scheme to send to a mailing list. > > Technically we can go down this path only if it is possible to set a > notification within GitHub. You would need to look into that and if we > decided to go forward we can ask Infra to do the needed GitHub Admin tasks. > > Community wise I agree with others that we are already splitting a lot of > work into various places. > > Regards, > Dave > > On Apr 21, 2022, at 5:47 AM, tison <wander4...@gmail.com> wrote: > > 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 >> > >
