Page MenuHomeMiraheze

Consider migration from unmaintained Phabricator to community-maintained Phorge Phabricator fork
Closed, ResolvedPublic

Description

Link: Phorge

Rationale: Phabricator is no longer maintained, and cherry-picking in updates from the Wikimedia-controlled unofficial fork was only intended to be a near-term, Band-Aid™ solution

Alternate: Consider other alternatives to Phabricator

Event Timeline

Dmehus triaged this task as Low priority.Mar 6 2022, 16:43
Dmehus created this task.
MacFan4000 changed the task status from Open to Stalled.EditedMar 6 2022, 17:54
MacFan4000 subscribed.

Stalled until there is an actual release of phorge, could take awhile

Unknown Object (User) closed this task as Declined.Mar 20 2022, 10:32
Unknown Object (User) claimed this task.
Unknown Object (User) subscribed.

We don't need to stall it. If this becomes necessary to do then it can be reconsidered, until then, with no actions we can take, I don't see why this should remain open. It can be reopened by someone else if this is the incorrect action here.

We don't need to stall it. If this becomes necessary to do then it can be reconsidered, until then, with no actions we can take, I don't see why this should remain open. It can be reopened by someone else if this is the incorrect action here.

The current Phabricator implementation is unmaintained and using an unapproved Wikimedia fork, which is customized for Wikimedia purposes/needs and with no broader community input, is non-viable over the long-term, so we do need to look something longer term. I believe that triaging this as low and classifying it as stalled, as MacFan4000, did is the best solution here, chiefly to prevent duplicate tasks from being created and also to maintain it on SRE's longer term radar. I view longer term as 6-12 months (or longer).

Unknown Object (User) added a comment.Mar 20 2022, 17:23

We don't need to stall it. If this becomes necessary to do then it can be reconsidered, until then, with no actions we can take, I don't see why this should remain open. It can be reopened by someone else if this is the incorrect action here.

The current Phabricator implementation is unmaintained and using an unapproved Wikimedia fork, which is customized for Wikimedia purposes/needs and with no broader community input, is non-viable over the long-term, so we do need to look something longer term. I believe that triaging this as low and classifying it as stalled, as MacFan4000, did is the best solution here, chiefly to prevent duplicate tasks from being created and also to maintain it on SRE's longer term radar. I view longer term as 6-12 months (or longer).

Well there is nothing we can do right now. This is basically the same things as when we close upstream tasks, as no actionable things we can do at the moment.

John edited projects, added Infrastructure (SRE); removed Site Reliability Engineering.
John subscribed.

I am marking this as declined as there is no current need to evaluate new software from an Infrastructure perspective.

It feels weird to have a stalled task on a software being released that we arguably haven’t agreed to use - when Phorge is in a release state, we can evaluate to move to it. Until then, Infrastructure are currently happy managing and dealing with the Phabricator software as is - if a need arises to move (which we will constantly evaluate), we will make software decisions based on the available options - unfortunately Phorge is not an available option currently.

In T8893#181599, @John wrote:

I am marking this as declined as there is no current need to evaluate new software from an Infrastructure perspective.

It feels weird to have a stalled task on a software being released that we arguably haven’t agreed to use - when Phorge is in a release state, we can evaluate to move to it. Until then, Infrastructure are currently happy managing and dealing with the Phabricator software as is - if a need arises to move (which we will constantly evaluate), we will make software decisions based on the available options - unfortunately Phorge is not an available option currently

We don't need to stall it. If this becomes necessary to do then it can be reconsidered, until then, with no actions we can take, I don't see why this should remain open. It can be reopened by someone else if this is the incorrect action here.

The current Phabricator implementation is unmaintained and using an unapproved Wikimedia fork, which is customized for Wikimedia purposes/needs and with no broader community input, is non-viable over the long-term, so we do need to look something longer term. I believe that triaging this as low and classifying it as stalled, as MacFan4000, did is the best solution here, chiefly to prevent duplicate tasks from being created and also to maintain it on SRE's longer term radar. I view longer term as 6-12 months (or longer).

Well there is nothing we can do right now. This is basically the same things as when we close upstream tasks, as no actionable things we can do at the moment.

Okay, sounds good. Any objections to me adding the Upstream project for monitoring purposes?

Noting that there is now an official release of phorge.

Reopening now that there is an official release. I think we can evaluate this again.

I just want to make sure that the EOL of Phabricator is over. There was an update in May 2022. https://secure.phabricator.com/w/changelog/2022.21/

Unknown Object (User) added a comment.Sep 15 2022, 00:36

I just want to make sure that the EOL of Phabricator is over. There was an update in May 2022. https://secure.phabricator.com/w/changelog/2022.21/

it is still maintained for security only.

Unknown Object (User) moved this task from Unsorted to Long Term on the Universal Omega board.Sep 19 2022, 07:31
John removed Unknown Object (User) as the assignee of this task.Oct 22 2022, 17:57
John moved this task from Short Term to Long Term on the Infrastructure (SRE) board.

This is something we can look into post Swift work, as that remains the priority for Infra currently. Given Phabricator is security maintained, there is no urgency currently.

In T8893#199118, @John wrote:

This is something we can look into post Swift work, as that remains the priority for Infra currently. Given Phabricator is security maintained, there is no urgency currently.

The swift work is now finished.

Phabricator isn’t even security maintained anymore. (No commits to the repos since last June) Furthermore, the upstream install is no longer functioning.

If there are no more security patches for Phab, I would recommend proceeding with this and even considering making it normal priority. What would the steps entail? Are there the same SQL tables, etc.?

https://phabricator.wikimedia.org/T328595 is relevant. It'll probably be useful to see how the WMF does things

Unknown Object (User) removed a project: Universal Omega.Mar 18 2023, 03:26
Unknown Object (User) unsubscribed.

Looks like the WMF didn't have much luck importing tasks from Phabricator to Phorge. Still, we should switch anyway.

From what I've read, you can't import tasks from Phabricator instance to Phabricator instance either way due to the way its designed (and so WMF couldn't test Phorge on a separate instance as they couldn't import some tasks without importing the entire database which includes private tasks) but WMF has approved migrating, per https://phabricator.wikimedia.org/T333885

I've been told there is a way but I'm not sure. Either way, switching without importing tasks would mean that we would have to keep Phabricator in a read only state indefinitely as we frequently need to refer to old tasks.

Upgrading to phorge is a normal phab upgrade with 2 extra steps. There is a guide that details it. I've done it for fossbots and it took 15 minutes.

I note that I changed the installation path at the same time.

We should probably think about moving forward with this - the WMF now uses Phorge.

MacFan4000 raised the priority of this task from Low to Normal.Oct 18 2023, 15:57

Raising priority as phab121 has been updated to bookworm, and phabricator has little support for php 8.2

Paladox claimed this task.
Paladox subscribed.

Switched to phroge.