Re: [Lazy Consensus] Move from JIRA to GitHub Issues

I like this move. Thanks! On Wed, May 17, 2017 at 9:38 PM, Joan Touzet wrote: > Hi everyone. > > As most of you know, a few months ago we moved many of our primary > repositories from primary Apache hosting to primary GitHub hosting. A > major reason we did so was to leverage

Re: [Lazy Consensus] Move from JIRA to GitHub Issues

As an user, I support the change. Needless to say, moving to GitHub is clearly a move that will ease the work of both current and future contributors. We already spend almost the entire day on GitHub , so it will be better to have everything in just one platform  2017-05-17 18:36 GMT-03:00

Re: [Lazy Consensus] Move from JIRA to GitHub Issues

nice +1 :) > On 17 May 2017, at 22:32, Eli Stevens (Gmail) wrote: > > As a user and occasional bug reporter, I welcome the change. > > Searching for existing issues in JIRA was painful, mostly due to > feeling like I had to repeat myself in saying that I wasn't interested

Re: [Lazy Consensus] Move from JIRA to GitHub Issues

As a user and occasional bug reporter, I welcome the change. Searching for existing issues in JIRA was painful, mostly due to feeling like I had to repeat myself in saying that I wasn't interested in any of the other projects on the instance. On Wed, May 17, 2017 at 1:59 PM, Jan Lehnardt

Re: [Lazy Consensus] Move from JIRA to GitHub Issues

\o\ /o/ \o/ <3 > On 17. May 2017, at 21:38, Joan Touzet wrote: > > Hi everyone. > > As most of you know, a few months ago we moved many of our primary > repositories from primary Apache hosting to primary GitHub hosting. A > major reason we did so was to leverage the better

[Lazy Consensus] Move from JIRA to GitHub Issues

Hi everyone. As most of you know, a few months ago we moved many of our primary repositories from primary Apache hosting to primary GitHub hosting. A major reason we did so was to leverage the better user experience of GitHub, especially for community interaction. It's now time for us to move