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 <mailto:dev@pulsar.apache.org> mailing list.
> From the previous thread it seems that the Pulsar community has already > multiple channels to catch up for contributors, while I only watch at > mailing list and GitHub issues & PRs I think that where the notifications are sent is important. Pulsar contributors are supposed to be watching dev@pulsar.apache.org <mailto:dev@pulsar.apache.org> and this should be the mailing list where discussions are visible to the community. I recommend that discussion notifications be sent there. > Besides, currently dev@ is full of Git notifications while we may sort them > out to issues@ as in Apache Kvrocks[5]. Regarding other notifications: the project is inconsistent. Also, please note that Pulsar does not have an issues@pulsar mailing list. The main repository is using this default: https://gitbox.apache.org/schemes.cgi?pulsar <https://gitbox.apache.org/schemes.cgi?pulsar> which differs from https://gitbox.apache.org/schemes.cgi?pulsar-site <https://gitbox.apache.org/schemes.cgi?pulsar-site> The overall notification scheme change is a new discussion which must be kept separate. Regards, Dave > On Jun 25, 2022, at 12:31 PM, tison <wander4...@gmail.com> wrote: > > 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: > >> GitHub Discussion is friendly for GitHub users and lower the bar to > participant in discussions. If we can sync all activities to mailing list, > it should be a nice supplement. > > You may take a look at Apache SkyWalking's practice[4] where it holds an > easy-to-find entrypoint for participants while keeps all decisions in > mailing list - VOTE and RESULT threads should happen on mailing list as it > used to be. > > At least, it can be a supplement of users@ with a Q&A category. > > From the previous thread it seems that the Pulsar community has already > multiple channels to catch up for contributors, while I only watch at > mailing list and GitHub issues & PRs. If you find other channel as source > of truth, I'm glad to learn and see whether we can keep as less source of > truth as possible - ideally, single source (orthogonal sources) of truth. > > Besides, currently dev@ is full of Git notifications while we may sort them > out to issues@ as in Apache Kvrocks[5]. > > Best, > tison. > > [1] https://github.com/apache/infrastructure-p6/pull/1120 > [2] https://github.com/apache/infrastructure-github-discussions-notifier/ > [3] > https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Notificationsettingsforrepositories > [4] https://github.com/apache/skywalking/discussions > [5] > https://github.com/apache/incubator-kvrocks/blob/dde438f04c577050e299cce981a17018f056c3b3/.asf.yaml#L46-L50
