Re: [DISCUSS] Enable GitHub Discussions?

Hi - If we add GitHub Discussions then I think that dev@ should be informed when a Discussion is started and closed while commits@ should get the comments. If we decide to add an issues@ mailing list then we need two volunteers for mailing list moderation.

Re: [DISCUSS] Enable GitHub Discussions?

Hi - Now that the ASF has a notifier on GitHub Discussions I have no objection to using discussions as long as these are visible on dev@pulsar.apache.org mailing list. > From the previous thread it seems that the Pulsar community has already > multiple channels

Re: [DISCUSS] Enable GitHub Discussions?

Hi Dave Fisher, any thoughts on enabling GitHub Discussions? Thank you. On 2022/06/27 02:41:12 Yu wrote: > +1 for enabling the GitHub Discussion as I proposed before. > > At that time, the main concern was not able to sync info between GitHub > Discussion and Mailing List. Since the concern can

Re: [DISCUSS] Enable GitHub Discussions?

+1 for enabling the GitHub Discussion as I proposed before. At that time, the main concern was not able to sync info between GitHub Discussion and Mailing List. Since the concern can be resolved now, we can make the most of GitHub Discussion as it's a powerful supplementary to community

Re: [DISCUSS] Enable GitHub Discussions?

Tison, Il Sab 25 Giu 2022, 21:32 tison ha scritto: > Hi, > > There is a previous discussion at > https://lists.apache.org/thread/83pst643h9cqcryo3zsjd240jmqzvn73. > > I'd like to bump this thread since INFRA has implemented forward GitHub > Discussions activities to mailing list[1][2][3]. > >

[DISCUSS] Enable GitHub Discussions?

Hi, There is a previous discussion at https://lists.apache.org/thread/83pst643h9cqcryo3zsjd240jmqzvn73. I'd like to bump this thread since INFRA has implemented forward GitHub Discussions activities to mailing list[1][2][3]. It may be a proper time we revisit this topic. My major argument is:

Re: Enable GitHub Discussions?

On 2022-04-25 12:34, Yu wrote: Another important part of The Apache Way is to make decisions by reaching consensus (and avoiding votes). But the Apache Website says "one of the fundamental aspects of accomplishing things within the Apache framework is doing so by consensus, we need a way to

Re: Enable GitHub Discussions?

Hi Dave, Thanks for your suggestions! 1. Using GitHub Discussions does not mean abandoning Google Docs, we can use both and leverage both advantages. 2. One question on this: > Another important part of The Apache Way is to make decisions by reaching consensus (and avoiding votes). But the

Re: Enable GitHub Discussions?

Hi Yu, > On Apr 21, 2022, at 11:46 PM, Yu wrote: > > 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

Re: Enable GitHub Discussions?

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

Re: Enable GitHub Discussions?

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

Re: Enable GitHub Discussions?

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 于2022年4月21日周四 21:43写道： > Agreed with @Enrico. If enabling the GitHub

Re: Enable GitHub Discussions?

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 wrote: > I believe that we

Re: Enable GitHub Discussions?

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 ha scritto: > > You can ask for ASF INFRA to see

Re: Enable GitHub Discussions?

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 于2022年4月21日周四 20:16写道： > > If/when GitHub disappears, will the community suffer from missing >

Enable GitHub Discussions?

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