This task involves the work of converging on a sequence and timeline in which the Editing Team, in collaboration with volunteers and projects, will undeploy StructuredDiscussions (Flow) and LiquidThreads (LQT). We will use the term "Flow" for both features, unless noted.
Defining the above will enable us to do things like:
- Decide whether new Flow-related issues warrant resolution in the time between when they emerge and when Flow will be undeployed?
- Coordinate with other teams to ensure the deployment plans they are making are not complicated/put at risk by Flow's deployment state
- E.g. T370322
Undeployment sequence
| Step | Description | Completion timing: Phase 0 wikis | Completion timing: Phase 1 wikis | Completion timing: Phase 2 wikis |
|---|---|---|---|---|
| Step #1 | Write script to automatically move talk pages | ✅ | ✅ | ✅ |
| Step #2 | Inform volunteers/communities of deprecation plan (w/ dates) | ✅ | ||
| Step #3 | Volunteers manually move Flow boards to sub-pages | ✅ | ||
| Step #4 | Run migration script (T376749) | ✅ | ||
| Step #5 | Fix any migration issues | ✅ | ||
| Step #6 | Set all Flow boards to read-only | ✅ | ||
| Step #7 | Convert content of all archived Flow boards to wikitext (T377051) | |||
| Step 8 | Remove Flow code and related data | |||
See more here: https://miro.com/app/board/uXjVKGsM740=/
Done
- A plan that includes the following information
- All of the wikis where Flow/StructuredDiscussions is currently active
- For each wiki we'll have identified above the dates we're proposing for Flow to be:
- Set into a read-only state
- All Flow boards to be moved to sub-pages
- Flow to be undeployed