[Reviewers] FYI: Phabricator experiment

[Gregory Szorc]

On Thu, Jun 15, 2017 at 10:34 AM, 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.
>

Harold (https://secure.phabricator.com/book/phabricator/article/herald/)
allows you to configure notifications within Phabricator. I'm guessing
we'll want a special user account associated with the devel list that has a
Harold notification to send updates when review activity occurs. Although,
there may be a special mode to notify email lists because e.g. LLVM's
Phabricator emails have reasonable author attribution:
http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20170612/thread.html


>
> 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)?
>
> > Nobody is building the tool I really want, which would parse emails and
> try to interpret comments-on-email-diffs and plunk them back into a
> web-based tool. A man can dream....
>
> Yeah, if we want that we're just gonna have to build it. :)
>
> pacem in terris / мир / शान्ति / ‎‫سَلاَم‬ / 平和
> Kevin R. Bullock
>
> _______________________________________________
> Reviewers mailing list
> Reviewers at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/reviewers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-reviewers/attachments/20170615/17182a2b/attachment-0002.html>