I think as an Apache project, using code review tools outside apache should
never be a "requirement". I agree that arc/phab are great tools, and they
help the patch/review process a lot. But I think what is essential for long
term sustainability as a project is to lower the entry barriers for
contributing. Not every developer who wants to contribute some code will be
willing to work with phab/rb.
What I would suggest is to always have the option to submit patches via
jira, and make rb / phab optional.
Just my 2 cents,
Enis
On Thu, Apr 19, 2012 at 4:35 PM, Ashutosh Chauhan <hashut...@apache.org>wrote:
> Hit a new problem with arc today:
>
> Fatal error: Uncaught exception 'Exception' with message 'Host returned
> HTTP/200, but invalid JSON data in response to a Conduit method call:
> <br />
> <b>Warning</b>: Unknown: POST Content-Length of 9079953 bytes exceeds the
> limit of 8388608 bytes in <b>Unknown</b> on line <b>0</b><br />
>
> for(;;);{"result":null,"error_code":"ERR-INVALID-SESSION","error_info":"Session
> key is not present."}' in
> /Users/ashutosh/work/hive/libphutil/src/conduit/client/ConduitFuture.php:48
> Stack trace:
> #0
> /Users/ashutosh/work/hive/libphutil/src/future/proxy/FutureProxy.php(62):
> ConduitFuture->didReceiveResult(Array)
> #1
> /Users/ashutosh/work/hive/libphutil/src/future/proxy/FutureProxy.php(39):
> FutureProxy->getResult()
> #2
>
> /Users/ashutosh/work/hive/libphutil/src/conduit/client/ConduitClient.php(52):
> FutureProxy->resolve()
> #3
>
> /Users/ashutosh/work/hive/arcanist/src/workflow/diff/ArcanistDiffWorkflow.php(341):
> ConduitClient->callMethodSynchronous('differential.cr...', Array)
> #4 /Users/ashutosh/work/hive/arcanist/scripts/arcanist.php(266):
> ArcanistDiffWo in
> /Users/ashutosh/work/hive/libphutil/src/conduit/client/ConduitFuture.php on
> line 48
>
>
> Any ideas how to solve this?
>
> Thanks,
> Ashutosh
>
> On Wed, Apr 11, 2012 at 18:37, Edward Capriolo <edlinuxg...@gmail.com
> >wrote:
>
> > I think the most practical solution is try and use arc/phab and then
> > if there is a problem fall back to Jira and do it the old way.
> >
> > Edward
> >
> > On Wed, Apr 11, 2012 at 7:17 PM, Carl Steinbach <c...@cloudera.com>
> wrote:
> > > +1 to switching over to Git.
> > >
> > > As for the rest of the Phabricator/Gerrit/Reviewboard discussion, I
> think
> > > we should pick this up again at the contributor meeting on Wednesday.
> > >
> > > Thanks.
> > >
> > > Carl
> > >
> > > On Wed, Apr 11, 2012 at 12:19 PM, Ashutosh Chauhan <
> hashut...@apache.org
> > >wrote:
> > >
> > >> +1 on moving away from arc/phabricator. It works great when it works,
> > but
> > >> most of the time it doesnt work.
> > >>
> > >> Ashutosh
> > >>
> > >> On Wed, Apr 11, 2012 at 11:57, Owen O'Malley <omal...@apache.org>
> > wrote:
> > >>
> > >> > On Wed, Apr 11, 2012 at 11:48 AM, Edward Capriolo <
> > edlinuxg...@gmail.com
> > >> >
> > >> > wrote:
> > >> > > If we are going to switch from fabricator we just might as well go
> > >> > > back to not using anything. Review board was really clunky and
> > >> > > confusing.
> > >> >
> > >> > I'm mostly +1 to that. If no one is supporting phabricator, then it
> > >> > won't work for long. Personally, I'd love it if we could move Hive
> to
> > >> > git completely. Has anyone used gerrit? The videos of it make it
> look
> > >> > better than sliced bread.
> > >> >
> > >> > -- Owen
> > >> >
> > >>
> >
>
