Software Collaboration for Wikidata/Documentation

Key Info

Updates

Activities

Partners

Resources

Open Call 2023

Documentation

Partner Meeting Wikicollabs and Wikimedia Deutschland Partner Meeting with the Igbo Wikimedians User Group and Wikimedia Deutschland Presentation of Quick Statement 3.0 by Wikimedia Brasil Summary The Wikidata Software Collaboration project, funded by the Arcadia Trust, was designed to promote decentralized software development within the Wikimedia Movement, focusing on creating tools that aim to improve the Wikidata ecosystem. Wikimedia Deutschland (WMDE) initiated this program through partnerships with various Wikimedia affiliates and community groups, each committed to developing software solutions tailored to their specific needs and local contexts. In the first phase of the project (2021–2023), the primary focus was set on laying the organizational groundwork. This involved hiring key staff and defining roles at WMDE, as well as finding and onboarding partners excited to shape those relationships in the Wikimedia movement. This foundational work enabled the project to move forward with a clear direction and solid administrative foundation. Wikicollabs and Wikimedia Indonesia in Indonesia, the Igbo Wikimedians User Group in Nigeria, Wikimedia Brasil in Brazil and the Wikidata ‘One Click Info’ Team located in Ghana joined as partners over the course of the project. Phase two (2023–2025) centered the project discovery and initial development of key products and projects. During this time, the partners worked on software tools like Lexica, a tool designed to simplify micro contributions to lexicographical data on Wikidata, QuickStatements 3.0, an improved version of a widely used tool for making a large number of edits to Wikidata and Wikidata One Click Info, a browser extension that provides summarized description based on Wikidata items to its users. Early versions of these tools were tested through community feedback, leading to continuous improvements and refinements. This phase solidified the development of the tools while ensuring that the solutions being built were aligned with the needs of the broader Wikidata community. Wiki Mentor Africa, a mentoring program to increase technical capacity in African volunteer communities - had been set up mentoring its first participants to improve widely used Wikidata tools. The third phase (2024–2025) scaled the developed tools and projects, integrated them further into the Wikidata ecosystem, while paving the way for their long-term sustainability. By this stage, Lexica was officially launched, receiving positive community feedback, and QuickStatements 3.0 had become widely adopted within the community. Wiki Mentor Africa expanded its scope to organizing regional hackathons with communities and multiple partner organisations across the African continent. Towards the end of the project, another application was developed by Wikicollabs with the goal to provide a way to Wikidata communities for completing and improving Wikidata's lexicographical data across different languages: Broomstick. Looking forward, WMDE plans to continue supporting these partnerships, with a strong focus on scaling the tools developed and securing further funding for future projects. The success of the Wikidata Software Collaboration shown by the wide adoption of the tools and program by our communities highlights the importance of building software that is not only technically robust but also culturally sensitive and accessible. Main Outcomes Outcome Description Lexica Micro contribution tool for enriching lexicographical data on Wikidata Broomstick Tool to uncover Lexemes that can be improved on Wikidata Wikidata One Click Info Browser extension that delivers verified Wikidata content to the general public QuickStatements 3.0 Significantly upgraded version of QuickStatements, a critical tool for mass editing Wikidata Wiki Mentor Africa Program Mentoring Program for Coding and related skills for African communities Main Learnings With this program, WMDE entered new territory, as they have never before established international multiyear partnerships with a focus on software development. Framed as a “prototype” from the start, the program offered a wide array of  learning opportunities for both WMDE and their partners to understand how similar partnerships and collaborative software development could work in the context of the Wikimedia movement. 1. Collaboration is Key—Build Strong, Trust-Based Partnerships International software collaboration thrives on strong, trust-based relationships among all parties involved. Regular check-ins, clear and honest communication, as well as shared goals help maintain alignment over time. In-person meetings early in the collaboration can be game-changers for establishing trust. Buy-in from the whole organisation across all management levels is central to ensure  long-term commitment to possibly major changes in the organisation.    2. Define Success Early—Set Clear Goals & Evaluation Metrics A shared vision of success should be established from the start Define measurable but flexible evaluation criteria that work for different partners and talk about those with all partners to provide guidance if needed   3. One Size Does Not Fit All—Adapt to Local Contexts Each team has different needs, structures, and working styles which will mean different approaches for each partner. Some partners will need more support in administrative processes, financial reporting, or team building. We are all Wikimedians working towards the same vision of the world, but there will be differences in how we tackle challenges or approach conflict. Inform yourself and familiarize with each other’s working styles and assume good faith in case of misunderstandings.   4. Foster a Culture of Knowledge Sharing Make sharing knowledge and expertise an explicit goal of collaboration. Encourage cross-affiliate exchange, not just between WMDE and partners but among partners themselves and plan dedicated resources and occasions for this, otherwise it might not happen. 5. Flexibility vs. Structure—A Balancing Act While adaptability is crucial, too much uncertainty can create stress and inefficiencies. Provide clear frameworks and topics as starting points but leave room for partners to explore and innovate. Experimentation is valuable, but it should be balanced with accountability and realistic timelines. 6. Administrative and Financial Processes Can Be Barriers—Plan Ahead International bank transfers, currency fluctuations, and administrative delays can significantly impact project timelines. Work closely with finance teams to establish clear, efficient reporting processes. Consider fiscal sponsorship models if partners lack formal organizational structures. 7. Stable Teams are Key to the Success of the Products Software development is long-term work, teams need stability to be successful. Ensure partners have the internal capacity to manage workload sustainably. Supporting administrative and financial assistance can prevent burnout. 8. Open Calls & Broad Engagement Can Spark Innovation Open calls for software contributions bring fresh perspectives and new potential partnerships. They require clear guidelines, transparent selection processes, and sufficient time for applicants to prepare. Engaging the broader Wikidata and Wikimedia community ensures that collaboration is inclusive. 9. Rome wasn’t built in a Day—And so Isn’t a Network for Decentralized Engineering True decentralized software development won’t happen overnight—it requires sustained investment. The first steps are capacity-building, team stability, and gradual transfer of ownership. Future collaboration models should build on existing successes and refine approaches. Sustainable financial arrangements take a long time to arrange and not all partners have the same preconditions for fundraising.