+1
The simpler the better.

On Fri, Jun 2, 2017 at 9:16 PM, Ivan Kelly <iv...@apache.org> wrote:

> +1 from me. Always good to reduce barriers to participation.
>
> -Ivan
>
> On Fri, Jun 2, 2017 at 12:29 AM, Matteo Merli <mme...@apache.org> 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 and to create labels that fit our
> > workflow.
> >
> >
> > On Thu, Jun 1, 2017 at 3:03 PM Sijie Guo <guosi...@gmail.com> wrote:
> >
> >> 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 <guosi...@gmail.com> wrote:
> >>
> >> > 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 it work out. I am starting this email
> >> thread
> >> > to vote for this.
> >> >
> >> > The vote will be:
> >> >
> >> > - Start using Github issues/pull requests for issue tracking for 3
> >> months.
> >> > - During this 3 months, we will continue using both JIRA and Github
> >> issues.
> >> > - After 3 months, if the community decides whether we should continue
> >> > using Github issues or moving from JIRA to Github issues. (The final
> >> > decision will be a separate vote in 3 months)
> >> >
> >> > Please vote +1 if in favor of trying out Github issues and -1 if not.
> >> >
> >> > See below thread and community meeting notes
> >> > <
> >> https://cwiki.apache.org/confluence/display/BOOKKEEPER/
> 2017-06-01+Meeting+notes
> >> >
> >> > for reference:
> >> >
> >> > http://mail-archives.apache.org/mod_mbox/bookkeeper-dev/201705.mbox/%
> >> > 3CCAO2yDyYKmUiSfGfkGCKtfP8mmQtcJubGoMO-KsWsjM9_3pOd0Q%40mail
> .gmail.com
> >> %3E
> >> >
> >> > - Sijie
> >> >
> >>
>

Reply via email to