When I first heard of Wikimedia, the first thing that came to my mind was Wikipedia. However,as time went by, I understood that behind the scenes, Wikimedia is a large ecosystem of tools, contributors, and communities working together to make knowledge accessible to everyone.
As I began exploring Wikimedia during my Outreachy application, I discovered that a lot of effort goes into improving not just content, but also the experience of contributors—the editors, researchers, and volunteers who make Wikimedia projects possible.
One initiative that really caught my attention is the Lusophone Technological Wishlist.
*What is the Lusophone Technological Wishlist?
*
The Lusophone Technological Wishlist is a community-driven initiative focused on identifying the most important technical needs of Portuguese-speaking Wikimedia contributors.
Rather than leaders making assumptions, this wishlist is created from real feedback from the community. It highlights tools and improvements that can make editing, researching, and contributing more efficient and enjoyable.
This aligns closely with Wikimedia’s broader goal of improving contributor experience, which ensures that contributors have the right tools they need to work effectively.
As part of this effort, specific proposals are selected for implementation—and two of them particularly were prerequisites for Outreachy applicants that will make them eligible to be selected as interns.
Wishlist #3: Detecting Duplicate References in the Visual Editor
One common challenge when editing Wikipedia articles is managing references. Contributors often reuse sources, but without proper checks, they can add the same reference multiple times, leading to duplication.
Wishlist #3 proposes a solution to this problem:
Automatically detect duplicate references in the Visual Editor using identifiers such as DOI, ISBN, or URL, and allow users to reuse existing references instead of creating new ones.
Why does this matter?
- It keeps articles cleaner and more organized
- It reduces redundancy in citations
- It improves the editing experience, especially for new contributors
My Perspective
While working on a related task involving URL validation, I began to understand how important it is to handle identifiers correctly. Even small inconsistencies in URLs or formats can lead to duplication or errors.
I also encountered a situation where date handling behaved differently across time zones, which made me realize that seemingly simple data can introduce subtle issues in real-world applications. This reinforced the importance of carefully handling edge cases when building features like duplicate detection.
Wishlist #8: Adding Wikidata Support to WikiScore
Another interesting proposal is Wishlist #8, which focuses on improving a tool called WikiScore.
WikiScore is used to track and evaluate contributions during events like edit-a-thons and contests. However, it currently has limited support for Wikidata contributions.
Wishlist #8 aims to:
Extend WikiScore to include Wikidata edits, allowing contributions to structured data to be properly counted and recognized.
Why is this important?
- Wikidata plays a major role in structuring knowledge across Wikimedia
- Contributors working on Wikidata deserve visibility and recognition
- It encourages broader participation in different types of contributions
My Perspective
During my tasks, I worked with structured data and learned how important it is to process and present it correctly. Transforming raw data into meaningful output is not always straightforward, especially when consistency and accuracy are required.
This gave me a better appreciation for tools like WikiScore, where contributions need to be tracked reliably and fairly.
What I Learned from Exploring These Tasks
Working on tasks related to these ideas helped me understand that:
- Small improvements can have a big impact on user experience Real-world data often comes with inconsistencies and edge cases
- Writing functional code is not enough,code must also be reliable and adaptable
- Feedback plays a key role in improving both code quality and understanding
For example, through feedback, I learned to:
- Handle time zone differences when working with dates
- Improve error handling to provide more meaningful output
- Follow best practices when making HTTP requests
These lessons helped me move beyond just “making things work” to thinking more deeply about how and why things should work.
Why This Matters
What stood out to me most is how these wishlist items focus on real contributor needs.
Whether it’s reducing duplicate references or recognizing Wikidata contributions, these improvements are about making it easier for people to contribute effectively.
In a global, collaborative platform like Wikimedia, even small enhancements can improve workflows for thousands of contributors.
Conclusion
Exploring the Lusophone Technological Wishlist has given me a deeper appreciation for the work that goes into supporting Wikimedia contributors.
It’s not just about building features—it’s about understanding real problems, handling real-world data, and creating tools that make collaboration smoother and more effective.
As I continue learning and contributing, I’m excited about the opportunity to be part of efforts that improve both the quality of information and the experience of those who help create it.
