Re: [DISCUSS] Apache Gitbox

2017-07-28 Thread Aldrin Piri
Certainly can appreciate that sentiment, Tony. I have a pretty good flow doing reviews that kind of abstracts away the fact that it is a PR versus just another branch/remote. However, when it comes to code reviews, the vast majority of my effort happens in GitHub at the moment. I believe there a

Re: [DISCUSS] Apache Gitbox

2017-07-28 Thread Andy LoPresto
I don’t think enabling this feature requires contributors to provide patches via GitHub, as attaching patches to the Jira is still available. I see this improving the workflow for the committers who are reviewing and merging PRs. Encapsulating some of the repetitive git invocations that committe

Re: [DISCUSS] Apache Gitbox

2017-07-28 Thread Tony Kurc
Worth considering, this twitter post has been circulating the blogosphere: https://twitter.com/agentdero/status/889582259522736128 I'd like to ensure we don't forget other means of providing patches (attaching a patch to a ticket). While github is convenient to some, using it as the sole source of

Re: [DISCUSS] Apache Gitbox

2017-07-28 Thread Tony Kurc
I'm a strong +0. I don't think think it is a huge step forward, but it isn't a step back either. On Jul 28, 2017 5:42 PM, "Andy LoPresto" wrote: > +1 to enable gitbox. > > Andy LoPresto > alopre...@apache.org > *alopresto.apa...@gmail.com * > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E

Re: [DISCUSS] Apache Gitbox

2017-07-28 Thread Andy LoPresto
+1 to enable gitbox. Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Jul 28, 2017, at 12:56 PM, Matt Burgess wrote: > > +1, I meant to bring this up after I saw the conversation on the Apache > Streams list.

Re: [DISCUSS] Apache Gitbox

2017-07-28 Thread Matt Burgess
+1, I meant to bring this up after I saw the conversation on the Apache Streams list. Seems like a great improvement to the workflow! > On Jul 28, 2017, at 3:26 PM, Suneel Marthi wrote: > > +1 to move to gitbox > >> On Fri, Jul 28, 2017 at 3:05 PM, Aldrin Piri wrote: >> >> Excellent. Thanks

Re: [DISCUSS] Apache Gitbox

2017-07-28 Thread Suneel Marthi
+1 to move to gitbox On Fri, Jul 28, 2017 at 3:05 PM, Aldrin Piri wrote: > Excellent. Thanks for the input, Suneel. The before and after links are > especially helpful. > > > On Fri, Jul 28, 2017 at 3:00 PM, Suneel Marthi wrote: > > > We migrated Apache OpenNLP to gitbox (beginning of July) and

Re: [DISCUSS] Apache Gitbox

2017-07-28 Thread Aldrin Piri
Excellent. Thanks for the input, Suneel. The before and after links are especially helpful. On Fri, Jul 28, 2017 at 3:00 PM, Suneel Marthi wrote: > We migrated Apache OpenNLP to gitbox (beginning of July) and even had a > release immediately. > > Yes, the PR commit workflow is lot simpler now w

Re: [DISCUSS] Apache Gitbox

2017-07-28 Thread Jeff Zemerick
Also from OpenNLP -- yes, the workflow is much simpler and faster. I highly recommend it. On Fri, Jul 28, 2017 at 3:00 PM, Suneel Marthi wrote: > We migrated Apache OpenNLP to gitbox (beginning of July) and even had a > release immediately. > > Yes, the PR commit workflow is lot simpler now with

Re: [DISCUSS] Apache Gitbox

2017-07-28 Thread Suneel Marthi
We migrated Apache OpenNLP to gitbox (beginning of July) and even had a release immediately. Yes, the PR commit workflow is lot simpler now with gitbox (just a button click). I would definitely recommend moving Nifi to gitbox, if anything it makes a committer's life lot easier. Before Gitbox, t

[DISCUSS] Apache Gitbox

2017-07-28 Thread Aldrin Piri
Hey folks, I saw mention on the Incubator general mailing list about Gitbox [1]. From that message it seems like it would help considerably with some of the maintenance tasks we perform on the repository. Has anyone in the community used it on another project and have any opinions on it? Doing