Ever wondered how the features you use on Wikipedia actually get built? It’s not just a top-down decision by developers. A massive chunk of the roadmap comes directly from the people who write and edit articles every day. The Community Wishlist Survey is the primary mechanism for this bottom-up innovation. If you’ve ever clicked "Edit" or scrolled through search results, your experience is shaped by these votes.
For 2025, the survey cycle has been particularly active, focusing heavily on mobile usability and editor tools. But with so many moving parts-proposal submission windows, voting phases, and technical implementation timelines-it’s easy to miss the deadlines. This guide breaks down exactly when you can vote, what the top proposals are fighting for, and why this process matters more than you think.
What Is the Community Wishlist Survey?
At its core, the Community Wishlist Survey is an annual event organized by the Wikimedia Foundation. It allows editors across all language versions of Wikipedia and other projects to propose changes they want to see in the software. Think of it as a democratic feature request system. Unlike traditional bug trackers where users report errors, this survey asks: "What would make your life easier?"
The process relies on collective intelligence. Thousands of volunteers submit ideas ranging from minor interface tweaks to major structural overhauls. These ideas then go through a rigorous vetting process before hitting the ballot box. The winning proposals don’t just sit in a backlog; they are prioritized for development by the Product team at the Wikimedia Foundation. This direct link between community desire and engineering action is what keeps the platform evolving without losing its user-centric soul.
Voting Dates and Timeline for 2025
Timing is everything in open-source communities. If you miss the window, your voice isn’t counted for that year. For the Community Wishlist Survey 2025, the timeline was structured to allow ample time for discussion and consolidation. Here is the breakdown of the critical phases:
- Proposal Submission: Editors submitted their wishes between January 13 and February 17, 2025. This phase required clear descriptions and justification for why the change was needed.
- Vetting and Merging: From February 18 to March 14, staff and experienced community members reviewed submissions. Duplicates were merged, and unclear proposals were clarified or rejected if they fell outside the scope of current technical capabilities.
- Voting Period: The actual voting took place from March 17 to April 7, 2025. Every registered account with a verified email address could cast votes. Each user had 20 votes to distribute among up to 10 proposals.
- Results Announcement: The final list of winning proposals was published in late April 2025, setting the stage for the development roadmap for the remainder of the year.
Why such tight windows? Because coordination costs money and resources. By limiting the voting period, the foundation ensures that the data collected is fresh and reflects the immediate needs of the community rather than outdated grievances from years past.
Top Proposals That Shaped the Agenda
Not all wishes are created equal. Some gain traction because they solve universal pain points. In the 2025 cycle, three categories dominated the conversation: Mobile Editing, Search Functionality, and Accessibility. Let’s look at what made the shortlist and why they resonated with voters.
| Proposal Category | Specific Feature Request | Primary User Group | Impact Level |
|---|---|---|---|
| Mobile Editing | Improved citation tool for mobile devices | New editors, casual contributors | High |
| Search & Navigation | Fuzzy search support for typos | All readers, researchers | Medium-High |
| Accessibility | Enhanced screen reader compatibility for tables | Visually impaired users | Critical |
| Editor Tools | Better diff view for complex edits | Experienced editors, patrollers | Medium |
The push for better mobile editing tools wasn't surprising. Over 60% of traffic to Wikipedia now comes from mobile devices, yet the editing interface has historically been desktop-first. Users complained that adding references on a phone was clunky and error-prone. The winning proposal aims to streamline this workflow, making it as easy to cite a source on a smartphone as it is on a laptop.
Another big winner was improved search functionality. Specifically, fuzzy search-which tolerates minor spelling errors-was a long-standing request. Many users abandon searches because they mistype a proper noun. Implementing robust fuzzy matching helps retain readers who might otherwise leave the site frustrated.
How Voting Works: The Mechanics of Consensus
You might assume that the proposal with the most votes wins. While raw numbers matter, the system is designed to prevent domination by large language communities like English or German Wikipedia. The voting algorithm uses a weighted approach to ensure smaller communities have a say.
Here’s how it functions in practice:
- One Person, One Account: You must log in with a unified account (Single-Sign-On) to vote. Anonymous IPs cannot participate.
- Vote Distribution: You have 20 votes total. You can give all 20 to one proposal or spread them out. However, you can only vote once per proposal.
- Normalization: Votes are normalized based on the size of the community submitting the proposal. A proposal from a small language wiki doesn’t need 10,000 votes to compete with a proposal from the English wiki needing 50,000. This prevents "vote farming" by larger groups.
- Thresholds: Proposals must meet a minimum number of unique supporters to be considered viable. This filters out niche requests that lack broad appeal.
This structure encourages collaboration. Often, users from different languages will rally behind a shared technical issue, boosting the visibility of a problem that affects everyone, regardless of language.
Why Your Vote Matters for MediaWiki Development
The output of this survey feeds directly into the MediaWiki software roadmap. When a proposal wins, it gets assigned to a product manager and a team of engineers. They assess feasibility, estimate development time, and schedule the work.
Consider the impact of the "Better Diff View" proposal. Before recent updates, comparing two versions of an article was difficult if multiple sections changed. The new interface highlights changes side-by-side, making it easier for patrollers to spot vandalism or good-faith errors. This improvement came directly from community pressure during previous wishlist cycles.
If you don’t vote, you’re essentially letting others decide what your digital encyclopedia looks like. Even if you aren’t a power editor, your perspective as a reader is valuable. Readers care about speed, accuracy, and ease of navigation. Those insights drive decisions that affect millions of daily visitors.
Pitfalls and Challenges in the Process
No system is perfect. The Community Wishlist Survey faces criticism for several reasons. First, technical feasibility often clashes with community desire. Just because users want a feature doesn’t mean it’s easy to build within the constraints of legacy code.
Second, there’s the issue of representation. Active voters tend to be tech-savvy long-time editors. Newcomers and casual readers rarely participate, meaning their needs might be underrepresented. To combat this, the foundation sometimes runs targeted outreach campaigns to encourage broader participation.
Finally, implementation delays are common. A proposal might win in April but not see release until the following year due to resource allocation shifts. Patience is part of the contract. The community understands that quality takes time, especially when maintaining stability across hundreds of wikis.
Preparing for the Next Cycle
As we move into late 2026, attention turns to the upcoming Community Wishlist Survey 2026. If you missed the 2025 deadline, don’t worry. The cycle repeats annually. Start thinking about your pain points now. What frustrates you about reading or editing today? Do you struggle with citations? Do you find certain templates hard to use?
Document these issues. Join local meetup groups or online forums to discuss potential proposals. Early engagement helps refine ideas before they hit the formal submission window. Remember, a well-articulated proposal with clear examples is far more likely to succeed than a vague complaint.
Who is eligible to vote in the Community Wishlist Survey?
Any registered user with a confirmed email address on any Wikimedia project can vote. You do not need to be an administrator or have a specific number of edits. However, anonymous users and those without verified emails cannot participate.
Can I submit a proposal if I am not a frequent editor?
Yes. The survey welcomes input from readers, editors, and even developers. If you have an idea that improves the experience, you are encouraged to submit it. The key is to clearly explain the problem and how your proposed solution addresses it.
What happens if my proposal does not win?
Non-winning proposals are not discarded. They are archived and reviewed periodically. Sometimes, a proposal that didn’t win in one year becomes relevant later due to changes in technology or community priorities. Additionally, some features may be implemented independently by volunteer developers outside the official wishlist process.
Are the voting results binding on the Wikimedia Foundation?
While the results strongly influence the product roadmap, they are not strictly binding contracts. The Foundation retains the right to reject proposals if they are technically unfeasible, conflict with legal requirements, or duplicate existing efforts. However, ignoring high-vote proposals consistently can lead to community friction.
How are duplicates handled during the voting phase?
During the vetting phase, similar proposals are merged into a single entry. This consolidates votes and clarifies the scope. If you voted for a proposal that was merged, your vote transfers to the consolidated version. This ensures that fragmented support for similar ideas counts toward a stronger mandate.
