|T76682 Flow: archiving existing wikitext pages (tracking)
|T76684 Flow board header wikitext created on officewiki during talk page migration is garbled
|T76685 Flow shouldn't take over redirected pages
|T76772 How to handle subpages during talk page conversion to Flow
|T78103 InvalidDataException on OfficeWiki history page (Unbreak Now)
|T78102 Flow-ified talk pages appear as redlinks even when the Flow board has content.
|T78105 Flow conversion assumes a talk page's namespace allows subpages
|T78111 Fix officewiki talk subpages that were archived but not Flow-enabled
|T101081 Algorithm to detect when the content above the first section needs to be archived and/or converted into Flow header
Why does the wiki page linked, https://www.mediawiki.org/wiki/Flow/Converting_talk_pages, completely ignore the discussion at https://www.mediawiki.org/wiki/Topic:S12prb6trf24nhkz ?
The discussion specifically raises some points regarding how to have the archives Flow-able:
- The archives pages should be migrated to Flow topics as whole posts.
- It should be possible to split topics and messages, indent them, and change author. Those interested in a particular section of an archive would cherry-pick it and structure it properly, and then talk.
- History would remain with one of the posts. All other splitted posts would have a first history entry linking to that post.
However, to my surprise, the wiki page linked in this task description suggests moving archives to some place outside of Flow, and does not depend on any tasks related to refactoring discussions. This ought to be fixed.
Yes, we still need to do it, but first we need to do T73197: Flow should support making actions as a bot and set rc_bot accordingly (now properly marked as a blocker of T78111: Fix officewiki talk subpages that were archived but not Flow-enabled), so @Quiddity can mark himself bot/flood.