 | This page isoutdated. This work is no longer being promoted. If you have checked or updated this page and found the content to be suitable, please remove this notice. See thetalk page for a possible discussion on this. |
TheTechnical Debt Program is being developed to help the Foundation and the broader community better manage technical debt. This article's purpose is to help document a process by which the Foundation and community can:
For more information about Technical Debt in MediaWiki, please see theTechnical Debt article.
The Technical Debt Engagement Model describes how the Program will work with the various stakeholders within the Wikimedia Foundation to establish pragmatic approaches to address existing Technical Debt as well as put in place measures to avoid the accrual of unintentional or otherwise unnecessary Technical Debt.
Please seeTechnical Debt Engagement Model for more information.
The Technical Debt Program's Awareness Campaign is focused on the sharing of information about the various aspects of Technical Debt. The Awareness Campaign will bring timely and relevant information about the state of our Technical Debt, current efforts to reduce the backlog, as well as broader Code Health issues.
Please seeTechnical Debt Awareness Campaign for more information.
The Technical Debt Management Process encompasses two distinct activities - managing efforts related to backlog reduction and decision making regarding the accumulation of new Technical Debt. Please seeTechnical Debt Management Process for more information.
| Sponsor: | Victoria Coleman (CTO, Technology Group) |
|---|---|
| Responsible: | Greg Grossmeier (Manager, Release Engineering) |
| Accountable: | Jean-Rene Branaa (Quality Program Manager, Release Engineering) |
| Consulted: | TechCom,Code Health Group, Technology Management, Engineering Managers,Technical Debt SIG |
| Informed: | Technical Community (volunteers and staff) |
| Title | Due | Phab Task | Status |
|---|---|---|---|
| Program 3: Outcome 1: Objective 1: Define a set of code stewardship levels (from high to low expectations) See:Code Stewardship | EOQ2 | T174090 |  Done |
| Program 3: Outcome 1: Objective 2: Identify and find stewards for high-priority/high use code segment orphans | EOQ3 | T174091 | Done |
| Program 3: Outcome 2: Objective 1: Define a “Technical Debt Project Manager” role that regularly communicates with all Foundation engineering teams regarding their technical debt | EOQ2 | T174093 | Done |
| Program 3: Outcome 2: Objective 2: Define and implement a process to regularly address technical debt across the Foundation | EOQ3 | T174095 | Done |
Technical Debt Program
|