These are the metrics being proposed in our draft for {T124019}:
Goal: Community liaison support to WMF Product teams around new initiatives and ongoing complex projects
* [[ https://meta.wikimedia.org/wiki/Community_Liaisons/KPIs | Number of major Product discussions that the team supports ]].
* [[ https://meta.wikimedia.org/wiki/Grants:Learning_%26_Evaluation/Global_metrics | Global metric ]]: Did your work increase the motivation of contributors, and how do you know?
Goal: Consolidation of the Product Development Process as a systematic approach to community engagement by WMF Product teams, corresponded by the Wikimedia communities.
* Number of major Product discussions within the PDP vs out of process.
* [[ https://meta.wikimedia.org/wiki/Grants:Learning_%26_Evaluation/Global_metrics | Global metric ]]: Did your work increase the motivation of contributors, and how do you know?
Goal: Connect free software developers with the Community Wishlist maintained by the Community Tech team.
* Number of volunteers contributing code to CW projects
* Number of CW projects completed by volunteers
* {T116370}
These metrics are under review just like the rest of the Annual Plan proposal. We should start working on them during the next quarter (April - June) in order to have a baseline by the beginning of the new fiscal year.
== Previous description ==
Let's discuss Community Liaisons and Developer Relations quarterly goals, with the goal of having satisfactory metrics by our next quarterly review in April.
Community Liaisons: are we happy about [[ https://meta.wikimedia.org/wiki/Community_Engagement_(Product)/KPIs | the metrics being collected currently ]]?
Developer Relations: the KPI about users of our APIs is simply not working (not technically working, not aligned with our actual work still today).
When thinking about the right KPIs, we need to consider the direction of these teams in the WMF Strategy and Annual Plan.