I don't think we can bridge the dev mail to the github issue, but it makes sense that to send the notification or the github issue to the dev mailing list. Now we need to figure out if we can seperate the github notification by checking if it comes from github issues.
Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Jan 14, 2019 at 10:00 PM Zheng Feng <zh.f...@gmail.com> wrote: > > I wonder if it can only watch the github issues by using the dev mailing > list or we can reply the thread and it could be posted to the github issue > automatically ? > > Zen Lin <zenlintechnofr...@gmail.com> 于2019年1月14日周一 下午8:38写道： > > > How about to create a new proposal discussion for split github issue track > > from commits mailing list to dev mailing list? > > I think discussion in github issue is quite different from commits, they > > are similar to the contents in the dev list. > > > > Best Regards, > > --- > > Zen Lin > > zenlintechnofr...@gmail.com > > Focused on Micro Service and Apache ServiceComb > > > > > > Willem Jiang <willem.ji...@gmail.com> 于2019年1月14日周一 下午8:20写道： > > > > > Actually we already had the vote[1] of moving the github notifications > > > into the commits mailing list to avoiding flooding the dev mailing > > > list . Here is the discussion of it[2]. Now the user questions in the > > > github issue are tracked in the commits mailing list. > > > > > > [1] > > > > > https://lists.apache.org/thread.html/833356d5dd8901f5d51e94b12d48f9dcb816d29f50b38d46915f8e9e@%3Cdev.servicecomb.apache.org%3E > > > [2] > > > > > https://lists.apache.org/thread.html/95f538f676326bd2cb1a06cf278c4076352b987bfbabad6c6ae247bc@%3Cdev.servicecomb.apache.org%3E > > > > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Mon, Jan 14, 2019 at 8:05 PM Willem Jiang <willem.ji...@gmail.com> > > > wrote: > > > > > > > > First we need to know the common process of building the consensus[1] > > in > > > Apache. > > > > Normally if we have some proposal, we discuss it first to build a > > > > common consensus, then we start the vote[2]. > > > > > > > > So let's discuss about this proposal first. > > > > > > > > [1]https://community.apache.org/committers/consensusBuilding.html > > > > [2]https://community.apache.org/committers/voting.html > > > > > > > > > > > > Willem Jiang > > > > > > > > Twitter: willemjiang > > > > Weibo: 姜宁willem > > > > > > > > On Mon, Jan 14, 2019 at 7:03 PM Zen Lin <zenlintechnofr...@gmail.com> > > > wrote: > > > > > > > > > > Hi Community, > > > > > > > > > > Although we have proposed to use JIRA as many times as possible, > > there > > > are > > > > > still many people using our Github issue. > > > > > Many users have been hoping to use the Github issue. > > > > > > > > > > So I propose to track the contents of the Github issue to our dev > > > mail so > > > > > that the community can better coordinate and discuss, so as not to > > > miss the > > > > > management of the Github issue. > > > > > This is a call for vote of tracking Github issue to > > > > > dev@servicecomb.apache.org mail list. > > > > > > > > > > Voting is starting now ( 14th Jan, 2018) and will remain open for > > next > > > 72 > > > > > hours. > > > > > > > > > > [ ] +1 Track Github issue discussions to mail list > > > > > dev@servicecomb.apache.org > > > > > [ ] +0 No Opinion > > > > > [ ] -1 Do not track Github issue discussions to the mail list > > > > > dev@servicecomb.apache.org > > > > > > > > > > > > > > > Best Regards, > > > > > --- > > > > > Zen Lin > > > > > zenlintechnofr...@gmail.com > > > > > Focused on Micro Service and Apache ServiceComb > > > > >
