+1 - thanks. Emails will go to dev@pulsar initially. We should have a separate discussion about notifications since these are set on a repository by repository basis.
> On Jul 12, 2022, at 4:04 AM, Yu <li...@apache.org> wrote: > > Hi tison, thanks for creating this vote! > I thought we reached a lay consensus since there was no objection since the > last discussion [1] > > +1 for this proposal. > I've explained the reasons and showed the benefits previously [2] > > [1] https://lists.apache.org/thread/1y7zbchlbokwnpd0jv2tt5jtzg6px6yn > [2] https://lists.apache.org/thread/83pst643h9cqcryo3zsjd240jmqzvn73 > > On Tue, Jul 12, 2022 at 6:01 PM tison <wander4...@gmail.com> wrote: > >> Hi, >> >> In the previous email[1] I started a discussion about enabling GitHub >> Discussions in apache/pulsar repository and we meet a consensus to avoid >> making development discussions truth happen on the sources. It's also a >> requirement of INFRA team[2] >> >> Apart of it, for user-facing discussions it's conventions for Pulsar users >> who have a GitHub account but are unfamiliar with mailing list to throw >> their use case and questions on GitHub discussion. >> >> Dave has opened and issue[2][3] and prepare the patch[4] for turning on the >> discussion option but obviously we still need an explicit consensus among >> the community and it's also required before INFRA team takes action. >> >> I'd like to start this voting thread for "Enable GitHub Discussion for >> user-facing discussion", please reply with your opinion: >> >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >> >> Best, >> tison. >> >> [1] https://lists.apache.org/thread/1y7zbchlbokwnpd0jv2tt5jtzg6px6yn >> [2] https://issues.apache.org/jira/browse/INFRA-23477 >> [3] https://github.com/apache/pulsar/issues/16275 >> [4] https://github.com/apache/pulsar/pull/16528 >>
