We must ensure that our socio-technical system helps editors increase the quality of Wikidata’s existing data and contribute new high-quality data.

Objective:

We want to better integrate the existing Entity Schemas so that they become more central to data maintenance processes and can codify modeling decisions.

Description:

We have Entity Schemas on Wikidata that are not well integrated into existing workflows and community processes. We want to change that and make them a more useful data quality tool.

Upcoming Activities:

• Continue development of new datatype to link to EntitySchemas in statements (Q1) (Q2)
• Rollout of the new datatype to link to EntitySchemas in statements (Q3)
• Further improvements to the new EntitySchema datatype (search by label and alias) (Q3) (Q4)

Objective:

We want to build out feedback loops with data re-users to get them more actively involved in improving the data on Wikidata.

Description:

We have developed the Mismatch Finder as a base for setting up these feedback loops. Now we need to help reusers find their way and understand their potential contributions.

Upcoming Activities:

• Partnership with Purdue University to have students compare Wikidata’s data to more external sources and generate more mismatches for the Mismatch Finder (Q1)
• In our partnership with Purdue University the students have successfully uploaded new mismatches to the Mismatch Finder and they now work on sharing their experiences (Q2)

We want to make sure that anyone can use the data in Wikidata to make the world a better place. While everyone can re-use our data, we give priority to organizations and projects that align with our values and have a high impact.

Objective:

We want to improve our APIs to make it easier for programmers to access our data.

Description:

We will release and improve the Wikibase REST API.

Upcoming Activities:

• Finish remaining operations for reading and editing Items and Properties (Q1) (Q2)
• Discuss next steps for the REST API and get feedback at for example the Wikimedia Hackathon (Q2)
• Improve REST API error messages and documentation (Q3)
• Research additional access methods reusers need (Q3) (Q4)

Objective:

We want to empower and encourage more people to develop applications using Wikidata’s data.

Description:

We will improve documentation and other material for a developer audience.

Upcoming Activities:

• Improve documentation and draft landing page for developers (Q1) (Q2)
• Publish landing page targeted at developers using data from Wikidata (Q3)
• Plan and start outreach activities to developers using data from Wikidata (Q3)
• Plan Data Reuse Days for early 2025 (Q4)

We want to ensure that diverse perspectives come into play as fundamental decisions are made for and about Wikidata. By doing so we can better support knowledge often underrepresented in knowledge graphs.

Objective:

Organize events for the Wikidata community.

Description:

We will organize events to bring the Wikidata community together and enable people to move closer into the core of the community.

Upcoming Activities:

• Leveling Up Days preparation (Q1)
• Running the Leveling Up Days (Q2)
• Planning and preparing for the next event centered around lexicographical data (Q2)
• Running the Lexicodays (Q2)
• Organizing activities for the Wikidata birthday (Q3)
• Celebrating Wikidata’s 12th birthday with events all around the world (Q4)

We need to invest time and effort into some core parts of Wikidata.

Objective:

Make improvements to the manual editing of Items (focused on mobile editing).

Description:

We will improve a part of how Items are edited manually.

Upcoming Activities:

• Settle on a focus for the initiative and start research (Q1)
• Research and design to decide how we can make editing of statements from mobile devices better (Q2)
• Technical investigations for the way forward for improving editing of statements on mobile devices (Q4)

Objective:

Reduce technical debt and maintenance burden.

Description:

We will deprecate WiKit, the design system, in favor of the new Wikimedia design system Codex.

Upcoming Activities:

• Migrate Mismatch Finder to Codex (Q1)
• Migrate Query Builder to Codex (Q2) (Q3) (Q4)
• Migrate Special:NewLexeme to Codex (Q3) (Q4)
• Polishing and rollout of mul language code (Q2) (Q3) (Q4)
• Investigate and if possible make necessary changes for a wider roll-out of Vector 2022 and dark mode (Q4)

The Wikimedia Projects should be able to rely on Wikidata to share their workload across language and project family boundaries.

Objective:

We want Wikidata and the other Wikimedia projects to increase their collaboration for mutual benefit

Description:

We establish structures to support the collaboration between Wikidata and the other Wikimedia projects sustainably.

Upcoming Activities:

• Hiring Senior and Mid-level Software Engineers to join the team (Q1)
• Map out the current Wikidata integrations with other Wikimedia projects and examine data to compare the scale of existing integrations (Q1)
• We’ve given offers to two engineers and will continue hiring for two more Engineers (Q2)
• Onboard one of our engineers (Q2)
• Present at Leveling Up Days and facilitate a few sessions (Q2)
• Reach out to community members who signed up to our user pool and schedule interviews with them to learn more about how we can solve their Wikidata Integration issues (Q2)
• Completing our analytics discovery research component (Q3)
• Welcoming and onboarding our Engineers (Q3) (Q4)
• Sharing the most important findings from our analytics research component (Q4)
• Technical implementation of Engineering onboarding tasks (Q4)

More people need access to knowledge and technology presented in their own language, and content in that language should be accessible to all. Language data is a fundamental building block in reaching that goal.

Objective:

We have trusting and sustainable relationships with our partners.

Description:

We want our partners at Wikimedia Indonesia and the Igbo Wikimedians User Group to have everything they need to implement their projects.

Upcoming Activities:

• Software Team Indonesia
  • Hiring a programming agency to develop the MVP of the micro contribution tool for lexicographical data the team has prototyped (Q1) (Q2)
  • Starting the user testing with the MVP (Q1) (Q2)
  • Hosting monthly activities about lexicographical data for the local communities (Q1) (Q2) (Q3) (Q4)
  • Co-hosting Lexicodays together with WMDE (Q2)
  • Develop a demo version of the micro contribution tool, “Lexica” (Q2)
  • Release the MVP of the micro contribution tool (Q3)
  • Gather community feedback on the tool, exploring ideas for potentially new features (Q3) (Q4)
  • Release of “Lexica” (Q4)
  • Implementing additional features to “Lexica” (Q4)
• Igbo Wikimedia User Group:
  • Hosting activities for the local communities (Q1) (Q2) (Q3)
  • Focusing on hosting additional in-person events across Africa. (Q3) (Q4)
• Wikidata One Click Info team:
  • Kick-start development of the Wikidata One Click Info browser extension for Firefox and Chrome (Q3)
  • Release of the Wikidata One Click Info browser extension (Q4)
• Wiki Movimento Brazil:
  • Kick-start development of QuickStatements 3.0 (Q3)
  • Conducting community research to prioritize new functionalities (Q3) (Q4)
  • Implementation of new functionalities. (Q3) (Q4)

We are aiming to grow our user base by enabling new joiners to more easily start their first Wikibase project, lowering the barrier to entry and continuing to enable a diverse ecosystem.

Objective:

Wikibase.cloud expands its user base with an improved experience for new joiners and continuous learning to suit their needs while increasing infrastructure reliability.

Description:

We continue to learn how to make it easier for our users to start their first projects. This will help us grow sustainably and retain users just starting out in our ecosystem. For that to succeed, we need to conduct further research into achieving a higher level of Knowledge equity. Additionally, we want to increase our infrastructure reliability to allow for stable growth of our ecosystem

Upcoming Activities:

• Reusing data models - Based on research, we identified the need for new users to reuse existing data models. We expect this to improve onboarding and reduce drop-off rates while upholding data quality. (Q2-Q3)
• Default main page - Guidance & instructions can help new users start their project. We plan to improve the main page in order to lower the barrier to entry for first time users of our service (Q2)
• New user research - Identify further areas of improvement for new users through UX research (Q2-Q3)
• Knowledge Equity research - In order to diversify our ecosystem, we need to learn where opportunities for improvement are (Q2-Q3)
• Infrastructure reliability - Gradually increasing reliability of our service through research and allocating resources accordingly (Q2-Q3)
• Deployment automation - Working on reducing time we spend on deployment to be able to invest it to other initiatives (Q1-Q4)
• Metrics framework - Introducing a way to track our progress meaningfully (Q2-Q3)
• Federated queries - Improvements of user experience when it comes to federated queries (Q4)
• Low-hanging features - Addressing low-effort bug fixes and features that can significantly improve the user experience with the product (Q4)
• Feature parity with Wikidata - Implementing the most wanted and low-hanging features familiar to our users from Wikidata (Q4)

We must ensure that more projects are able to independently onboard themselves into the Wikibase Ecosystem by reducing the complexity of software setup, data importing, and maintenance. To support knowledge equity, in parallel, we must ensure that the Wikibase Ecosystem welcomes a diversity of people, knowledge, and disciplines.

Objective:

Experts in the public and open use of Wikibase Suite have taken a key role in determining the future of the product.

Description:

We are investing in building processes that provides more opportunities to partner with, and learn from, expert users in the Wikibase ecosystem. This will enable us to better align our efforts towards the areas of biggest impact for the ecosystem as a whole.

Upcoming Activities:

• Partner with the Wikibase Stakeholder Group to develop an outcome oriented roadmap (Q3-Q4)
• Publish code contribution strategy for Wikibase Suite (Q3-Q4)

Objective:

Beginners within the Wikibase ecosystem are increasingly well supported in pursuing success with their Wikibase projects.

Description:

A thriving ecosystem needs space for new voices and diverse perspectives. As such, we want to support beginners in finding success with Wikibase Suite.

Upcoming Activities:

• We hired a developer advocate in Q1 who will likely be starting in Q3.
• We will improve or add three key documentation topics (Q3-Q4)

Objective:

Wikibase Suite is reliable for mission-critical use in public and open knowledge projects.

Description:

We will develop and release improvements to the Wikibase Suite software package, with a focus on those relevant to public and open knowledge projects.

Upcoming Activities:

• We will work on a series of features which making updating and running Wikibase Suite in a production environment easier and more reliable. (Q3-Q4)
• We will continue to work on maintaining a fast release cycle in response to forthcoming Mediawiki releases

• Wikidata board on Phabricator
• Wikibase board on Phabricator
• archived development plan page - 2023 and earlier
• Wikidata:Report a technical problem