I would rather us not use phabricator at all. One of the largest reasons is
a fear that if phabricator is shut down we will lose the comments on it. We
can count on the ASF to maintain and backup review board. If it flaky we
can file some tickets with infra or bring this fact up in a board meeting
until it is resolved.




On Thu, Oct 17, 2013 at 4:12 PM, Thejas Nair <the...@hortonworks.com> wrote:

> +1
> But I have found that apache reviewboard is sometimes flaky. I assume
> that we can still use phabricator in one-off cases, if there is an
> extended downtime for reviewboard.
>
>
> On Thu, Oct 17, 2013 at 1:08 PM, Alan Gates <ga...@hortonworks.com> wrote:
> > Major +1 (non-binding).  Using 3rd party tools where we have no option
> for support or help is not good.
> >
> > Alan.
> >
> > On Oct 16, 2013, at 5:32 PM, Edward Capriolo wrote:
> >
> >> Our wiki has instructions for posting to phabricator for code reviews.
> >> https://cwiki.apache.org/confluence/display/Hive/PhabricatorCodeReview
> >>
> >> Phabricator now requires an external facebook account to review patches,
> >> and we have no technical support contact where phabricator is hosted. It
> >> also seems like some of the phabricator features are no longer working.
> >>
> >> Apache has a review board system many people are already using.
> >> https://reviews.apache.org/account/login/?next_page=/dashboard/
> >>
> >> This vote is to remove the phabricator instructions from the wiki. The
> >> instructions will reference review board and that will be the only
> system
> >> that Hive supports for patch review process.
> >>
> >> +1 is a vote for removing the phabricator instructions from the wiki.
> >>
> >> Thank you,
> >> Edward
> >
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

Reply via email to