[RFC] RFC Issue Mirroring to dev@mxnet.apache.org

[szha]

Problem Statement

Before setting up the mirroring, activity on dev@mxnet.apache.org and on GitHub are disconnected. Community members need to manually bring discussion on GitHub to the dev@ list by sending a notification with a link, and vise versa. This problem has been discussed (and voted on) and solutions have been proposed in the past, but was shelved due to concerns on large amount of traffic. Still, fixing the communication gap is greatly beneficial for a healthy community.

Proposal

This is an RFC for bidirectional mirroring of GitHub issues with [RFC] in the subject on the dev@mxnet.apache.org. By mirroring the RFCs in GitHub issues on dev@ automatically, community members can join the discussion on new proposals either on GitHub, or on dev@ list, within the same conversation. Also, this decreases the burden on people who are writing new proposals as it would no longer be necessary to duplicate the notification to both channels.

Approach

The mirroring is achieved through setting up an email filter for the desired subset of emails and automatically forward them to the dev@ list.

GitHub notifications already allow joining GitHub conversations through replying to the notification email (with reply-to address notifications@github.com). GitHub notification emails that are automatically forwarded will have notifications@github.com as the sender, and thus replying all to that email will reply on both dev@ and notifications@github.com, and the later will send the message back to the GitHub. For message on GitHub, the automatic forwarding will send the message to the same email thread. As a result, messages from both channels will show as a single cohesive conversation.

Comments and suggestions are welcome.

[mxnet-label-bot]

Hey, this is the MXNet Label Bot.
Thank you for submitting the issue! I will try and suggest some labels so that the appropriate MXNet community members can help resolve it.
Here are my recommended labels: Doc

[vrakesh]

@mxnet-label-bot add [RFC]

[junrushao]

+1 for the proposal!

BTW shall we have an option to block messages sent by the label bot to avoid too much traffic?

[marcoabreu]

Yeah anything involving the label bot should be blocked if possible

[roywei]

+1 cycled reference between github disucssion and dev list dicussion is confusing.

[szha]

RFC issue mirroring has been up and running. The mirroring on the email side requires replying all to the thread on dev@.