Because {T235752} felt bumpy and more like "individuals try to remember random places".
Tagging as #Code-Stewardship-Reviews because trying to find existing docs, https://www.mediawiki.org/wiki/Sunsetting_Working_Group says it's been superseded by https://www.mediawiki.org/wiki/Code_stewardship_reviews which links to https://www.mediawiki.org/wiki/Technical_Debt_Program which hasn't seen updates since 2018.
Related:
* #Projects-Cleanup instructions in https://phabricator.wikimedia.org/project/profile/2829/
* https://www.mediawiki.org/wiki/Gerrit/Inactive_projects (probably outdated and superseded by Code Stewardship reviews by now?)
* Pages like https://www.mediawiki.org/wiki/Reading/Web/Sunsetting_a_project (there might be more)
* Tasks which have comments which cover some steps. See e.g. T235752#7368776, T235752#7399147, T235752#7399456, T235752#7404499.
This is different from archiving a codebase, that would be {T198059} (with e.g. {T292654} being affected)
---
= Tech Decision Forum template: =
== 1) WHAT? ==
==== Write your problem statement using layperson’s terminology. In one sentence, what is the problem or opportunity? ====
==== What does the future look like if this is achieved? ====
==== What happens if we do nothing? ====
== 2) WHY? ==
==== Identify the value(s) this problem/opportunity provides. Add links to relevant OKRs. ====
==== Rank values in order of importance and be explicit about who this benefits and where the value is. ====
| User Value/Organization Value | Objective it supports and How |
| 1. | |
| 2. | |
| 3. | |
| 4. | |
==== Why are you bringing this decision to the Technical Forum? What about the scope of this problem led you and your team to seek input across departments/organizations? ====
== 3) Technical Forum Chair Review ==