The RFC at Wikipedia talk:Wikiproject Breakfast on the English Wikipedia has concluded, with consensus that the test installation of Flow at that location should be removed, restoring it to being a normal talk page. Can that please be done.
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Catrope | T122961 Remove Flow from Wikipedia talk:WikiProject Breakfast on enwp | |||
Open | None | T96301 Solution for disabling Flow on a page | |||
Resolved | matthiasmullie | T90075 Update and retest the convertToText script | |||
Invalid | None | T107097 convertToText.php not working | |||
Open | None | T230683 New syntax for multiline list items / talk page comments | |||
Open | None | T114432 [RFC] Heredoc arguments for templates (aka "hygienic" or "long" arguments) | |||
Open | None | T246960 Publish Technical RfC: new syntax for multi-line list items/talk page comments | |||
Resolved | ppelberg | T256694 Add RfC link to "switching disabled" exception message | |||
Invalid | • Whatamidoing-WMF | T258850 Make volunteer stakeholders aware of RfC for implementing new syntax for multi-line comments | |||
Open | None | T256324 References may disappear in DiscussionTools when switching from visual to wikitext (or saving) | |||
Open | None | T317352 Remove switching restrictions |
Event Timeline
As the final step of the Trial, I am interested to see the outcome of the software for converting all of the the Flow discussions back to Talk format. Thanx.
@Alsee: Could you please bring up general Flow questions / discussion on https://www.mediawiki.org/wiki/Talk:Flow as this Phabricator task is specifically about removing Flow from enwp's Wikipedia talk:WikiProject Breakfast. Thanks for your understanding!
It's a completely valid point here. If this removal is going to take place, it's going to affect real editors' content, and assurances need to be made as to how that's going to happen. There were two possible outcomes for the trial: either Flow would be accepted and retained, or declined and removed. Both contingencies should have been planned for.
A converttotext.php script exists, but needs some updates. I'll update this thread next week, with more details on that, when normal work resumes (post devsummit/allhands).
We need to discuss as a team before we make any decisions regarding use of convertToText.php.
This is under active discussion. See https://en.wikipedia.org/w/index.php?title=Topic:Stn15z0u230zcbve&topic_showPostId=sw7pdpu97lrffids#flow-post-sw7pdpu97lrffids and https://en.wikipedia.org/wiki/Wikipedia:Administrators%27_noticeboard#Request_close_review_of_RFC_-_Remove_Flow_from_WikiProject_Breakfast.3F .
The close was challenged, reviewed, and confirmed as correct: https://en.wikipedia.org/w/index.php?title=Wikipedia%3AAdministrators%27_noticeboard&type=revision&diff=699373873&oldid=699336258
Consensus to end Flow Trial at EN:WikiProject_Breakfast.
The script to export the structured Flow board to create an unstructured wikitext page is being updated and checked. The WikiProject Breakfast talk page will be switched over once that is ready. The existing Flow page will be moved to a subpage and protected, for detailed attribution purposes. Apologies that it will take longer than the 24hours stated 2 years ago.
@Quiddity, could you clarify the "detailed attribution" issue?
Ideally the conversion would use a series of synthetic edits to properly recreate the full history (as discussed in T96301). That idea appears to have been dropped because of the work involved and the (hopefully) limited use this converter is going to get. I'm willing to accept the current converter as adequate for the current limited use.
Are you saying that the WMF is unable to fully rollback this Flow trial? Are you saying there would be some legal issue if the archived Flow page were to be nominated for speedy deletion?
@Alsee The change back to wikitext contentmodel is as originally described. (Standard disclaimer for this is not legal advice) As with all pages, the history retained within the deleted page is sufficient for complete attribution. The recommendation to leave the Flow page visible, is just a recommendation. It would make comparison easier, and attribution more detailed. We were planning on creating the conversion page, moving the Flow page, and then let the Enwiki admins carry out the protection or deletion of the Flow page.
@Quiddity
Bug report: The Edit Description link disappeared from at https://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Breakfast/Flow_archive
I was trying to place a deletion tag on it, per the discussion above. I'll post on Admin Noticeboard.
My description of the bug was inaccurate because the bugs here themselves created confusion, and because Quiddity said in his earlier comment that the WMF was not going to be applying protection to the page.
Bug: The page history does not contain any entry for Page Protection. (I specifically checked for this before posting here, and this is why I concluded it wasn't a Protected-Page issue.) There's no indication anywhere that the page is protected.
Bug: There are still a links to post new threads, post a new replies, and to edit existing comments. Those links still open the editor, with no indication that the page is protected.
Bug: Clicking save in any of the above cases throws up a completely mangled error message.
Bug: When an Admin post on the page, they are given no warning that they are editing a Fully Protected page.
Possible Bug(?) I not an Admin so I can't check: Does the Edit Description link show up for Admins? It's definitely a bug if Admins can't Edit Description.
My apologies for that.
Bug: The page history does not contain any entry for Page Protection. (I specifically checked for this before posting here, and this is why I concluded it wasn't a Protected-Page issue.) There's no indication anywhere that the page is protected.
Looks like a regression. Filed as T127770: Log entries missing from Flow history pages
Bug: There are still a links to post new threads, post a new replies, and to edit existing comments. Those links still open the editor, with no indication that the page is protected.
Bug: Clicking save in any of the above cases throws up a completely mangled error message.
Covered by the above (which might need to be split into 1 or more sub-tasks).
Bug: When an Admin post on the page, they are given no warning that they are editing a Fully Protected page.
This is T108762: Notify users who are editing protected flow content.
Possible Bug(?) I not an Admin so I can't check: Does the Edit Description link show up for Admins? It's definitely a bug if Admins can't Edit Description.
It does show up.
Thank you for the details.