2017 Community Wishlist Survey
Total: 214 proposals, 1137 contributors, 6613 support votes
- Submit, discuss and revise proposals: Nov 6–20, 2017
- Community Tech and Technical Collaboration review and organize proposals: Nov 20–26
- Vote for proposals: Nov 27–Dec 11
- Results posted: Dec 15
- Screening and assessment of top wishes by Community Tech team: End of December
- Presentation of the initial assessment: Early January 2018
- Working on wishes: January–December 2018!
The Community Tech team is a Wikimedia Foundation team focused on the needs of active Wikimedia contributors for improved curation and moderation tools. The projects that we work on are decided by the Wikimedia community, through the annual Community Wishlist Survey.
Once a year active Wikimedia contributors can submit proposals for features and fixes that you'd like our team to work on. After two weeks, you can vote on the ideas that you're most interested in. The top 10 wishes will be investigated and addressed by the Community Tech team. Some of the other top wishes may be addressed by other development teams.
This is our third annual Community Wishlist Survey. See 2016 Community Wishlist Survey/Status report 1 for the latest info on last year's wishes!
We held our second Community Wishlist Survey in November and December 2016, and in 2017, we've been working on the top 10 wishes. This survey process was developed by Wikimedia Deutschland's Technical Wishes team, who run a wishlist survey on German Wikipedia. The international wishlist process is supported by the Technical Collaboration team.
Quite a few! Here's the status on our work so far this year:
- Wish #2: Edit summary length for non-Latin languages – MediaWiki Platform team is deploying the necessary database changes. There are a few more steps; we expect the wish to be completed by the end of the year.
- Wish #3: Section heading URLs for non-Latin languages – Done.
- Wish #4: Global preferences – Currently in active development; we expect this to be completed by the end of the year.
- Wish #5: Rewrite XTools – Live at xtools.wmflabs.org.
- Wish #6: Wikitext editor syntax highlighting – Live as beta feature on left-to-right language wikis. We’re still working on right-to-left languages.
- Wish #7: Warning on unsuccessful login attempts – Live on all wikis, see Preferences/Notifications to change defaults.
- Wish #9: Fix Mr. Z-bot's popular pages bot – Live on the English Wikipedia, see WikiProject Spiders/Popular pages for an example.
- Wish #10: User rights expiration – Completed by volunteer developer This, that and the other.
The proposal phase is the first two weeks of the survey, from November 6th to 19th, 2017.
In the proposal phase, contributors from every project and language can submit proposals for features and fixes that you'd like to see in 2018. Proposals may be submitted in any language. If you are comfortable writing in English, that makes it easier to get feedback from the Community Tech team and other editors.
Proposals should be discrete, well-defined tasks that will directly benefit active Wikimedia contributors. Proposals should answer the following questions:
- What is the problem that you want to solve?
- Which users are affected? (editors, admins, Commons users, Wikipedia users, etc.)
- How is this problem being addressed now?
- What are the proposed solutions? (if there are any ideas)
Your proposal should be as specific as possible, especially in the problem statement. Don't just say that "(x feature) is out of date", "needs to be improved" or "has a lot of bugs". That's not enough information to figure out what needs to be done. A good proposal explains exactly what the problem is, and who's affected by it. It's okay if you don't have a specific solution to propose, or if you have a few possible solutions and you don't know which is best.
Submitting a proposal is just the beginning of the process. The two-week proposal phase is a time that the community can collaboratively work on a proposal that presents the idea in a way that's most likely to succeed in the voting phase. When a proposal is submitted, everyone is invited to comment on that proposal, and help to make it better—asking questions, and suggesting changes. Similar proposals can be combined; very broad proposals should be split up into more specific ideas. The goal is to create the best possible proposal for the voting phase.
The person who submits a proposal should expect to be active in that discussion, and help to make changes along the way. Because of that, we're going to limit proposals to three per person. If you post more than three proposals, we'll ask you to narrow it down to three. Bring your best ideas!
One more note: Proposals that call for removing or disabling a feature that a WMF product team has worked on are outside of Community Tech's possible scope. They won't be in the voting phase.
Yes, there are definitely some worthwhile proposals that didn't get enough support votes last year, and deserve a second try.
If you decide to copy a proposal from the old survey into the new survey, we expect you to "adopt" that proposal—meaning that you'll be actively participating in the discussion about that idea, and willing to make changes to the proposal in order to make it a stronger idea when it moves to the voting phase. As we said above, there's a limit of three proposals per person, and posting a proposal from last year counts.
It's helpful if you want to post a link to the previous discussion, but please don't copy over the votes and discussion from last year. If there are good points that people made in last year's discussions, include the suggestions or caveats in the new proposal.
After a week's break, the voting phase happens over next two weeks—from November 27th to December 10th.
All active contributors can review and vote for the proposals that you want to support. You can vote for as many different proposals as you want.
The only votes that are counted are Support votes. The final list of wishes will be ranked in order of the most Support votes.
However, lively discussion is encouraged during the voting phase. If you want to post an Oppose or Neutral vote with a comment, then feel free to do so. These discussions can help people to make up their mind about whether they want to vote for the proposals. The discussions also provide useful input to guide the work that will happen through the year.
A reasonable amount of canvassing is acceptable. You've got an opportunity to sell your idea to as many people as you can reach. Feel free to reach out to other people in your project, WikiProject or user group. Obviously, this shouldn't involve sockpuppets, or badgering people to vote or to change their vote. But a good-faith "get out the vote" campaign is absolutely okay.
It's common that most of the proposals that end up in the top 10 are for the biggest projects—the big Wikipedias, and Commons. There are many smaller groups and projects that don't have enough "voting power" to boost their proposal into the top 10, but are doing important work for our movement.
Our team has a commitment to work on projects that help out smaller groups, including campaign and program organizers, GLAM participants, smaller projects like Wikisource and Wiktionary, and stewards and CheckUsers. Here are some projects that we worked on in 2017:
- For Wikisource: Internet Archive Upload tool
- For grant recipients: Grant metrics tool
- For admins and checkusers: Range contributions
- For admins: Cookie blocking
- For English WP New Pages Patrol: ACTRIAL research, related to Wish #14: Article Creation Workflow
Having smaller projects' proposals in the Wishlist Survey is important—it helps our team know what people in smaller groups need, and other teams use these as well, like the WMDE Technical Wishes team, and Community Tech's Anti-Harassment Tools team. So yes, please come and post your proposals, even if you don't think you'll get into the top 10!
The Support-vote rankings create a prioritized backlog of wishes, and the Community Tech team is responsible for evaluating and addressing the top 10 wishes. To do that, we investigate all of the top wishes, and look at both the technical and social/policy risk factors.
The Oppose and Neutral votes are very helpful in raising potential downsides. For controversial wishes, we balance the voting with a more consensus-based review. As an example, this worked in the 2015 survey: The wish to "add a user watchlist" received a lot of votes but also some heartfelt Oppose votes. We listened to all sides, and made a decision on whether to pursue the project or not.
... instead of addressing every item from #11 to 230 from last year's survey?
The main reason why we're making the survey an annual event is that we want to include more people! More people know about the team and the survey now, and after a year where many of the top wishes were completed, we're expecting that people will be even more interested and excited about participating. We want to give everyone a chance to bring new ideas.
If there are wishes from last year's survey that you think deserve another shot, see "Can I resubmit a proposal from the 2016 survey?" above.
||This page or project is maintained by Community Tech.