Sometimes a talk subpage contains actual discussion of its related article. so it should become a Flow board. Other times it just holds related information for its parent discussion page, so it should remain a regular wikitext page.
Example: the conversion of a namespace to Flow on OfficeWiki did not touch the subpage https://office.wikimedia.org/wiki/OfficeWiki_talk:WikiProject_OfficeWiki/guidingprinciples
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T76682 Flow: archiving existing wikitext pages (tracking) | ||
| Resolved | EBernhardson | T76772 How to handle subpages during talk page conversion to Flow |
If we determine that a Flow should be enabled on a subpage, then this is blocked by T76197.
We agreed the test for whether a subpage should be Flowified is if there's an article corresponding to it. For example, mw:Talk:Mobile_web/Team should be a Flow board because it's the talk page for a real page. But en:Talk:Bacon/Draft_3 should not.
So, convertNamespaceFromWikitext.php should perform this check, and output either
Subpage found, Foo_talk:Bar/Baz, no corresponding article so not converting to Flow.
or
Subpage found, Foo_talk:Buzz/Scratch, has corresponding article so converting to Flow.
Sounds reasonable? AIUI converting subpages to Flow is blocked until we address T76778, but the warning is still useful.
Can I ask how specifically are we converting it to a Flow board? Where does the original content go? Thanks.
Change 179337 had a related patch set uploaded (by EBernhardson):
Allow subpage conversion under limited circumstances
( Spage: I disagree with the process documented on the wiki page you linked. Please discuss here: https://phabricator.wikimedia.org/T76682 ) Discussed on IRC. Looks like we agree there (and this current task is needed just not to lose the data — for some wikis which feel ready to start Flowing without converting old discussions.)
Change 179337 merged by jenkins-bot:
Allow subpage conversion under limited circumstances