Wikimedia Technology/Goals/2017-18 Q2
Introduction
[edit]Purpose of this document
[edit]Goals for the Wikimedia Technology department, for the second quarter of fiscal year 2017â18 (October 2017 â December 2017). The goal owner in each section is the person responsible for coordinating completion of the section, in partnership with the team(s) and relevant stakeholders.
This quarter, the Technology department is orienting its goals to the annual plan programs it is working on, rather than to individual teams. The goal-setting process is described here.
Goals for the Audiences department are available on their own page
Legend
[edit]Tech Goal categorizes work into one or more of these quadrants:
| A Foundation level goals | C Features that we build to improve our technology offering |
| B Features we build for others | D Modernization, renewal and tech debt goals |
ETA (Estimated Time of Arrival) fields may use the acronym EOQ (End of Quarter).
Status fields can use the following templates: 
In progress, 
To do, 
 Postponed, 
 Done or 
Partially done
Technology departmental programs
[edit]Overall goal owner: Mark Bergsma
- Owner for Outcome 1: Mark Bergsma
- Owner for Outcome 2: Ian Marlier
- Owner for Outcome 3: Nuria Ruiz
- Owner for Outcome 4: Bryan Davis
- Owner for Outcomes 5 and 6: Greg Grossmeier
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 1: All production sites and services maintain current levels of availability or better. | Objective 1: Deploy, update, configure, and maintain production services (Traffic infrastructure, databases & storage, MediaWiki application servers, (micro)services, network, and miscellaneous sites & services) | Provide dedicated database resources for wikidata  Done
|
TechOps (DBA) | Release Engineering, WMCS, MediaWiki, Wikidata (all MediaWiki developers using Wikidata) | D | EOQ | Â Done
|
| Outcome 1: All production sites and services maintain current levels of availability or better. | Objective 1: Deploy, update, configure, and maintain production services (Traffic infrastructure, databases & storage, MediaWiki application servers, (micro)services, network, and miscellaneous sites & services) | Upgrade Varnish from v4 to v5 on at least one Traffic cluster  Done
|
TechOps (Traffic) | Analytics (varnishkafka) | D | EOQ | Â Done
|
| Outcome 1: All production sites and services maintain current levels of availability or better. | Objective 1: Deploy, update, configure, and maintain production services (Traffic infrastructure, databases & storage, MediaWiki application servers, (micro)services, network, and miscellaneous sites & services) | Modernize Puppet configuration management:
|
TechOps + WMCS | D | EOQ | In progress
| |
| Outcome 1: All production sites and services maintain current levels of availability or better. | Objective 1: Deploy, update, configure, and maintain production services (Traffic infrastructure, databases & storage, MediaWiki application servers, (micro)services, network, and miscellaneous sites & services) | Reduce technical debt in metrics monitoring: Increase porting of statsd/graphite metrics to Prometheus
|
TechOps | Analytics, Search | D | EOQ | In progress
|
| Outcome 1: All production sites and services maintain current levels of availability or better. | Objective 1: Deploy, update, configure, and maintain production services (Traffic infrastructure, databases & storage, MediaWiki application servers, (micro)services, network, and miscellaneous sites & services) | Plan for when HHVM no longer supports PHP5 task T172165
|
CTO-Team + Ian | MediaWiki platform, TechOps, TechCom | D | Q3 | Â Postponed
|
| Outcome 1: All production sites and services maintain current levels of availability or better. | Objective 3: Maintain data center infrastructure and equipment lifecycle from procurement through break-fix to decommissioning |
|
TechOps (Traffic, DC Ops) | Finance, Legal | A | EOQ | Â Done
|
| Outcome 2: All our users consistently experience systems that perform well. | Objective 1: Maintain a comprehensive toolset to measure the performance of our platforms |
|
Performance | None | C/D | EOQ | Â Done
|
| Outcome 2: All our users consistently experience systems that perform well. | Objective 3:Â Modernize our performance toolset. We will measure performance metrics that are closer to what users experience. |
|
Performance | None | A/ B | EOQ | Â Done
|
| Outcome 2: All our users consistently experience systems that perform well. | Performance | None | B | EOQ | Â Done
| ||
| Outcome 3: We have scalable, reliable and secure systems for data transport. | Objective 1: Consolidation of analytics Kafka infrastructure to tier-1 requirements, including TLS encryption | Analytics | TechOps | C: Improving our offering
D: Tech debt |
Q4 | In progress
| |
| Outcome 3: We have scalable, reliable and secure systems for data transport. | Objective 2: Maintenance and expansion of current Hadoop cluster to support new use cases that require more computational resources |
|
Analytics | C: Improving our offering | Q4 | ||
| Outcome 3: We have scalable, reliable and secure systems for data transport. | Objective 3: Software, hardware upgrades, and maintenance on analytics stack to maintain current level of service |
|
Analytics | TechOps | C: Improving our offering | EOY | In progress
|
| Outcome 4: Wikimedia Cloud Services users can leverage a reliable and public Infrastructure as a Service (IaaS) product ecosystem for VPS hosting. | Objective 2: Pay down technical debt and allow upgrading of the core OpenStack platform to modern, supported releases by replacing the current network topology layer with OpenStack Neutron, which has become the standard for most OpenStack deployments. | WMCS | C: Improving our offering
D: Tech debt |
Q3 | In progress
| ||
| Outcome 5: We have effective and easy-to-use testing infrastructure and tooling for developers. | Milestone 1: Develop and migrate to a JavaScript-based browser testing stack | Migrate majority of developers to JavaScript based browser test framework (webdriver.io)
|
Release Engineering | All developers | C, D | EOY | In progress
|
Goal owner: Tim Starling
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 1: Stakeholders in MediaWiki development will have sense of progress and direction | Objective 1: Develop a MediaWiki roadmap |
|
MediaWiki | None | C: Improving our offering | End of Q3 | In progress
|
| Outcome 2: MediaWiki code quality will be improved | Namespaceization (T166010) | MediaWiki | none | D: Tech debt | End of Q3 | In progress
| |
| Outcome 3: MediaWiki security and stability will be improved | Objective 1: Address the backlog of action items that arise from security and downtime post-mortems | Support restricted execution of external commands (T173370) | MediaWiki | Operations | A: Programmatic core priority: improve privacy and security | EOQ; Q3 deployment | Â Done
|
| Outcome 3: MediaWiki security and stability will be improved | Objective 1: Address the backlog of action items that arise from security and downtime post-mortems | Cease using unserialize() for MediaWiki text storage (T161647) | MediaWiki | None | A: Programmatic core priority: improve privacy and security | End of Q3 | In progress
|
Goal owner: Jean-Rene Branaa
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 1: The amount of orphaned code that is running Wikimedia âproductionâ services is reduced | Objective 1: Define a set of code stewardship levels (from high to low expectations) - task T174090 | Objective 1, defining a set of stewardship levels. | Release Engineering | Code Health Group | B, D | EOQ | Partially done
|
| Outcome 1: The amount of orphaned code that is running Wikimedia âproductionâ services is reduced | Objective 2: Identify and find stewards for high-priority/high use code segment orphans - task T174091 | Objective 2, begin finding stewards for high priority orphans. Two quarters worth of work. | Release Engineering | Code Health Group, Current and future code/product stewards | B, D | End of Q3 | In progress
|
| Outcome 2: Organizational technical debt is reduced. | Objective 1: Define a âTechnical Debt Project Managerâ role that regularly communicates with all Foundation engineering teams regarding their technical debt | Objective 1, define the Technical Debt PM role. | Release Engineering | WMF Product Mangers (or similar) | B, D | EOQ | Â Done
|
| Outcome 2: Organizational technical debt is reduced. | Objective 2: Define and implement a process to regularly address technical debt across the Foundation | Objective 2, begin defining and implementing the process to regularly address technical debt. Two quarters worth of work. | Release Engineering | B, D | End of Q3 | In progress
|
Overall goal owner: Bryan Davis
- Owner for Outcome 1: Bryan Davis
- Owner for Outcomes 2 and 4: Dario Taraborelli
- Owner for Outcome 3: Cindy Cicalese
- Owner for Outcome 5: Deb Tankersley
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 1: Becoming a technical contributor to the Wikimedia movement by creating and maintaining 'tools' (bots, webservices, etc) and other innovative solutions is easier than it has been historically because documentation is easier to find, more comprehensive, and descriptive of start to finish steps needed to solve common problems. Cloud Services product users feel comfortable sharing their knowledge with others as part of a community with a culture of sharing via documentation and mutual support. | Objective 1: Collaborate with community to find volunteers willing to form a documentation Special Interest Group to update documentation of existing Cloud Services products |
|
WMCS | Technical Collaboration | A: Foundation goal (Community)
B: Serving our audiences C: Improving our offering |
EOQ | Â Postponed
|
| Outcome 1: Becoming a technical contributor to the Wikimedia movement by creating and maintaining 'tools' (bots, webservices, etc) and other innovative solutions is easier than it has been historically because documentation is easier to find, more comprehensive, and descriptive of start to finish steps needed to solve common problems. Cloud Services product users feel comfortable sharing their knowledge with others as part of a community with a culture of sharing via documentation and mutual support. | Objective 2: Create tutorial content for common issues including but not limited to: creating initial account, deploying a functional web service, deploying a functional bot, and running periodic jobs with variations. Where applicable, produce variants for more than one implementation language (e.g. PHP, Python, etc). | WMCS | A: Foundation goal (Community)
B: Serving our audiences C: Improving our offering |
EOQ | Â Done
| ||
| Outcome 2: The adoption of Wikimedia technology can be reliably measured. | Objective 1: Design a set of formal KPIs (key performance indicators) to measure the growth and diversity of our technology audience (task T171220) |
|
Research |
|
A: Foundation goal (Community)
B: Serving our audiences C: Improving our offering |
EOQ | In progress
|
| Outcome 3: Value-added vendors who provide services and support based on Wikimedia software and true 'third parties' who install and use software produced by the Wikimedia movement on their own computers are more confident in recommending, deploying, and extending Wikimedia FLOSS projects. | Objective 1: Establish canonical point of contact for third-parties by promoting the existence of a dedicated technical liaison for software projects with support for third-party users |
|
MediaWiki | A: Foundation goal (Community)
B: Serving our audiences C: Improving our offering |
In progress
| ||
| Outcome 3: Value-added vendors who provide services and support based on Wikimedia software and true 'third parties' who install and use software produced by the Wikimedia movement on their own computers are more confident in recommending, deploying, and extending Wikimedia FLOSS projects. | Objective 2: Clarify the Foundationâs short- and long-term commitments to third-party users. Create, publish, and promote a multi-tiered, third-party support level system for Wikimedia software projects. Document the support level of existing FLOSS projects and ensure that the documented levels of support are delivered. |
|
MediaWiki | A: Foundation goal (Community)
B: Serving our audiences C: Improving our offering |
In progress
| ||
| Outcome 4: The collaboration with research in industry and academics is further scaled and supported. | Objective 1: Organize and host the annual Wiki Research Workshop. (task T171118) |
|
Research |
|
A: Foundation goal (Community)
B: Serving our audiences |
EOQ | Corresponding to each bullet point under goals:
|
| Outcome 5: Organize Wikimedia Developer Summit | Objective 1: A good representation of non-WMF stakeholders related to the main theme are invited and participate at the event (preferred) or online. |
|
CTO Team |
|
A: Foundation goals (Community)
B: Serving our audiences C: Improving our offering |
EOQ | Â Done
|
| Outcome 5: Organize Wikimedia Developer Summit | Objective 2: Discussions start before the event with the involvement of all the relevant stakeholders, in order to identify the points that need to be addressed at the event. |
|
CTO Team |
|
A: Foundation goals (Community)
B: Serving our audiences C: Improving our offering |
EOQ | Â Done
|
Goal owner: Aaron Halfaker See phab tracking Epic: task T176324
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 1: Tool developers and Product teams can innovate tools that use machine prediction to make wiki-work more efficient. | Objective 1: Expand vandalism & good-faith detection models to more wikis (focus on Emerging Communities) |
|
Scoring Platform | C | EOQ | Corresponding to each bullet point under goals:
| |
| Outcome 1: Tool developers and Product teams can innovate tools that use machine prediction to make wiki-work more efficient. | Objective 2: Work with CE and a community liaison to develop and implement better processes for supporting new wikis with a focus on emerging communities | Engage in a community-led discussion about the design and use of JADE (task T170954) | Scoring Platform | CE (Keegan) | A | EOY | In progress
|
| Outcome 1: Tool developers and Product teams can innovate tools that use machine prediction to make wiki-work more efficient. | Deploy on new ORES* cluster (task T168073) | Scoring Platform | Operations (Alexandros) | D | EOQ | In progress
| |
| Outcome 2: Volunteers are empowered to track trends in prediction bias and other failures of AI in the wiki. | Objective 1: Develop best practices for using community input to improve/correct predictions | Deploy an MVP of the JADE API in labs (state database, event generation, structured UI support) (task T176333) | Scoring Platform | Operations (Alexandros) | AC | EOY | In progress
|
Goal owner: Mark Bergsma
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 1: We have seamless productization and operation of (micro)services | Objective 1: Set up production-ready Kubernetes cluster(s) with adequate capacity |
|
TechOps | C | EOQ | Â Done
| |
| Outcome 1: We have seamless productization and operation of (micro)services | Objective 2: Create a standardized application environment for running applications in Kubernetes |
|
TechOps | C | Q3 | Â Done
| |
| Outcome 2: Developers are able to develop and test their applications through a unified pipeline towards production deployment. | Objective 2: Set up a continuous integration and deployment pipeline to publish new versions of an application to production via testing and staging environments that reliably reproduce production |
|
Release Engineering | Technical Operations, Services | C | EOQ | Corresponding to each bullet point under goals:
|
Overall goal owner: Nuria Ruiz
- Outcome 1 owner: Nuria Ruiz
- Outcome 2 owner: Marko Obrovac
- Outcome 3 owner: Bryan Davis
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 1: Foundation staff and community have better tools to access data. | Objective 1: Wikistats 2.0 redesign |
|
Analytics | C: Improving our offering | Q4 | Corresponding to each bullet point under goals:
| |
| Outcome 1: Foundation staff and community have better tools to access data. | Objective 2: Better visual access to EventLogging data |
|
Analytics | C: Improving our offering
D: Tech debt |
Q4 | Corresponding to each bullet point under goals:
| |
| Outcome 1: Foundation staff and community have better tools to access data. | Objective 3: Experiments with real-time data and community support for new datasets available |
|
Analytics | C: Improving our offering | Corresponding to each bullet point under goals:
| ||
| Outcome 2:
Access to Wikimedia content and data with scalable APIs |
Objective 1: Revision storage scaling | Migrate mobile HTML storage to Cassandra 3 cluster & new schema. | Service Platform | Technical Operations | D: Tech debt | EOQ | Â Done
|
| Outcome 3: Wikimedia Cloud Services users have easy access to public data. | Objective 1: Provide reliable and available access to Wikimedia database dumps by upgrading the hardware used and consolidating access by internal teams, Cloud Services users, external mirrors, and HTTPS downloaders to the new canonical location. | WMCS | C: Improving our offering | Q3 | In progress
| ||
| Outcome 3: Wikimedia Cloud Services users have easy access to public data. | Objective 2: Complete migration of production database replica access for Cloud services customers to the new high-availability cluster, which uses 'row based' replication technology to provide a more consistent view of production data. | WMCS | Technical Operations (DBA) | C: Improving our offering
D: Tech debt |
Partially done
|
Overall goal owner: Tim Starling
- Outcome 1 owner: Tim Starling
- Outcome 2 owner: Marko Obrovac
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 1: Our audiences enjoy improved MediaWiki and REST API availability and reduced wiki read-only impact from data center fail-overs. | Objective 1: MediaWiki support for having read-only âreadâ requests (GET/HEAD) be routed to other data centers |
|
Performance (MediaWiki) | None | D: Tech debt | EOQ | Partially done
|
| Outcome 2: Backend infrastructure works reliably across data centers | Objective 1: Reliable, multi-DC job processing | Service Platform | Operations, Analytics | D: Tech debt | EOQ | Â Done
|
Goal owner: Leila Zia
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 1: Surface relevant information about the articles to editors at the time of editing with the goal of helping editathon organizers | Objective 1: Build, improve, and expand algorithms that can provide more detailed recommendations to editors about how an article could be expanded. (task T171224) |
|
Research |
|
B, C |
EOQ | Corresponding to each bullet point under goals:
|
Goal owner: Bryan Davis
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 1: Members of the Wikimedia movement are able to develop and deploy technical solutions with a reasonable investment of time and resources on the Wikimedia Cloud Services Platform as a Service (PaaS) product. | Objective 2: Migrate Tool Labs account workflows from Wikitech to Striker where they are easier to integrate with the new user onboarding workflow and easier to maintain |
|
WMCS | Research | A: Foundation goal (Community)
B. Serving our Audiences |
EOQ | In progress
|
| Outcome 2: The 'Labs, labs, labs' branding confusion is eliminated. Branding is separated, so that all of these are no longer referred to as just âLabsâ: infrastructure as a service product, the platform as a service product, the team that manages those products, and the community that uses them to produce technical solutions. | Objective 1: Complete initial outlined rebranding activities and announcements by 2017-12-31 | WMCS | C: Improving our offering | EOQ | Â Done
| ||
| Outcome 3: Wikimedia community members, Foundation staff, and potential contributors are aware of the breadth of products and services offered by the Cloud Services team. | Objective 1: Promote available services and products at relevant conferences, hackathons, and within the Wikimedia communities | WMCS | Technical Collaboration | A: Foundation goal (Community)
B: Serving our audiences |
EOQ | In progress
|
Goal owner: Dario Taraborelli
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 1: Quantitative research is available to help Wikipedia and Wikidata contributors focus and prioritize their sourcing efforts | Objective 1: Estimate what proportion of content in Wikipedia or Wikidata is unsourced and in need of citations. | Publish a rich dataset on citation contexts to support additional research on Wikipedia sourcing gaps (task T175663) |
|
|
C | EOQ | Â Done
|
| Outcome 3: Outreach activities continue to ensure community and technical efforts are aligned | Objective 1: Fundraise for, and host the 3rd annual meeting in the WikiCite series | Write a report for the funders (task T176500) and fundraise for WikiCite 2018 (task T174750) |
|
|
B | EOQ | In progress
|
Goal owner: Leila Zia
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 1: | To do
|
Note: When the draft annual plan was written, the Search Platform and Fundraising Tech teams were in Product. They were moved into Technology during the "tune-up" in June 2017.
Goal owner: Erika Bjune
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
|
|
|
Search Platform | Analytics, Operations, Community Engagement | C. Improve our own feature set | EOQ | Â Done
|
|
|
|
Search Platform | Analytics, Operations, Community Engagement | A. Foundation Goal: Reach,
C. Improve our own feature set |
EOQ | Partially done
|
|
Address technical debt:
|
Search Platform | Operations, Search Front-end | D. Technical Debt | EOQ | Â Done
| |
|
|
|
Search Platform | Analytics, Operations, WMDE | C. Improve our own feature set | Q3 | In progress
|
Goal owner: Katie Horn
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 1: Advancement and fr-tech find a solution that lowers or does not increase current maintenance costs. | Q2 we will be running down our list of options and investigating them. We have priority meetings regularly | As time allows: possible tech investigations | Advancement/fr-tech | Advancement management | D | EOQ | Â Done
|
Goal owner: Katie Horn
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 1: In FY 16/17 four well-trained team members spent 106 hours on deduping related to the English campaign. One of those employees may not be available for this task next year and a new contractor may help. We still hope to reduce the hours spent. | We have scoped out several phases to fix names and addresses | Work on Phase 1 and 2 in the spec attached to task T143057 | fr-tech | Major Gifts team | B | EOQ | In progress
|
Segment 3: Research on harassment
[edit]Goal owner: Dario Taraborelli
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 1: We aim to understand and model the characteristics of harassment in Wikimedia projects. | Objective 1: Conduct research to characterize and model wikihounding. (task T171249) |
|
|
|
A (Community), C |
EOQ |
In progress
|
| Outcome 1: We aim to understand and model the characteristics of harassment in Wikimedia projects. | Objective 2: Prototype new models to facilitate sockpuppet detection and the classification of toxic discussions. (task T171251) |
|
|
|
A (Community), C |
EOQ |
Corresponding to each bullet point under goals:
|
Segment 2: Technology
[edit]- Owner for Outcome 2: Nuria Ruiz
- Owner for Segment 3: Erika Bjune
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 2: To protect user data and uphold movement values, the Wikimedia Foundation continues compliance with best practices for data management | Objective 3: Ensure retention guidelines are being followed | Purge all old data from EventLogging master task T168414, Data Purging for eventlogging data slaves task T156933 | Analytics | To do
| |||
| Segment 3: Office IT, Outcome 1: Through improvements to our organizational security posture, the Foundation ensures the high-quality protection and security of our infrastructure and data | Objective 1: Evaluate current security practices and make changes and provide training as appropriate | Evaluate and recommend an outside solution for ongoing WMF employee training on protection from phishing | OIT, Security, Legal | DBAs (Ops) | In progress
|
Segment 1: Database Integration
[edit]Goal owner: Tim Starling
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
|
|
|
MediaWiki, WMDE | EOQ | To do
|
Goal owner: Erika Bjune
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 1: Readers, editors, and content re-users can find media [on commons] using precise queries. | Objective 1: Commons search will be extended via CirrusSearch and Elasticsearch and Wikidata Query Service, to support searching based on structured data elements describing media. |
|
Search Platform, Analysts, WMDE | C. Improve our own feature set | EOY | In progress
| |
| Outcome 1: Readers, editors, and content re-users can find media [on commons] using precise queries. | Objective 2: Advanced search capabilities (e.g., Wikidata Query Service, SPARQL queries) will be updated to support the more specific media search filters and the relationships to the topics they represent. |
|
Search Platform, WMDE | Operations | C. Improve our own feature set | EOY | In progress
|
Goal owner: Jonathan Morgan
| Annual plan outcome | Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 2: Develop a better understanding of existing needs for Structured Commons | Objective 1: Attend movement and GLAM network events that allow us to identify needs and priorities for this stakeholder groups.(task T171252) |
|
Research | Community Programs; Technical Collaboration | C | EOQ | In progress
|
| Outcome 2: Develop a better understanding of existing needs for Structured Commons | Objective 2: Write case studies and documentation for Commons and Wikidata projects that allow project development among Wikimedia Communities and allow us to identify gaps in existing tools.(task T171252) |
|
Research | Community Programs; Technical Collaboration; Multimedia | C | EOQ | To do
|
"Missing" Program
[edit]In early 2017, when the Fundraising Tech team (fr-tech)was developing their FY2017-18 annual plan, they were discouraged from including any kind of program related to the actual raising of funds. Since then, as an organization, we have decided to try to capture more of our work in the form of quarterly goals within programs.
Fr-tech works closely with Advancement to raise the target budget each year. Their first priority is the maintenance of current systems and the support of live activities and campaigns for Advancement. At least 50% of the budget is raised in Q2 (Oct-Dec) each year. The following work is not expressly called out in the annual plan but is essential to the funding of this organization. The table is structured as if there were a program in the annual plan.
| (Faux) Annual plan outcome | (Faux) Annual plan objective(s) | Quarterly Work (or Goal) | Primary Team(s) | Dependencies | Tech Goal | ETA | Status |
|---|---|---|---|---|---|---|---|
| Outcome 1: Advancement and fr-tech raise the target budget amount for the year | Conduct a successful English fundraising campaign | Support the English Campaign:
|
fr-tech with Advancement | Advancement, External vendors: Ingenico and Adyen | On-going | In progress
|
Please note that virtually all activities in fr-tech are for fundraising purposes, and are budgeted as fundraising (and not as "programs") in the non-profit accounting format. Anything labeled as an fr-tech project or programs is budgeted as non-programmatic work.