# Problem Statement Before setting up the mirroring, activity on d...@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](https://lists.apache.org/thread.html/5375f46e9e358603fdabb46d97c838420d827e79e189f3ffbbdc1b57@%3Cdev.mxnet.apache.org%3E)) 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 (and demo) for bidirectional mirroring of GitHub issues with `[RFC]` in the subject on the d...@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 notificati...@github.com). GitHub notification emails that are automatically forwarded will have notificati...@github.com as the sender, and thus replying to the email on dev@ 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. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-mxnet/issues/15749
