mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sheng Zha <>
Subject [apache/incubator-mxnet] [RFC] RFC Issue Mirroring to (#15748)
Date Sun, 04 Aug 2019 22:15:29 GMT
# Problem Statement

Before setting up the mirroring, activity on 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 (and demo) for bidirectional mirroring of GitHub issues with `[RFC]` in the
subject on the 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 GitHub notification emails that are
automatically forwarded will have 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:
  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message