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.

Permalinks are now available everywhere by default.

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.

Hi y'all – thank you for being patient with me/us about this.

In T368632#10011490, @Gerges wrote:

Hi @DLynch, would you mind taking a look at this enabling request?

Meta: I've updated the task description to clarify the requirements of this task based on what @MNeisler and I talked about offline on 17 July 2024.

In T357600#9983296, @Jdlrobson wrote:

@ppelberg what is the long term plan for Flow? I assume it is going to be replaced with discussion tools at some point. Is there a timeline or any plans in motion?

Thank you for chiming in, @kostajh.

Meta: the next step on this ticket is describing the process I'm proposing KR 1.2 hypothesis "owners" and I follow to converge on a target improvement.

Per what @MNeisler and I talked about offline this week, the findings Megan shared in T369663#9982261 are precisely what we needed to move forward with T368988.

Maybe we could create a diagram similar to the one below to demonstrate the key properties of Edit Suggestions and Checks.

I'm moving this ticket back to Ready to be worked on to implement the following revision Nico identified, and we converged on as a team:

Meta: I've added the path forward we've converged on (T370322#9993052) to the newly-created Requirements section within the task description.

In T370322#9991693, @Tchanders wrote:

Note that we're awaiting approval from @ppelberg.

Thank you for affording me/us the space to think this through. Per what I shared in Slack, the Editing Team supports the path forward y'all are proposing, and putting into effect, with this ticket. See "Proposal" below.

Per what @ovasileva and I talked about offline during today's Editing - Web Team meeting, Editing is going to assume responsibility for testing talk pages to ensure the more targeted testing the Web Team completed in T365509#9965955 did not miss any issues.

hey @CCiufo-WMF – a question for you (we think!) emerged in a meeting between @DLynch, @Jdrewniak, @ovasileva, and I just now about how to make comment/topic permalinks appear in dark mode in a way that passes accessibility contrast checks.

Notes

• Edit Checks are reactions to actions you've explicitly taken
• Edit Suggestions are proactive suggestions based on inferences we/the software makes about what you are interested in and equipped to accomplish.

Next step: per today's team meeting, @nayoub is going to update this ticket with the base set of components we converged on and then resolve.

@Ryasmeen: this issue should now hopefully be fixed. Can you please test in the same way that helped you identify the issue [i] originally.

This issue is effectively resolved seeing as how it only existed in the ephemeral state where permalinks were not available by default at all wikis.

In T365583#9946857, @Mvolz wrote...

@Mvolz, three questions in response to this update...