| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | srishakatux | T323302 Develop a set of practices that support high-impact tools and their maintainers. | |||
| Resolved | srishakatux | T323317 Initiate and strengthen connections with the community and other partners | |||
| Resolved | srishakatux | T333178 [Session] Best practices & ideas for implementing them for high-impact tools & their maintainers |
Event Timeline
Anybody knows if there are plans to update https://www.mediawiki.org/wiki/Wikimedia_Technical_Engagement/Practices_to_support_maintainers_and_high-impact_tools which has not seen any edits apart from four days in November 2022?
Sorry for the delayed response. I see the wiki page describing this project has been marked obsolete. I think that best represents the current reality of the project. This project has suffered from a loss of supporting teams, pivoted resources, and no space in the annual plan to prioritize. There is no clear home for the project and I understand it was not targeted for transition as it was a new / just launching effort. In addition, there are no resources now who are able to pick this work up.
All that said, I would encourage anyone interested in this topic to engage with SDS1 (https://meta.wikimedia.org/wiki/Talk:Wikimedia_Foundation_Annual_Plan/2023-2024/Product_%26_Technology/OKRs#SDS1:_Defining_essential_metrics) as similar efforts in defining and measuring essential metrics such as tool maintainers are present. See https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2023-2024/Product_%26_Technology/OKRs#Bucket_2:_Signals_&_Data_Services for other "signal" related OKRs.
Adding some context for those who came across this ticket after discussions at Wikimania 2023 about tool sustainability, especially the challenges with the GLAM toolchain.
Building on what @nskaggs mentioned, this project was initially experimental and lacked a clear owner after the organizational changes (~between April and June 2023, still somewhat ongoing). The Technical Engagement team, which previously supported tool developers and users, no longer exists. The WMCS (Cloud Services) subteam is still intact, but the former members of the Developer Advocacy subteam have moved on to other roles and/or teams.
This initiative originated from T313546: Identify metrics to measure the impact of a tool [Tech Engagement Experiment Week]. The primary aim was to identify ways to support key tool maintainers. The focus on "metrics" was to pinpoint tools that were both essential and potentially at risk. The metrics were a means to an end, not the primary objective. I believe this project doesn't align with the signal-related OKRs. With the Developer Advocacy team now dissolved, the challenge is to determine the next steps for this project. This means identifying an appropriate bucket/OKRs in the annual plan and advocating for this project's inclusion.