You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mxnet.apache.org by Sheng Zha <no...@github.com> on 2019/08/04 22:16:42 UTC

[apache/incubator-mxnet] [RFC] RFC Issue Mirroring to dev@mxnet.apache.org (#15749)

# 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](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 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 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

Re: [apache/incubator-mxnet] [RFC][WIP] RFC Issue Mirroring to dev@mxnet.apache.org (#15749)

Posted by Rakesh Vasudevan <no...@github.com>.
@mxnet-label-bot add [RFC]

-- 
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/15749#issuecomment-518148397

Re: [apache/incubator-mxnet] [RFC][WIP] RFC Issue Mirroring to dev@mxnet.apache.org (#15749)

Posted by Lai Wei <no...@github.com>.
+1 cycled reference between github disucssion and dev list dicussion is confusing.

-- 
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/15749#issuecomment-518441849

Re: [apache/incubator-mxnet] [RFC][WIP] RFC Issue Mirroring to dev@mxnet.apache.org (#15749)

Posted by Junru Shao <no...@github.com>.
+1 for the proposal!

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

-- 
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/15749#issuecomment-518323470

Re: [apache/incubator-mxnet] [RFC] RFC Issue Mirroring to dev@mxnet.apache.org (#15749)

Posted by Sheng Zha <no...@github.com>.
RFC issue mirroring has been up and running. The mirroring on the email side requires replying all to the thread on dev@.

-- 
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#issuecomment-557633070

Re: [apache/incubator-mxnet] [RFC][WIP] RFC Issue Mirroring to dev@mxnet.apache.org (#15749)

Posted by Sheng Zha <zh...@apache.org>.
Thanks for the suggestions. For now I've put in an exclusion rule for mxnet-label-bot but I'm not sure whether it's effective yet. I will try it out.

-sz

On 2019/08/05 18:15:37, Marco de Abreu <no...@github.com> wrote: 
> Yeah anything involving the label bot should be blocked if possible
> 
> -- 
> You are receiving this because you authored the thread.
> Reply to this email directly or view it on GitHub:
> https://github.com/apache/incubator-mxnet/issues/15749#issuecomment-518341748

Re: [apache/incubator-mxnet] [RFC][WIP] RFC Issue Mirroring to dev@mxnet.apache.org (#15749)

Posted by Marco de Abreu <no...@github.com>.
Yeah anything involving the label bot should be blocked if possible

-- 
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/15749#issuecomment-518341748

Re: [apache/incubator-mxnet] [RFC][WIP] RFC Issue Mirroring to dev@mxnet.apache.org (#15749)

Posted by Ade <no...@github.com>.
thats a good option 

-- 
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/15749#issuecomment-518178698

Re: [apache/incubator-mxnet] [RFC] RFC Issue Mirroring to dev@mxnet.apache.org (#15749)

Posted by Sheng Zha <no...@github.com>.
Closed #15749.

-- 
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#event-2824101270

Re: [apache/incubator-mxnet] [RFC] RFC Issue Mirroring to dev@mxnet.apache.org (#15749)

Posted by mxnet-label-bot <no...@github.com>.
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

-- 
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/15749#issuecomment-518040671