Topic on Talk:Structured Discussions/Flow

Can we ever expect to have a migration from LQT 2 to Flow, so that we can assume, that Flow is LQT 4.0 and not just some kind of incompatible never ready software that's only use-case is to upset users?

We'll be working on a conversion script that turns LQT discussions into Flow topics, in late 2014.

—Flow#Why not use LiquidThreads?

They're working on that migration script right now. A large quantity of the work is done, and it's currently going through testing and edge-case discovery. Once it's had some more bug-fixes and polish, they'll be doing some public demonstrations of page-conversions, for wider feedback and analysis.

If you'd like to follow the details, see https://trello.com/c/6OqlxIYI/ for the product management notes, and https://gerrit.wikimedia.org/r/#/c/119243/ for the WIP code.

Are we still planning on moving existing classic talk pages?

To my understanding we just need to be able to migrate them as one post, with appropriate split functionality (I split a discussion in two, its history entry of one of them will say where I split it from, all history will remain in the oldest post and be linked).

I.e. I create topics "foo" and "bar" on a classic talk page which has archives. Then:

1. We move it to a single Flow board post titled "Migrated".
2. We move archives to single Flow board post titled "Archive 1", "Archive 2", etc.
3. Users split the discussions by hand.
4. For each thing they split out of the big post, the history says:

   Gryllida split Topic:43546554DSF from Topic:FDGFD34534

   Gryllida split Topic:FGH345 from Topic:FDGFD34534

5. Anyone who wants to see history will consult a post history which will, in its first edit, link to the original Topic:FDGFD34534 post (the oldest one on the corresponding page) which holds the whole talk page history from the classic talk page.
6. The end result is that all discussions are searchable, they are more or less correct headlines and proper TOC. Where people want to reply, they need to do some more splitting of a single thread into invididual messages.
7. All this functionality is not redundant, because a lot of this will be useful for refactoring Flow-enabled discussions in big RFCs.

I had raised all this at this topic but got completely ignored...

Sorry :(

I'm really looking forward to being able to refactor Flow topics, so that we can do things like move this tangent, into that other/original topic. Can we move the discussion there, so as not to bother DaSch and Klipe, and so that we keep it all in one place?

This should be on the roadmap really early as it makes migrating things from classic pages to Flow pages easier (and doable!).

I'm OK with it being discussed in the thread I linked. I copied my comment there.