Change Details

==== Background We are planning to deploy temporary accounts to testwiki (see parent task: T348895). Flow has not been updated to work with temporary accounts, and it is used on testwiki. We therefore proposed doing {T368910} in time for the testwiki deployment. Following discussions with @ppelberg and @Trizek-WMF, it appears there is more concern within communities about having Flow available to some users but not others, compared to making Flow read-only for everyone. The discussion concluded that it would be better to make Flow read-only for everyone on testwiki, ahead of temporary accounts deployment. ==== What needs doing Set `$wgFlowReadOnly = true` on testwiki, ahead of temporary accounts being deployed there. === Requirements In line with Monday’s (22 July) deployment of temp accounts to test wiki, Flow will be placed into a read-only state for everyone -- Where “read-only state” means people will NOT be able to: --- Start new topics ---Comment in existing discussions --- Take any other Flow-related action (e.g. hide, edit title, thank, report, etc.) [i] -- Where “everyone” means people who are: --- Logged in ---Logged out (read: holding temporary accounts)

==== Background We are planning to deploy temporary accounts to testwiki (see parent task: T348895). Flow has not been updated to work with temporary accounts, and it is used on testwiki. We therefore proposed doing {T368910} in time for the testwiki deployment. Following discussions with @ppelberg and @Trizek-WMF, it appears there is more concern within communities about having Flow available to some users but not others, compared to making Flow read-only for everyone. The discussion concluded that it would be better to make Flow read-only for everyone on testwiki, ahead of temporary accounts deployment. ==== What needs doing Set `$wgFlowReadOnly = true` on testwiki, ahead of temporary accounts being deployed there. === Requirements In line with Monday’s (22 July) deployment of temp accounts to test wiki, Flow will be placed into a read-only state for everyone -- Where “read-only state” means people will NOT be able to: --- Start new topics --- Comment in existing discussions --- Take any other Flow-related action (e.g. hide, edit title, thank, report, etc.) [i] -- Where “everyone” means people who are: --- Logged in --- Logged out (read: holding temporary accounts)

==== Background We are planning to deploy temporary accounts to testwiki (see parent task: T348895). Flow has not been updated to work with temporary accounts, and it is used on testwiki. We therefore proposed doing {T368910} in time for the testwiki deployment. Following discussions with @ppelberg and @Trizek-WMF, it appears there is more concern within communities about having Flow available to some users but not others, compared to making Flow read-only for everyone. The discussion concluded that it would be better to make Flow read-only for everyone on testwiki, ahead of temporary accounts deployment. ==== What needs doing Set `$wgFlowReadOnly = true` on testwiki, ahead of temporary accounts being deployed there. === Requirements In line with Monday’s (22 July) deployment of temp accounts to test wiki, Flow will be placed into a read-only state for everyone -- Where “read-only state” means people will NOT be able to: --- Start new topics --- Comment in existing discussions --- Take any other Flow-related action (e.g. hide, edit title, thank, report, etc.) [i] -- Where “everyone” means people who are: --- Logged in --- Logged out (read: holding temporary accounts)