Investigate the implications of setting Flow to read-only for all users
Open, Needs TriagePublic
Actions

Assigned To

None

Authored By

	• Tchanders
	Tue, Jul 23, 9:44 AM

Description

Background

Flow can be put into read-only mode for everyone, via the config $wgFlowReadOnly.

As part of the effort to remove support for Flow (T370722), there is the possibility of using read-only mode on WMF production sites where Flow was previously actively used.

Investigation

In read-only mode, users can read, delete or undelete posts (code here).

Is this acceptable, or do we need to allow any other actions, for example suppression?

Notes

Since Flow doesn't support temporary accounts, it was already set to read-only for testwiki, when temporary accounts were deployed to testwiki (T370322).

Related Objects
Search...

Status	Assigned	Task
Open	None	T335670 Disable Flow/Structured Discussions from all namespaces, except for user talk pages, on Catalan Wikipedia
Open	None	T106123 Extensions needing to be removed from Wikimedia wikis
Open	None	T332022 [Epic] Undeploying StructuredDiscussions (Flow)
In Progress	Trizek-WMF	T370722 Set Flow sunsetting timeline and sequence
Open	None	T370753 Investigate the implications of setting Flow to read-only for all users

Event Timeline

• Tchanders created this task.Tue, Jul 23, 9:44 AM

Restricted Application added a project: Growth-Team. · View Herald TranscriptTue, Jul 23, 9:44 AM

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

• Tchanders edited parent tasks, added: T370722: Set Flow sunsetting timeline and sequence; removed: T332022: [Epic] Undeploying StructuredDiscussions (Flow).Tue, Jul 23, 9:45 AM

@ppelberg I've filed this as a follow-up to our discussion elsewhere.

Might involve a product/community judgement call as to what's acceptable, with some technical input regarding what delete/undelete actually do and whether suppress is even possible?

Michael moved this task from Inbox to Triaged on the Growth-Team board.Tue, Jul 23, 11:58 AM

Yes, good idea. One possible impact is that looks like it kills the Newsletter extension, except there will be found an alternative way to keep it.

Investigate the implications of setting Flow to read-only for all usersOpen, Needs TriagePublicActions