| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | None | T174087 FY2017/18 Program 3: Addressing technical debt | |||
| Resolved | Jrbranaa | T174088 FY2017/18 Program 3 Outcome 1: The amount of orphaned code that is running Wikimedia “production” services is reduced. | |||
| Resolved | Jrbranaa | T174090 FY2017/18 Program 3 Outcome 1 Objective 1: Define a set of code stewardship levels (from high to low expectations) |
Event Timeline
Added first pass changes regarding code stewardship.
New:
Describes the areas of stewardship, what it means to be a steward, and a base set of SLAs for both Reviews and Tasks/Bugs. I departed from the Reading group's approach a little in that I defined SLAs that are based on Priority - "UnBreak Now" should have a shorter SLA than a "Low".
Changed:
Renamed column "Responsible Wikimedia Team" to "Stewards"
Added brief section describing stewardship and referring to the Code_Stewardship page.
Currently the reading groups model is to define different SLAs for different components. I think this is a practical approach, but I'm not sure that it's too friendly to outside contributors. From what I can tell, many of the SLAs are based on whether the component is actively being developed. If possible, it would be more contributor friendly if by and large all actively developed components had the same SLA and all inactive components had the same SLA. I'm mostly thinking out-loud on this though.
Changes to Developers/Maintainers page where reverted as they referred to an "in draft" page regarding stewardship, which I totally understand.
The sticky point I believe it the commitment to "SLAs". This could be moved out of the steward page and into the discussion page for starters.
This is pretty much done, just going to work with Victoria and Toby regarding communication.