[llvm-dev] Phabricator Creator Pulling the Plug

Chris Tetreault via llvm-dev llvm-dev at lists.llvm.org
Fri Oct 1 09:47:18 PDT 2021

(replying to my initial email because the thread seems to have gone off on a tangent)

A long term plan on what to do (migrate to github PRs? Something else?) is important, but let’s not get lost in the weeds: we have breakages with phabricator today. I think it’s important to not let our daily workflows degrade while we argue about what to do next. Minimally, we could fork phabricator into the LLVM project and fix the arcanist breakage. I don’t think maintaining a fork long term is a good idea, especially since phorge exists. We should not advertise our fork as being “maintained” to anybody, aside from the minimal goal of keeping existing workflows for LLVM functional while we decide on a migration plan.

My personal opinion on the topic of “using phabricator vs github PRs” is to stick with phabricator. I personally prefer the “push patch sets, then merge a patch into the tree” approach to the github “fork the repo, push some changes to your fork, then merge your fork with upstream”. I occasionally commit to CMake (which uses gitlab), and always find the experience quite confusing and awkward. I don’t know much about Phorge, but if it’s a Phabricator clone, and is actually being maintained, it seems to me to be a good migration target. I would also personally be fine with using Gerrit.

   Chris Tetreault

From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of Chris Tetreault via llvm-dev
Sent: Thursday, September 30, 2021 2:54 PM
To: MyDeveloper Day <mydeveloperday at gmail.com>; cfe-commits <cfe-commits at lists.llvm.org>
Cc: llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] Phabricator Creator Pulling the Plug

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
As I, and others have noticed, it seems that as of today, there’s some certificate issue with arcanist. (See: https://lists.llvm.org/pipermail/llvm-dev/2021-September/153019.html) The fix seems simple, and a PR is up, but looking through the PR activity, it seems that the PR will not be accepted because Phabricator is no longer being maintained. It seems that arc has become the first casualty of the discontinuation of maintenance of phabricator.

I know that arc is not universally used, but I think it’s a serious blow to many people’s workflows. I think that MyDeveloperDay’s question might have just become a bit more urgent.

I suppose in the short-term, we could fork the phabricator repos in order to fix little issues like this. Alternately, we should probably stop recommending arcanist (unless we want to provide instructions on how to fix any breakages that come along).

   Chris Tetreault

From: llvm-dev <llvm-dev-bounces at lists.llvm.org<mailto:llvm-dev-bounces at lists.llvm.org>> On Behalf Of MyDeveloper Day via llvm-dev
Sent: Wednesday, August 18, 2021 10:17 AM
To: llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>>; cfe-commits <cfe-commits at lists.llvm.org<mailto:cfe-commits at lists.llvm.org>>
Subject: [llvm-dev] Phabricator Creator Pulling the Plug

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

I'm a massive fan of Phabricator, and I know there is often lots of contentious discussion about its relative merits vs github,

But unless I missed this, was there any discussion regarding the recent "Winding Down" announcement of Phabricator? and what it might mean for us in LLVM


Personally I'm excited by the concept of a community driven replacement ( https://we.phorge.it/) .
epriestley did a truly amazing job, it wasn't open to public contributions. Perhaps more open development could lead to closing some of the github gaps that were of concern.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20211001/d51ae1a9/attachment.html>

More information about the llvm-dev mailing list