Page MenuHomeMiraheze

Consider migration from unmaintained Phabricator to community-maintained Phorge Phabricator fork
Open, LowPublic

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 added a subscriber: MacFan4000.

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

Universal_Omega claimed this task.
Universal_Omega added a subscriber: Universal_Omega.

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).

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 added a subscriber: John.

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/

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.