The WMF quarterly review materials focus on team goals, but also includes KPIs, workflows, and scorecards. For {T119387} we have basically combined the data points Community Liaisons and Developer Relations had in their previous quarterly reviews, but we should review everything and decide what makes sense to keep and what is missing.
Also, we should have on-wiki versions with this data. Or, to be more precise, we should keep track of this data on-wiki on a regular basis, and then paste the information to our quarterly review slides.
== Candidates ==
Quoting the Technical Collaboration team strategy (which might need review, see T131689).
* Number of volunteers contributing code to Wikimedia projects / Community Wishlist projects.
* Number of Community Wishlist projects completed by volunteers
* Number of major Product discussions that the team supports.
* Number of major Product discussions within the Technical Collaboration Guidance vs in conflict with it.
Other ideas to be discussed:
* Participation in community events (people sent, sessions facilitated).
* [[ https://www.mediawiki.org/wiki/Team_Practices_Group/Light_engagement_survey | Light engagement surveys ]], like the #team-practices group uses.
* CL coverage:
** How many product audience teams have CLs assigned, involved in product planning activities.
** Percentage of Product and Technology goals requiring CL support that are resourced.
** Beyond team goals, percentage of support requests submitted to CL that receive a response within a week.
** Beyond team goals, percentage of support requests accepted that are resourced within three months.
* Number of unanticipated clashes with the communities related to goals or tasks where CL support has been committed, or where TCG best practices have been followed by the Foundation teams (CLs must ensure that development teams are aware of potential and emerging points of conflict).
* Number of wiki projects requesting beta features and early deployments (where applicable).
* Percentage of top 25 wiki projects in terms of active contributors that have at least one active tech ambassadors and one translator identified (could be the same person).
* Degree of satisfaction of teams receiving CL support or using TCG documentation, recorded via surveys and/or interviews.
* Rates of major community collaborations by volunteers through surveys, to verify whether TCG expectations on best practices were met.
* Number of software projects recommended for new developers, based on their ability to provide mentors, good entry-level documentation, first tasks, and a roadmap.
* Number of active local developer meetups and their regional distribution.
* Number of Wikimedia affiliates and partner organizations (through Wikipedia Education Program, GLAM...) involved in developer outreach activities.