+1 just one change: keep answer questions.
Willem Jiang <willem.ji...@gmail.com> 于2019年1月21日周一 下午4:05写道： > I'm agree with Liubao. > > The background of moving the github issue is to attract more users by > sporting the popular way of asking question in github issue. > If we treat github issue as the mailing list of > us...@servicecomb.apache.org, if we can keep answer the question and > the question are archived, I think it should be fine. We don't need to > do anything to routing the mail around. > > BTW, when I draft the board report, I include the github activities > with the mail activities. > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Mon, Jan 21, 2019 at 3:36 PM bismy <bi...@qq.com> wrote: > > > > For my personal preferences, we don't need to change anything, and now > everything works fine. > > > > > > 1. We discussion problem is dev mailing list. Users can send their > questions though mail. > > 2. Users submit issues or ask questions in issues @github, I subscribe > notifications from github and answers questions @github. > > > > > > We can encourage users to discuss problems using mailing list and > submit/discuss issues @github. > > > > > > ------------------ 原始邮件 ------------------ > > 发件人: "Zen Lin"<zenlintechnofr...@gmail.com>; > > 发送时间: 2019年1月15日(星期二) 中午12:07 > > 收件人: "dev"<dev@servicecomb.apache.org>; > > > > 主题: Re: [VOTE]Tracking the Github issue discussions to > dev@servicecomb.apache.org > > > > > > > > If there is no one knows how the Infra team track the github notification > > to commits list, I am going to ask the Infra team for the details, and > will > > help to research the feasibility of separation. > > > > Best Regards, > > --- > > Zen Lin > > zenlintechnofr...@gmail.com > > Focused on Micro Service and Apache ServiceComb > > > > > > Zen Lin <zenlintechnofr...@gmail.com> 于2019年1月15日周二 上午11:56写道： > > > > > Is there anyone knows how Infra group track the github notification to > > > comm...@servicecomb.apache.org? > > > If it is using github API, it is work to seperate github issue. > > > > > > Best Regards, > > > --- > > > Zen Lin > > > zenlintechnofr...@gmail.com > > > Focused on Micro Service and Apache ServiceComb > > > > > > > > > Willem Jiang <willem.ji...@gmail.com> 于2019年1月15日周二 上午11:44写道： > > > > > >> We cannot just redirect the question to the Infra team without doing > > >> the research first. > > >> My suggestion is we need to do some research to figure out how to > > >> separate the github issue notification from the github notification > > >> stream. > > >> Then we can give the Infra team instructions to do the work with their > > >> admin right. > > >> If we cannot get there, we could consider to disable the github issue > > >> function to let user use mail to ask questions directly. > > >> > > >> Willem Jiang > > >> > > >> Twitter: willemjiang > > >> Weibo: 姜宁willem > > >> > > >> On Tue, Jan 15, 2019 at 9:54 AM Zen Lin <zenlintechnofr...@gmail.com> > > >> wrote: > > >> > > > >> > Yeah, > > >> > If we track the github issue to dev mail, we can watch the issue > > >> > contents in the dev mailing list. > > >> > If you want your reply can posted to the github issue, you can > > >> > reply the mail sent by github, in that way, the reply can be posted > > >> > on issue and also be sent to the dev mailing list. > > >> > > > >> > Anyway, as Willem said, we now have tracked the github > > >> > notification to comm...@servicecomb.apache.org, we just need > > >> > to seperate them from the github notification. > > >> > > > >> > Hi Willem, > > >> > As I known, this will be implemented by Apache Infra group. > > >> > What about to create a vote for this, and then I will create an > > >> > issue to Apache Infra, > > >> > or just create a mail to copy to infrastructure-...@apache.org > > >> > > > >> > Best Regards, > > >> > --- > > >> > Zen Lin > > >> > zenlintechnofr...@gmail.com > > >> > Focused on Micro Service and Apache ServiceComb > > >> > > > >> > > > >> > Willem Jiang <willem.ji...@gmail.com> 于2019年1月15日周二 上午9:27写道： > > >> > > > >> > > 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 > > >> > > > > > > > >> > > > > > > >> > > > > >> > > > >
