Summary: we'll convert some LiquidThreads conversations on mediawiki.org into Flow boards on test2wiki. The real move off LQT depends on changing how Flow pages are enabled, which has further dependencies.
Danny Horn, Erik Bernhardson, quiddity, and I met to talk about next steps in moving off LiquidThreads, which is deployed on 13 wikis. We will eventually convert all their LQT pages and threads to Flow boards and topics.
There are inter-dependencies:
We would need to enable Flow on 8 new wikis in order to convert all those LQT pages. (We would probably leave wikimania2010wiki as is.) Our initial focus will be mediawiki.org.
Kill LQT on mediawiki.org means 1,500 pages become Flow boards -> that's impractical to manage with the current PHP FlowOccupyPages variable So we need to replace it with a Special page to enable/disable Flow. -> which depends on *Bug 49193* https://bugzilla.wikimedia.org/show_bug.cgi?id=49193 - "Add ContentHandler columns to Wikimedia wikis, and set $wgContentHandlerUseDB = true" -> which hasn't completed and is blocked by bug 70901
We have a patch that replaces FlowOccupyPages with a bare-bones Special page to change a page between wiki text and Flow board. Eventually enabling Flow on a page is going to be a wiki administrative function, a big change that's a win for decentralization and local decision-making. We would restrict this Special page to Flow team on mediawiki.org at first, but there would be pushback if we do this on other wikis.
As Andrew Werdna suggested, the Special page would eventually handle the conversion from an LQT page to Flow, and if you disable Flow it would convert the Flow board into wikitext. Lots to do.
In the interim we are going to focus on the script that converts a LQT page into a Flow board. We need to show this to people who will be affected by the change from LQT to Flow.
TODO: change current script to target a LQT page on mediawiki.org and convert it into Flow boards and topics on test2wiki, without changing the original. (We'll write this conversion script so it can eventually be called from the Special page to enable Flow.)
We'll create a "Test Zero" LQT page with Flow team members participating, and convert that. Then we'll convert a few actual LQT pages from mw.org onto test2wiki.
Notes on the conversion script: * It'll produce weird results if run multiple times on the same LQT page. * Not sure what happens to multiple thread edits. * Conversion needs to add the converted Flow board and topics to the watchlists of users wwho were watching the LQT page and threads. * Conversion will create redirects for common LQT URLs, but not e.g. the Summary namespace URLs. * Conversion itself will not generate Echo notifications and e-mails
quiddity mentioned the following as likely concerns of LQT users after the conversion to Flow: * LQT TOC (we should have a nice Flow TOC soon!) * Splitting and merging threads: * Moving threads to a new Talk page. * User-friendly Topic names, e.g. Thread:Extension_talk:Flow/Appearance/reply_(6) becomes Topic:Rylnpvcpshj9n30s#flow-post-rylnvqsqmjnng558
Project planning goes on in < https://trello.com/c/0VP635yr/683-tracking-when-should-we-kill-lqt%3E and related cards.
Cheers.
Will permalinks to old conversations survive conversion to Flow?
On Fri, Sep 19, 2014 at 2:39 PM, S Page spage@wikimedia.org wrote:
Summary: we'll convert some LiquidThreads conversations on mediawiki.org into Flow boards on test2wiki. The real move off LQT depends on changing how Flow pages are enabled, which has further dependencies.
Danny Horn, Erik Bernhardson, quiddity, and I met to talk about next steps in moving off LiquidThreads, which is deployed on 13 wikis. We will eventually convert all their LQT pages and threads to Flow boards and topics.
There are inter-dependencies:
We would need to enable Flow on 8 new wikis in order to convert all those LQT pages. (We would probably leave wikimania2010wiki as is.) Our initial focus will be mediawiki.org.
Kill LQT on mediawiki.org means 1,500 pages become Flow boards -> that's impractical to manage with the current PHP FlowOccupyPages variable So we need to replace it with a Special page to enable/disable Flow. -> which depends on Bug 49193 - "Add ContentHandler columns to Wikimedia wikis, and set $wgContentHandlerUseDB = true" -> which hasn't completed and is blocked by bug 70901
We have a patch that replaces FlowOccupyPages with a bare-bones Special page to change a page between wiki text and Flow board. Eventually enabling Flow on a page is going to be a wiki administrative function, a big change that's a win for decentralization and local decision-making. We would restrict this Special page to Flow team on mediawiki.org at first, but there would be pushback if we do this on other wikis.
As Andrew Werdna suggested, the Special page would eventually handle the conversion from an LQT page to Flow, and if you disable Flow it would convert the Flow board into wikitext. Lots to do.
In the interim we are going to focus on the script that converts a LQT page into a Flow board. We need to show this to people who will be affected by the change from LQT to Flow.
TODO: change current script to target a LQT page on mediawiki.org and convert it into Flow boards and topics on test2wiki, without changing the original. (We'll write this conversion script so it can eventually be called from the Special page to enable Flow.)
We'll create a "Test Zero" LQT page with Flow team members participating, and convert that. Then we'll convert a few actual LQT pages from mw.org onto test2wiki.
Notes on the conversion script:
- It'll produce weird results if run multiple times on the same LQT page.
- Not sure what happens to multiple thread edits.
- Conversion needs to add the converted Flow board and topics to the
watchlists of users wwho were watching the LQT page and threads.
- Conversion will create redirects for common LQT URLs, but not e.g. the
Summary namespace URLs.
- Conversion itself will not generate Echo notifications and e-mails
quiddity mentioned the following as likely concerns of LQT users after the conversion to Flow:
- LQT TOC (we should have a nice Flow TOC soon!)
- Splitting and merging threads:
- Moving threads to a new Talk page.
- User-friendly Topic names, e.g.
Thread:Extension_talk:Flow/Appearance/reply_(6) becomes Topic:Rylnpvcpshj9n30s#flow-post-rylnvqsqmjnng558
Project planning goes on in https://trello.com/c/0VP635yr/683-tracking-when-should-we-kill-lqt and related cards.
Cheers.
=S Page Features engineer
EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee
/me adds emphasis that this is all going to occur Slowwwwwly and patiently, starting off very small, with much testing, and many (steadily louder) requests for feedback on the test results.
@ James Salsman: Yes for thread links. No for Summary-namespace links. (per:
...
- Conversion will create redirects for common LQT URLs, but not e.g. the
Summary namespace URLs. ...
On Fri, Sep 19, 2014 at 5:39 PM, S Page spage@wikimedia.org wrote:
Summary: we'll convert some LiquidThreads conversations on mediawiki.org into Flow boards on test2wiki. The real move off LQT depends on changing how Flow pages are enabled, which has further dependencies.
Danny Horn, Erik Bernhardson, quiddity, and I met to talk about next steps in moving off LiquidThreads, which is deployed on 13 wikis. We will eventually convert all their LQT pages and threads to Flow boards and topics.
There are inter-dependencies:
We would need to enable Flow on 8 new wikis in order to convert all those LQT pages. (We would probably leave wikimania2010wiki as is.) Our initial focus will be mediawiki.org.
Kill LQT on mediawiki.org means 1,500 pages become Flow boards -> that's impractical to manage with the current PHP FlowOccupyPages variable So we need to replace it with a Special page to enable/disable Flow. -> which depends on *Bug 49193* https://bugzilla.wikimedia.org/show_bug.cgi?id=49193 - "Add ContentHandler columns to Wikimedia wikis, and set $wgContentHandlerUseDB = true" -> which hasn't completed and is blocked by bug 70901
We have a patch that replaces FlowOccupyPages with a bare-bones Special page to change a page between wiki text and Flow board. Eventually enabling Flow on a page is going to be a wiki administrative function, a big change that's a win for decentralization and local decision-making. We would restrict this Special page to Flow team on mediawiki.org at first, but there would be pushback if we do this on other wikis.
As Andrew Werdna suggested, the Special page would eventually handle the conversion from an LQT page to Flow, and if you disable Flow it would convert the Flow board into wikitext. Lots to do.
In the interim we are going to focus on the script that converts a LQT page into a Flow board. We need to show this to people who will be affected by the change from LQT to Flow.
TODO: change current script to target a LQT page on mediawiki.org and convert it into Flow boards and topics on test2wiki, without changing the original. (We'll write this conversion script so it can eventually be called from the Special page to enable Flow.)
We'll create a "Test Zero" LQT page with Flow team members participating, and convert that. Then we'll convert a few actual LQT pages from mw.org onto test2wiki.
Notes on the conversion script:
- It'll produce weird results if run multiple times on the same LQT page.
- Not sure what happens to multiple thread edits.
- Conversion needs to add the converted Flow board and topics to the
watchlists of users wwho were watching the LQT page and threads.
- Conversion will create redirects for common LQT URLs, but not e.g. the
Summary namespace URLs.
- Conversion itself will not generate Echo notifications and e-mails
quiddity mentioned the following as likely concerns of LQT users after the conversion to Flow:
- LQT TOC (we should have a nice Flow TOC soon!)
- Splitting and merging threads:
- Moving threads to a new Talk page.
- User-friendly Topic names, e.g.
Thread:Extension_talk:Flow/Appearance/reply_(6) becomes Topic:Rylnpvcpshj9n30s#flow-post-rylnvqsqmjnng558
Project planning goes on in < https://trello.com/c/0VP635yr/683-tracking-when-should-we-kill-lqt%3E and related cards.
Cheers.
=S Page Features engineer
EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee
On Fri, Sep 19, 2014 at 5:55 PM, Nick Wilson (Quiddity) < nwilson@wikimedia.org> wrote:
/me adds emphasis that this is all going to occur Slowwwwwly and patiently, starting off very small, with much testing, and many (steadily louder) requests for feedback on the test results.
Yes. We want to communicate plans, and it feels silly to begin every sentence "We'll probably, ... " "We think...", "Most likely...". The truth is you learn by doing and plans change accordingly
On Fri, Sep 19, 2014 at 5:48 PM, James Salsman jsalsman@gmail.com wrote:
Will permalinks to old conversations survive conversion to Flow?
@ James Salsman: Yes for thread links. No for Summary-namespace links.
I wonder how often people link to a particular reply in a LQT thread, e.g. https://www.mediawiki.org/wiki/Thread:Extension_talk:BreadCrumbs/Preferences...)
I assume people link to threads, e.g. https://www.mediawiki.org/wiki/Summary:Extension_talk:BreadCrumbs/Preference...
It seems farfetched that someone would link to a thread summary e.g. https://www.mediawiki.org/wiki/Summary:Extension_talk:BreadCrumbs/Preference... ; just link to the thread and visitors see its summary, if any.
-- =S Page Features engineer
Just to be clear, the transition to Flow won't break wikitext discussion permalinks, either, will it?
There are a lot of things that are possible on talk pages with wikitext that I know I can't do with LT (one time someone insisted on a biased and inaccurate summary.... years ago) and since Flow is more or less still up in the air as to the details, I am hoping there is more than one way to find out about this than waiting for time to tell.
On Fri, Sep 19, 2014 at 3:54 PM, S Page spage@wikimedia.org wrote:
On Fri, Sep 19, 2014 at 5:55 PM, Nick Wilson (Quiddity) nwilson@wikimedia.org wrote:
/me adds emphasis that this is all going to occur Slowwwwwly and patiently, starting off very small, with much testing, and many (steadily louder) requests for feedback on the test results.
Yes. We want to communicate plans, and it feels silly to begin every sentence "We'll probably, ... " "We think...", "Most likely...". The truth is you learn by doing and plans change accordingly
On Fri, Sep 19, 2014 at 5:48 PM, James Salsman jsalsman@gmail.com wrote: Will permalinks to old conversations survive conversion to Flow?
@ James Salsman: Yes for thread links. No for Summary-namespace links.
I wonder how often people link to a particular reply in a LQT thread, e.g. https://www.mediawiki.org/wiki/Thread:Extension_talk:BreadCrumbs/Preferences...)
I assume people link to threads, e.g. https://www.mediawiki.org/wiki/Summary:Extension_talk:BreadCrumbs/Preference...
It seems farfetched that someone would link to a thread summary e.g. https://www.mediawiki.org/wiki/Summary:Extension_talk:BreadCrumbs/Preference... ; just link to the thread and visitors see its summary, if any.
-- =S Page Features engineer
EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee
On Fri, Sep 19, 2014 at 7:03 PM, James Salsman jsalsman@gmail.com wrote:
Just to be clear, the transition to Flow won't break wikitext discussion permalinks, either, will it?
You'll have to be more specific. For example, https://www.mediawiki.org/wiki/Talk:Beta_Features/Nearby_Pages remained the same wikilink and URL after becoming a Flow board. What we typically do when converting a talk page to Flow is move the existing page to a /Archive subpage that remains wikitext, and link to it from the Flow board heading. See the /Archive_1 subpage of the page above. Section links break but that seems no worse than what happens with current talk pages when archiving old sections.
There are a lot of things that are possible on talk pages with wikitext that I know I can't do with LT (one time someone insisted on a biased and inaccurate summary.... years ago) and since Flow is more or less still up in the air as to the details, I am hoping there is more than one way to find out about this than waiting for time to tell.
If you wonder if something works in Flow, try it at https://www.mediawiki.org/wiki/Talk:Sandbox , and discuss issues at https://www.mediawiki.org/wiki/Talk:Flow Many are covered at https://www.mediawiki.org/wiki/Flow/FAQ
Regards, -- =S Page Features engineer
On 09/19/2014 10:03 PM, James Salsman wrote:
Just to be clear, the transition to Flow won't break wikitext discussion permalinks, either, will it?
If you mean true permalinks like https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28technic... , I don't think it will break.
S said the wikitext pages are moved to an archive title, which means the revision still exists (it's not deleted), so I think it will be accessible via oldid.
Matt Flaschen
On 9/19/14, 5:39 PM, S Page wrote:
There are inter-dependencies:
We would need to enable Flow on 8 new wikis in order to convert all those LQT pages. (We would probably leave wikimania2010wiki as is.)
I think our eventual goal should be to remove LQT from the cluster, which means you have to convert all wikis, even closed ones like wm2010.
Our initial focus will be mediawiki.org http://mediawiki.org.
Kill LQT on mediawiki.org http://mediawiki.org means 1,500 pages become Flow boards -> that's impractical to manage with the current PHP FlowOccupyPages variable So we need to replace it with a Special page to enable/disable Flow. -> which depends on *Bug 49193* https://bugzilla.wikimedia.org/show_bug.cgi?id=49193 -"Add ContentHandler columns to Wikimedia wikis, and set $wgContentHandlerUseDB = true" -> which hasn't completed and is blocked by bug 70901
Please also add https://bugzilla.wikimedia.org/show_bug.cgi?id=71082 to the dependency list. I'll try and get it done early next week, poke me if I don't.
-- Kunal / Legoktm
Yey!
Just to confirm, you have our fullest support in enabling Flow and convering all LQT threads to flow boards on se.wikimedia,org. We have already been talking to request that so we are really looking forward to it.
*Med vänliga hälsningar,Jan Ainali*
Verksamhetschef, Wikimedia Sverige http://wikimedia.se 0729 - 67 29 48
*Tänk dig en värld där varje människa har fri tillgång till mänsklighetens samlade kunskap. Det är det vi gör.* Bli medlem. http://blimedlem.wikimedia.se
2014-09-20 2:39 GMT+02:00 S Page spage@wikimedia.org:
Summary: we'll convert some LiquidThreads conversations on mediawiki.org into Flow boards on test2wiki. The real move off LQT depends on changing how Flow pages are enabled, which has further dependencies.
Danny Horn, Erik Bernhardson, quiddity, and I met to talk about next steps in moving off LiquidThreads, which is deployed on 13 wikis. We will eventually convert all their LQT pages and threads to Flow boards and topics.
There are inter-dependencies:
We would need to enable Flow on 8 new wikis in order to convert all those LQT pages. (We would probably leave wikimania2010wiki as is.) Our initial focus will be mediawiki.org.
Kill LQT on mediawiki.org means 1,500 pages become Flow boards -> that's impractical to manage with the current PHP FlowOccupyPages variable So we need to replace it with a Special page to enable/disable Flow. -> which depends on *Bug 49193* https://bugzilla.wikimedia.org/show_bug.cgi?id=49193 - "Add ContentHandler columns to Wikimedia wikis, and set $wgContentHandlerUseDB = true" -> which hasn't completed and is blocked by bug 70901
We have a patch that replaces FlowOccupyPages with a bare-bones Special page to change a page between wiki text and Flow board. Eventually enabling Flow on a page is going to be a wiki administrative function, a big change that's a win for decentralization and local decision-making. We would restrict this Special page to Flow team on mediawiki.org at first, but there would be pushback if we do this on other wikis.
As Andrew Werdna suggested, the Special page would eventually handle the conversion from an LQT page to Flow, and if you disable Flow it would convert the Flow board into wikitext. Lots to do.
In the interim we are going to focus on the script that converts a LQT page into a Flow board. We need to show this to people who will be affected by the change from LQT to Flow.
TODO: change current script to target a LQT page on mediawiki.org and convert it into Flow boards and topics on test2wiki, without changing the original. (We'll write this conversion script so it can eventually be called from the Special page to enable Flow.)
We'll create a "Test Zero" LQT page with Flow team members participating, and convert that. Then we'll convert a few actual LQT pages from mw.org onto test2wiki.
Notes on the conversion script:
- It'll produce weird results if run multiple times on the same LQT page.
- Not sure what happens to multiple thread edits.
- Conversion needs to add the converted Flow board and topics to the
watchlists of users wwho were watching the LQT page and threads.
- Conversion will create redirects for common LQT URLs, but not e.g. the
Summary namespace URLs.
- Conversion itself will not generate Echo notifications and e-mails
quiddity mentioned the following as likely concerns of LQT users after the conversion to Flow:
- LQT TOC (we should have a nice Flow TOC soon!)
- Splitting and merging threads:
- Moving threads to a new Talk page.
- User-friendly Topic names, e.g.
Thread:Extension_talk:Flow/Appearance/reply_(6) becomes Topic:Rylnpvcpshj9n30s#flow-post-rylnvqsqmjnng558
Project planning goes on in < https://trello.com/c/0VP635yr/683-tracking-when-should-we-kill-lqt%3E and related cards.
Cheers.
=S Page Features engineer
EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee
This is very very very exciting. I'm glad this is something you are doing. Getting Flow in front of more people is going to make the product even better!
On Fri, Sep 19, 2014 at 11:21 PM, Jan Ainali jan.ainali@wikimedia.se wrote:
Yey!
Just to confirm, you have our fullest support in enabling Flow and convering all LQT threads to flow boards on se.wikimedia,org. We have already been talking to request that so we are really looking forward to it.
*Med vänliga hälsningar,Jan Ainali*
Verksamhetschef, Wikimedia Sverige http://wikimedia.se 0729 - 67 29 48
*Tänk dig en värld där varje människa har fri tillgång till mänsklighetens samlade kunskap. Det är det vi gör.* Bli medlem. http://blimedlem.wikimedia.se
2014-09-20 2:39 GMT+02:00 S Page spage@wikimedia.org:
Summary: we'll convert some LiquidThreads conversations on mediawiki.org into Flow boards on test2wiki. The real move off LQT depends on changing how Flow pages are enabled, which has further dependencies.
Danny Horn, Erik Bernhardson, quiddity, and I met to talk about next steps in moving off LiquidThreads, which is deployed on 13 wikis. We will eventually convert all their LQT pages and threads to Flow boards and topics.
There are inter-dependencies:
We would need to enable Flow on 8 new wikis in order to convert all those LQT pages. (We would probably leave wikimania2010wiki as is.) Our initial focus will be mediawiki.org.
Kill LQT on mediawiki.org means 1,500 pages become Flow boards -> that's impractical to manage with the current PHP FlowOccupyPages variable So we need to replace it with a Special page to enable/disable Flow. -> which depends on *Bug 49193* https://bugzilla.wikimedia.org/show_bug.cgi?id=49193 - "Add ContentHandler columns to Wikimedia wikis, and set $wgContentHandlerUseDB = true" -> which hasn't completed and is blocked by bug 70901
We have a patch that replaces FlowOccupyPages with a bare-bones Special page to change a page between wiki text and Flow board. Eventually enabling Flow on a page is going to be a wiki administrative function, a big change that's a win for decentralization and local decision-making. We would restrict this Special page to Flow team on mediawiki.org at first, but there would be pushback if we do this on other wikis.
As Andrew Werdna suggested, the Special page would eventually handle the conversion from an LQT page to Flow, and if you disable Flow it would convert the Flow board into wikitext. Lots to do.
In the interim we are going to focus on the script that converts a LQT page into a Flow board. We need to show this to people who will be affected by the change from LQT to Flow.
TODO: change current script to target a LQT page on mediawiki.org and convert it into Flow boards and topics on test2wiki, without changing the original. (We'll write this conversion script so it can eventually be called from the Special page to enable Flow.)
We'll create a "Test Zero" LQT page with Flow team members participating, and convert that. Then we'll convert a few actual LQT pages from mw.org onto test2wiki.
Notes on the conversion script:
- It'll produce weird results if run multiple times on the same LQT page.
- Not sure what happens to multiple thread edits.
- Conversion needs to add the converted Flow board and topics to the
watchlists of users wwho were watching the LQT page and threads.
- Conversion will create redirects for common LQT URLs, but not e.g. the
Summary namespace URLs.
- Conversion itself will not generate Echo notifications and e-mails
quiddity mentioned the following as likely concerns of LQT users after the conversion to Flow:
- LQT TOC (we should have a nice Flow TOC soon!)
- Splitting and merging threads:
- Moving threads to a new Talk page.
- User-friendly Topic names, e.g.
Thread:Extension_talk:Flow/Appearance/reply_(6) becomes Topic:Rylnpvcpshj9n30s#flow-post-rylnvqsqmjnng558
Project planning goes on in < https://trello.com/c/0VP635yr/683-tracking-when-should-we-kill-lqt%3E and related cards.
Cheers.
=S Page Features engineer
EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee
EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee
Jon, does "very very very" mean that you have usability test results supporting your opinion?
On Mon, Sep 22, 2014 at 9:49 AM, Jon Robson jrobson@wikimedia.org wrote:
This is very very very exciting. I'm glad this is something you are doing. Getting Flow in front of more people is going to make the product even better!
On Fri, Sep 19, 2014 at 11:21 PM, Jan Ainali jan.ainali@wikimedia.se wrote:
Yey!
Just to confirm, you have our fullest support in enabling Flow and convering all LQT threads to flow boards on se.wikimedia,org. We have already been talking to request that so we are really looking forward to it.
*Med vänliga hälsningar,Jan Ainali*
Verksamhetschef, Wikimedia Sverige http://wikimedia.se 0729 - 67 29 48
*Tänk dig en värld där varje människa har fri tillgång till mänsklighetens samlade kunskap. Det är det vi gör.* Bli medlem. http://blimedlem.wikimedia.se
2014-09-20 2:39 GMT+02:00 S Page spage@wikimedia.org:
Summary: we'll convert some LiquidThreads conversations on mediawiki.org into Flow boards on test2wiki. The real move off LQT depends on changing how Flow pages are enabled, which has further dependencies.
Danny Horn, Erik Bernhardson, quiddity, and I met to talk about next steps in moving off LiquidThreads, which is deployed on 13 wikis. We will eventually convert all their LQT pages and threads to Flow boards and topics.
There are inter-dependencies:
We would need to enable Flow on 8 new wikis in order to convert all those LQT pages. (We would probably leave wikimania2010wiki as is.) Our initial focus will be mediawiki.org.
Kill LQT on mediawiki.org means 1,500 pages become Flow boards -> that's impractical to manage with the current PHP FlowOccupyPages variable So we need to replace it with a Special page to enable/disable Flow. -> which depends on *Bug 49193* https://bugzilla.wikimedia.org/show_bug.cgi?id=49193 - "Add ContentHandler columns to Wikimedia wikis, and set $wgContentHandlerUseDB = true" -> which hasn't completed and is blocked by bug 70901
We have a patch that replaces FlowOccupyPages with a bare-bones Special page to change a page between wiki text and Flow board. Eventually enabling Flow on a page is going to be a wiki administrative function, a big change that's a win for decentralization and local decision-making. We would restrict this Special page to Flow team on mediawiki.org at first, but there would be pushback if we do this on other wikis.
As Andrew Werdna suggested, the Special page would eventually handle the conversion from an LQT page to Flow, and if you disable Flow it would convert the Flow board into wikitext. Lots to do.
In the interim we are going to focus on the script that converts a LQT page into a Flow board. We need to show this to people who will be affected by the change from LQT to Flow.
TODO: change current script to target a LQT page on mediawiki.org and convert it into Flow boards and topics on test2wiki, without changing the original. (We'll write this conversion script so it can eventually be called from the Special page to enable Flow.)
We'll create a "Test Zero" LQT page with Flow team members participating, and convert that. Then we'll convert a few actual LQT pages from mw.org onto test2wiki.
Notes on the conversion script:
- It'll produce weird results if run multiple times on the same LQT
page.
- Not sure what happens to multiple thread edits.
- Conversion needs to add the converted Flow board and topics to the
watchlists of users wwho were watching the LQT page and threads.
- Conversion will create redirects for common LQT URLs, but not e.g. the
Summary namespace URLs.
- Conversion itself will not generate Echo notifications and e-mails
quiddity mentioned the following as likely concerns of LQT users after the conversion to Flow:
- LQT TOC (we should have a nice Flow TOC soon!)
- Splitting and merging threads:
- Moving threads to a new Talk page.
- User-friendly Topic names, e.g.
Thread:Extension_talk:Flow/Appearance/reply_(6) becomes Topic:Rylnpvcpshj9n30s#flow-post-rylnvqsqmjnng558
Project planning goes on in < https://trello.com/c/0VP635yr/683-tracking-when-should-we-kill-lqt%3E and related cards.
Cheers.
=S Page Features engineer
EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee
EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee
EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee
On 09/22/2014 03:49 PM, Jon Robson wrote:
This is very very very exciting. I'm glad this is something you are doing. Getting Flow in front of more people is going to make the product even better!
I agree. It's also important (and good) that we're providing a migration path for an extension we (meaning the WMF) (among other contributors) previously worked on.
Matt Flaschen