[RESULT] [VOTE] Use Github Issues for Issue Tracking

2017-06-08 Thread Sijie Guo
Closed this voting thread. The vote for "trying out Github" is accepted with 5 +1 (3 binding votes) and 0 -1. We can start trying out Github issues and build the workflow that is suitable for us. If anyone has the idea on the workflow, feel free to raise the discussion and propose the changes. Th

Re: [VOTE] Use Github Issues for Issue Tracking

2017-06-07 Thread Flavio Junqueira
Sure, feel free to close the vote. Thanks for bearing with me. -Flavio > On 06 Jun 2017, at 18:07, Sijie Guo wrote: > > On Tue, Jun 6, 2017 at 12:41 AM, Flavio Junqueira > wrote: > >> >>> On 05 Jun 2017, at 18:30, Sijie Guo wrote: >>> >>> On Mon, Jun 5, 2017 at 2:53

Re: [VOTE] Use Github Issues for Issue Tracking

2017-06-06 Thread Sijie Guo
On Tue, Jun 6, 2017 at 12:41 AM, Flavio Junqueira wrote: > > > On 05 Jun 2017, at 18:30, Sijie Guo wrote: > > > > On Mon, Jun 5, 2017 at 2:53 AM, Flavio Junqueira wrote: > > > >> Ok, so why don't we make clear what we are voting for? > > > > If this vote is approved, then the outcome is that th

Re: [VOTE] Use Github Issues for Issue Tracking

2017-06-06 Thread Sijie Guo
On Tue, Jun 6, 2017 at 12:41 AM, Flavio Junqueira wrote: > > > On 05 Jun 2017, at 18:30, Sijie Guo wrote: > > > > On Mon, Jun 5, 2017 at 2:53 AM, Flavio Junqueira wrote: > > > >> Ok, so why don't we make clear what we are voting for? > > > > If this vote is approved, then the outcome is that th

Re: [VOTE] Use Github Issues for Issue Tracking

2017-06-06 Thread Flavio Junqueira
> On 05 Jun 2017, at 18:30, Sijie Guo wrote: > > On Mon, Jun 5, 2017 at 2:53 AM, Flavio Junqueira wrote: > >> Ok, so why don't we make clear what we are voting for? > > If this vote is approved, then the outcome is that the community is going >> to work on a plan to move to github issues, and

Re: [VOTE] Use Github Issues for Issue Tracking

2017-06-05 Thread Sijie Guo
On Mon, Jun 5, 2017 at 2:53 AM, Flavio Junqueira wrote: > Ok, so why don't we make clear what we are voting for? If this vote is approved, then the outcome is that the community is going > to work on a plan to move to github issues, and that plan will be voted? I believed that I made the clari

Re: [VOTE] Use Github Issues for Issue Tracking

2017-06-05 Thread Flavio Junqueira
Ok, so why don't we make clear what we are voting for? If this vote is approved, then the outcome is that the community is going to work on a plan to move to github issues, and that plan will be voted? Or is it going to be considered a code change and require just a +1 from a committer? The reas

Re: [VOTE] Use Github Issues for Issue Tracking

2017-06-03 Thread Sijie Guo
On Sat, Jun 3, 2017 at 7:39 AM, Flavio Junqueira wrote: > Thanks for pushing this through, Sijie. I have a couple of concerns about > this proposal: > > 1- There is a proposal, but I'm not seeing a workflow defined for github > issues. Should we define one and make that part of the vote? > Defin

Re: [VOTE] Use Github Issues for Issue Tracking

2017-06-03 Thread Flavio Junqueira
Thanks for pushing this through, Sijie. I have a couple of concerns about this proposal: 1- There is a proposal, but I'm not seeing a workflow defined for github issues. Should we define one and make that part of the vote? 2- I'm not sure what the binding votes are and what the approval process

Re: [VOTE] Use Github Issues for Issue Tracking

2017-06-03 Thread Flavio Junqueira
Thanks for pushing this through, Sijie. I have a couple of concerns about this proposal: 1- There is a proposal, but I'm not seeing a workflow defined for github issues. Should we define one and make that part of the vote? 2- I'm not sure what the binding votes are and what the approval process

Re: [VOTE] Use Github Issues for Issue Tracking

2017-06-02 Thread Jia Zhai
+1 The simpler the better. On Fri, Jun 2, 2017 at 9:16 PM, Ivan Kelly wrote: > +1 from me. Always good to reduce barriers to participation. > > -Ivan > > On Fri, Jun 2, 2017 at 12:29 AM, Matteo Merli wrote: > > +1 > > > > Having issues and PR in one tool is a great plus. > > > > If this proposa

Re: [VOTE] Use Github Issues for Issue Tracking

2017-06-02 Thread Ivan Kelly
+1 from me. Always good to reduce barriers to participation. -Ivan On Fri, Jun 2, 2017 at 12:29 AM, Matteo Merli wrote: > +1 > > Having issues and PR in one tool is a great plus. > > If this proposal is accepted, we should also ask INFRA to allow to assign > issues/PRs to committers/contributors

Re: [VOTE] Use Github Issues for Issue Tracking

2017-06-01 Thread Matteo Merli
+1 Having issues and PR in one tool is a great plus. If this proposal is accepted, we should also ask INFRA to allow to assign issues/PRs to committers/contributors and to create labels that fit our workflow. On Thu, Jun 1, 2017 at 3:03 PM Sijie Guo wrote: > My vote on this is +1. > > Simply

Re: [VOTE] Use Github Issues for Issue Tracking

2017-06-01 Thread Sijie Guo
My vote on this is +1. Simply because I'd like to have one central place for tracking issues and reviewing pull requests. - Sijie On Thu, Jun 1, 2017 at 12:59 PM, Sijie Guo wrote: > Per the community meeting > >

Re: [VOTE] Use Github Issues for Issue Tracking

2017-06-01 Thread Enrico Olivelli
+1 let's try github Il gio 1 giu 2017, 21:59 Sijie Guo ha scritto: > Per the community meeting > < > https://cwiki.apache.org/confluence/display/BOOKKEEPER/2017-06-01+Meeting+notes > > > this morning, JV proposed to start use Github issues for issue tracking for > a few months and see how does i

[VOTE] Use Github Issues for Issue Tracking

2017-06-01 Thread Sijie Guo
Per the community meeting this morning, JV proposed to start use Github issues for issue tracking for a few months and see how does it work out. I am starting this email thread to vote for this. The vote will be: -