One important step is turn off user talk page Beta Feature for each opted-in users and then disable the Beta Feature permanently.

In T370722#10005410, @Bugreporter wrote:

One important step is turn off user talk page Beta Feature for each opted-in users and then disable the Beta Feature permanently.

Great spot, @Bugreporter. @Trizek-WMF and I will ensure this step is accounted for in the un-deployment sequence.

Thank you for saying something; if any other ideas of this sort emerge, we'd value you sharing them with us!

In T370722#10005410, @Bugreporter wrote:

One important step is turn off user talk page Beta Feature for each opted-in users and then disable the Beta Feature permanently.

It is already covered: T248309: StructuredDiscussions (Flow): Prevent users from enabling Flow on their user talk page (beta feature) :)

In T370722#10012556, @Trizek-WMF wrote:

In T370722#10005410, @Bugreporter wrote:

One important step is turn off user talk page Beta Feature for each opted-in users and then disable the Beta Feature permanently.

It is already covered: T248309: StructuredDiscussions (Flow): Prevent users from enabling Flow on their user talk page (beta feature) :)

What I mean is disable for people currently using it in user talk page.

Update

Today, @Trizek-WMF defined three deployment phases (see below). Next, Benoît is going to:

1. Assign each wiki where Flow is active (T350073) to one of these three un-deployment phases (see below)
2. Estimate how much time wikis in each un-deployment phase will need for the various steps within the un-deployment sequence (e.g. manually migrating Flow boards to sub-pages, enabling a script to mass-migrate Flow boards that had not been moved manually, etc.)

In parallel, I'll be working with Editing Engineering to estimate the time needed for doing things like writing a migration script, QA'ing said script, and addressing any issues that script surfaces.

Deployment phases

@ppelberg the task title mentions LiquidThreads (related T350164: Undeploy LiquidThreads), but the work here seems specific to Flow. Is there a plan/timeline for LiquidThreads as well?

In T370722#10295685, @kostajh wrote:

@ppelberg the task title mentions LiquidThreads (related T350164: Undeploy LiquidThreads), but the work here seems specific to Flow. Is there a plan/timeline for LiquidThreads as well?

I'm on it. :)

Dates regarding Phases 1 and 2 will be discussed with the Editing team on November 13.

While deleting one of the the Topic pages on Commons, I came across this error:
[b81ebde5-b932-404b-8f19-0dd5929528a0] 2024-12-24 11:03:36: Fatal exception of type "MediaWiki\Page\PageAssertionException"

This follows after a deletion request at Commons' Admin Noticeboard about some obsolete flow topics. Feel free to move this to any appropriate place though, if it doesn't belong here. I;d say sorry in advance.

In T370722#10422664, @Aafi wrote:

While deleting one of the the Topic pages on Commons, I came across this error:
[b81ebde5-b932-404b-8f19-0dd5929528a0] 2024-12-24 11:03:36: Fatal exception of type "MediaWiki\Page\PageAssertionException"

This follows after a deletion request at Commons' Admin Noticeboard about some obsolete flow topics. Feel free to move this to any appropriate place though, if it doesn't belong here. I;d say sorry in advance.

@ppelberg @Trizek-WMF Something is wrong here.

Please file separate tasks for separate issues; this task is about defining a timeline only.
The issue you run into ("MediaWiki\Page\PageAssertionException: The given PageIdentity Special:Badtitle/NS2601:Sn8f417nuorxes8d does not represent a proper page") is a bit similar to T339879. Thanks a lot!

@ppelberg @Pppery I have a few questions to ask:

1. There are sites using LQT. (enwikinews, enwikitionary, huwikipedia, translatewiki) However, there aren't any phases and tasks for them. Will you create a task for processing pages of them?
2. Some closed wikis (for example, strategy.wikimedia.org) were still using Flow or LQT until it was closed. When the extensions are eventually removed, archives in closed wikis are inaccessible anymore. It is recommended to reopen these sites temporarily to process those discussion pages.

In T370722#10609952, @angry_sovietball wrote:

@ppelberg @Pppery I have a few questions to ask:

1. There are sites using LQT. (enwikinews, enwikitionary, huwikipedia, translatewiki) However, there aren't any phases and tasks for them. Will you create a task for processing pages of them?

Yes. We are finishing the work with Flow first. The work on LQT is documented on T350164: Undeploy LiquidThreads and sub-tasks.

2. Some closed wikis (for example, strategy.wikimedia.org) were still using Flow or LQT until it was closed. When the extensions are eventually removed, archives in closed wikis are inaccessible anymore. It is recommended to reopen these sites temporarily to process those discussion pages.

I don't think we should. The entire wiki is already an archive. When the conversion of Flow/LQT contents is performed, we will replace the contents with standard talk pages.

@Trizek-WMF Well, as you have said, those closed wiki is an archive. But removing Flow directly would cause archive damage of the site. So we should fix them before being inaccessible.

On the other hand, translatewiki is not on the list on T350164.

In T370722#10610416, @angry_sovietball wrote:

On the other hand, translatewiki is not on the list on T350164.

Translatewiki is not a Wikimedia Foundation managed wiki (https://www.spi-inc.org/projects/translatewiki.net/).