Thanks for reading them Pine! I think it would be great if you reach out to those teams (either on meta talk pages if they have them, other mailing lists etc). I think leaving the questions here all as one pile is sadly a recipe for non-response as not only are most staff members (like most community members) not subscribed (for the best, it would be an enormous amount of donor funds spent all combined with them reading it) it's also rarely a productive use of a thread to try and throw it in so many directions at once. That said, the high level comments seem perfect for the thread.
James Alexander Manager Trust & Safety Wikimedia Foundation (415) 839-6885 x6716 @jamesofur
On Mon, Oct 19, 2015 at 1:35 AM, Pine W wiki.pine@gmail.com wrote:
Thanks Tilman. I finally got around to skimming most of this. Questions & Comments below:
Communications: seems to be firing on all cylinders.
Team Practices: seems to be making a difference in supporting other individuals and teams. Some of the metrics chosen look great.
Release engineering: great idea about the skill matrix; would HR and Team Practices like to expand this to other teams?
Grants restructuring: big job, thanks/congrats for how it was done, looking forward to execution
TechOps: nice to see that OTRS upgrade is in progress; I believe that this has been talked about for years
Labs: I have a subjective impression of much improved reliability, so thank you
Design research: University of Washington mentioned; what's the connection?
Performance: thank you for working on paint time
Security: I have a suggestion for KPIs: maximum and median times for resolution of critical and high priority bugs; and maximum and median time for first response to bug reports on all channels (Phabricator, email, etc)
Reading: can we get an update on what's being done WRT push notifications?
Partnerships: happy to see pre-install deal coming soon
Editing: how is the community feedback about the split of Echo notifications.
Multimedia: yay for ability to upload to Commons from VE; excited that Excel import is coming (this may stop my complaints to Grantmaking about MediaWiki tables for budgets)
High level comment: from these reports it looks like the Foundation is generally making good progress. Going forward a theme that I'd really like to see is closer integration of WMF priorities with community priorities. I hear from my colleagues at in-person meetings and online that there is a sense that WMF's priorities may or may not be the community's priorities. A certain amount of that is understandable, but my subjective sense is that there's a fair amount of frustration in the community and that the situation could be better. Suggestion: take advantage of the Evaluation team's enhanced survey capacity to run surveys like the one that WMIL ran, and run them every 6 months. Prioritize the languages to maximize return on translation investment. Then adjust WMF quarterly priorities in alignment with the priorities expressed in the community priorities survey. Also, establish SLAs for all departments with regard to responses to community questions.
Thanks! I hope that other community members will write comments and questions also.
Pine
On Fri, Oct 16, 2015 at 10:15 PM, Tilman Bayer tbayer@wikimedia.org wrote:
Greetings everyone,
the Wikimedia Foundation's quarterly reviews of teams' work in the past quarter (July-September, Q1 of the 2015-16 fiscal year) took place last week. Minutes and slides for those meetings are now available:
Community Engagement:
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarterl...
Discovery:
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarterl...
Reading and Advancement (with Fundraising Tech):
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarterl...
Editing (comprising the Collaboration, Language Engineering, Multimedia, Parsing, and VisualEditor teams):
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarterl...
Infrastructure (comprising the Analytics, Release Engineering, Services, TechOps, and Labs teams) and CTO (comprising the Design Research, Research & Data, Performance, and Security teams):
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarterl...
Legal, Talent & Culture (HR), Communications, Finance & Administration & Office IT, and Team Practices:
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarterl...
As usual, much of this information will also be available in consolidated form as part of the general WMF quarterly report for Q1, which is planned to be published on October 19.
See
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarterl...
for some general background about the Foundation's quarterly review process.
-- Tilman Bayer Senior Analyst Wikimedia Foundation IRC (Freenode): HaeB
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe