Опитування побажань спільноти 2017

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search
This page is a translated version of the page Community Wishlist Survey 2017 and the translation is 6% complete.

Outdated translations are marked like this.
Other languages:
Bahasa Indonesia • ‎Bahasa Melayu • ‎British English • ‎Deutsch • ‎English • ‎Jawa • ‎Tiếng Việt • ‎Türkçe • ‎asturianu • ‎català • ‎dansk • ‎español • ‎euskara • ‎français • ‎hrvatski • ‎italiano • ‎magyar • ‎polski • ‎português do Brasil • ‎suomi • ‎svenska • ‎čeština • ‎Ελληνικά • ‎Кыргызча • ‎беларуская (тарашкевіца)‎ • ‎български • ‎македонски • ‎русский • ‎српски / srpski • ‎українська • ‎עברית • ‎العربية • ‎فارسی • ‎مصرى • ‎বাংলা • ‎தமிழ் • ‎ಕನ್ನಡ • ‎ไทย • ‎မြန်မာဘာသာ • ‎ქართული • ‎中文 • ‎日本語 • ‎ꯃꯤꯇꯩ ꯂꯣꯟ • ‎한국어

Magic Wand Icon 229981 Color Flipped.svg Опитування побажань спільноти 2017 завершилося. Magic Wand Icon 229981 Color Flipped.svg

Ось результати Опитування побажань спільноти 2017!

Загалом: 214 пропозицій, 1137 дописувачі, 6613 голосів на підтримку

Переглянути випадкову пропозицію

Натисніть на категорію, щоб переглянути пропозиції

Адміни і стюарди
13 пропозицій
Протидія переслідуванням
3 пропозицій
Боти і гаджети
10 пропозицій
5 пропозицій
25 пропозицій
27 пропозицій
Мобільний перегляд та застосунки
18 пропозицій
Мультимедіа та Вікісховище
29 пропозицій
Програми і події
2 пропозицій
13 пропозицій
8 пропозицій
Списки спостереження
15 пропозицій
29 пропозицій
9 пропозицій
8 пропозицій


  • Подача, обговорення та розгляд пропозицій: Nov 6–20, 2017
  • Community Tech reviews and organizes proposals: Nov 20–26
  • Голосування за пропозиції: Nov 27–Dec 11
  • Публікація результатів: Dec 15
  • Перегляд та початкове оцінювання командою Community Tech побажань, що набрали найбільше підтримки: кінець грудня
  • Презентація оцінки: початок січня 2018
  • Робота над побажаннями: січень—грудень 2018!


Технічна команда (Community Tech) — команда Фонду Вікімедіа, що зосереджується на задоволенні потреб активних дописувачів Вікімедіа у покращених інструментах спостереження і модерування. Проекти, над якими ми працюємо, визначаються спільнотою Вікімедіа через щорічне Опитування побажань спільноти.

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 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 Community Relations team.

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!


Quite a few! Here's the status on our work so far this year:

2009 Christmas Kokopuff.JPG


Талісман Community Tech: собака в шапці Санти.

The proposal phase is the first two weeks of the survey.

In the proposal phase, contributors from every project and language can submit proposals for features and fixes that you'd like to see in 2017. Proposals may be submitted in any language. If you submit a proposal in a language other than English, we will attempt to get it translated so everyone can read and vote on it more easily.

Proposals should be discrete, well-defined tasks that will directly benefit active Wikimedia contributors. Proposals should answer the following questions:

  • Яку саме проблему ви хочете вирішити?
  • Яких користувачів це зачіпає? (редактори, адміни, користувачі Вікісховища, користувачі Вікіпедії тощо)
  • Як з цією проблемою обходяться зараз?
  • Які запропоновані рішення? (якщо є якісь ідеї)

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 account. If you post more than three proposals, we'll ask you to narrow it down to three. Bring your best ideas!

Similarly, only registered users can make proposals to ensure they can watchlist the discussion and respond to questions. Just as with voting, you should be an active editor on at least one Wikimedia project. If you do not meet this criteria, or you have hit your proposal limit but have more ideas, you can seek other users to adopt your proposals.

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, you may submit some proposals that didn't get enough support votes in past years, 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.


Aldino per Natale.jpg

After the proposal phase, we take a break to review the proposals before the voting phase begins.

All active contributors can review and vote for the proposals that they want to support. You can vote for as many different proposals as you want. To ensure fair voting, only registered users can vote, and votes by very new accounts may be removed.

The only votes that are counted are Support votes. The final list of wishes will be ranked in order of the most Support votes. If you are the proposer, a support vote is automatically counted for your proposal.

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.

Having smaller projects' proposals in the Wishlist Survey is important — it helps our team and the Wikimedia Foundation broadly know what people in smaller groups need. So yes, please come and post your proposals, even if you don't think you'll get into the top 10!

Here are some projects that we worked on in 2017:

  • For English WP New Pages Patrol: ACTRIAL research, related to Wish #14: Article Creation Workflow


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.


Every dog that wears a Santa hat works for Community Tech.

... замість того, щоб зайнятися питаннями після десятого з результатів опитування минулого року?

Основною причиною того, чому ми робимо такі опитування щорічною подією, є наше бажання залучити більше людей! Тепер більше людей знають про команду й опитування, і через рік, коли основні побажання вже будуть виконані, ми очікуємо, що люди будуть ще більш зацікавленими й охочими взяти участь в такому опитуванні. Ми хочемо дати шанс кожному висловити нові ідеї.

Якщо є побажання з опитування минулого року, які на Вашу думку заслуговують другого шансу, дивіться «[[[[#resubmit|Translations:Community Wishlist Survey/section-resubmit/56/uk]]|Чи можу я повторно подати пропозицію з минулорічного опитування?]]» вище.