[Reviewers] FYI: Phabricator experiment

[Gregory Szorc]

On Thu, Jun 15, 2017 at 11:12 AM, Augie Fackler <raf at durin42.com> wrote:

>
> > On Jun 15, 2017, at 13:34, Kevin Bullock <kbullock at ringworld.org> wrote:
> >
> >> On Jun 15, 2017, at 12:25, Augie Fackler <raf at durin42.com> wrote:
> >>
> >> I was figuring we'd have Phabricator send emails to the list, but if
> you wanted to use the experimental Phabricator workflow, you'd have to
> submit /to Phabricator/.
> >
> > Ahh, okay. So if someone submits a patch via Phabricator, we'd still get
> a notification on -devel (as we do for bugs). That seems reasonable for
> this experiment.
> >
> > Another question for the group: How do we configure authentication in
> Phabricator for a community project like Mercurial, such that anyone can
> review patches there (and ideally we don't have to create accounts for
> every reviewer)?
>
> I think it's easy to turn on some kind of OpenID authentication or
> something? I've never set up a phabricator, but hopefully the docs are
> sufficiently clear.
>
> (I can also, presumably, poke around in the configs for our internal
> Phabricator we use for narrowhg.)
>

Yes, it supports auth federation with common service providers. In addition
to its own user database of course. We probably want to federate because
nobody likes creating accounts.

API requests are authenticated using tokens. The Arcanist client has a nice
workflow to guide you through the process of creating a token and storing
it to your ~/.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-reviewers/attachments/20170615/a26f4cd6/attachment-0002.html>