コミュニティ要望アンケート/更新情報/2022結果

This page is a translated version of the page Community Wishlist Survey/Updates/2022 results and the translation is 64% complete.

Community Wishlist Survey banner - translatable.svg

2022

皆さん、こんにちは。

コミュニティ要望アンケート 2022※1は〆切りました。今年の開催に参加してくださった皆さんのおかげですし、票には現れていなくても特段の活躍をしてくださった皆さんに担当一同より改めて深謝申します。皆さんのご尽力がなければここまで来ることはできませんでした。(※1=Community Wishlist Survey)

それで、次はどうなるの? 今回の投票について優先順位をつける手順、ありあわせて優先課題の順位の確認をぜひどうぞ。

2022年分の集計結果

投票

2022年1月28日から2月11日まで、アカウント保有の貢献者には1月前半にまとめた提案に投票してもらいました。

今回の参加者はおよそ1600名です。 集まった提案は467件、その内訳は過去に提出された分142件、大型案件は55件、参加者の採用投票で可否を決めたものは合計270件です。賛成票の総計は9554票、そのうち 採用投票に8387票が集まりました。皆さん、無事に開票まで進んだことを喜びましょう!

開票結果はコミュニティ要望アンケート2022/結果をご参照ください。

優先順位付け

Community Tech Wishes Prioritization Score 2022.svg

As we wrote on the FAQ page, technical popularity (so the number of votes) is the main factor in the decision which proposals we will be working on. It is an important factor, but not the only one. We assessed the top 30 proposals from three perspectives: technical complexity, product and design complexity, and community impact.

技術的な複雑さ

Our engineers estimate how much effort they would need to put into granting a wish. They prioritize less complex (more workable) projects. Whenever something is not clear, they try to overestimate rather than underestimate.

  • Technical dependency – we check if the work requires interactions with other Wikimedia Foundation teams. It could be that part of the work needs to be on other teams' roadmap or that we need other teams' input or feedback before we can complete the wish. Examples of these are schema changes, security reviews, adding a new extension, and upgrading third-party libraries.
  • Technical research – we ask ourselves if we know how to approach a particular problem. Sometimes we need to evaluate and consider our options before we can start thinking about a solution. Sometimes we need to confirm that what needs to be done can be done or is within what the platform we are working on can handle.
  • Technical effort – we ask ourselves how familiar we are with the underlying code and how big or complex the task can be. A high-effort score could also mean that the code we'll be working with is old, brittle, or has some degree of technical debt that will have to be dealt with before we can start working on our actual task.

プロダクトと設計

Similarly to the assessments above, our designer estimates what effort should be made to complete a project. They prioritize less complex (more workable) projects. Whenever something is not clear, they tries to overestimate rather than underestimate.

  • Design research effort – we seek to understand the level of research needed for each proposal. In this case, the research involves understanding the problem, either at the very beginning through initial discovery work (the scope and details of the project, surveys or interviews with community members), or later in the process through community discussions and usability testing (e.g. how do users contribute with and without this new feature).
  • Visual design effort – a significant number of proposals require changes in the user interface of Wikimedia projects. Therefore, we check to estimate the change of the user interface, how many elements need to be designed and their complexity. For instance, using existing components from our design system or creating new ones, keeping in mind how many states or warnings need to be conceived to help guide users, including newcomers.
  • Workflow complexity – we ask ourselves how does this particular problem interfere with the current workflows or steps in the user experience of editors. For example, a high score here would mean that there are a lot of different scenarios or places in the user interface where contributors might interact with a new feature. It can also mean that we might have to design for different user groups, advanced and newcomers alike.

コミュニティの受ける影響

In contrast to the two perspectives described above, this part is about equity. Practically, it's about ensuring that the majorities aren't the only ones whose needs we work on.

Depending on this score, proposals with similar numbers of votes and similar degrees of complexity are more or less likely to be prioritized. If a given criterion is met, the proposal gets +1. The more intersections, the higher the score. This assessment was added by our Community Relations Specialist.

  • Not only for Wikipedia – proposals related to various projects and project-neutral proposals, are ranked higher than projects dedicated only to Wikipedia. Autosave edited or new unpublished article is an example of a prioritized proposal.
  • Sister projects and smaller wikis – we additionally prioritize proposals about the undersupported projects (like Wikisource or Wiktionary). We counted Wikimedia Commons as one of these. Tool that reviews new uploads for potential copyright violations is an example of a prioritized proposal.
  • Critical supporting groups – we prioritize proposals dedicated to stewards, CheckUsers, admins, and similar groups serving and technically supporting the broader community. Show recent block history for IPs and ranges is an example of a prioritized proposal.
  • Reading experience – we prioritize proposals improving the experience of the largest group of users – the readers. Select preview image is an example of a prioritized proposal.
  • Non-textual content and structured data – we prioritize proposals related to multimedia, graphs, etc. Mass uploader is an example of a prioritized proposal.
  • Urgency – we prioritize perennial bugs, recurring proposals, and changes which would make contributing significantly smoother. Fix search and replace in the Page namespace editor is an example of a prioritized proposal.
  • Barrier for entry – we prioritize proposals about communication and those which would help to make the first contributions. Show editnotices on mobile is an example of a prioritized proposal.

項目と得点表

These scores may change when we start working on the proposals. As we explained above, we have tried to overestimate rather than underestimate. Check out the proposals, in order of prioritization:

要望 一般性の順位 集票 技術の値 プロダクトと設計の値 コミュニティの受ける影響度 優先順位の数値
Autosave edited or new unpublished article 29 69 1.0 0.3 2 2.66
Get WhatLinksHere's lists in alphabetical order 22 74 1.3 0.3 2 2.63
Enable negation for tag filters 26 71 2.0 0.3 2 2.47
Fix search and replace in the Page namespace editor 11 93 2.3 0.7 2 2.47
Improve SVG rendering 5 108 4.0 0.8 3 2.44
Notifications for user page edits 2 123 1.3 1.7 1 2.38
Check if a page exists without populating WhatLinksHere 14 89 2.7 0.7 2 2.38
Tool that reviews new uploads for potential copyright violations 4 109 4.3 2.7 4 2.21
IPA audio renderer 9 97 3.0 2.7 3 2.15
floating table headers 24 73 1.0 2.7 2 2.14
Mass-delete to offer drop-down of standard reasons, or templated reasons. 25 72 1.0 2.7 2 2.14
Formatting columns in table 19 77 4.0 0.3 2 2.11
Select preview image 8 100 3.0 2.0 2 2.07
Add DeepL as a machine translation option in ContentTranslation 20 75 3.3 0.0 1 2.06
Change default number of search results displayed 12 92 2.0 1.7 1 2.05
Better diff handling of paragraph splits 1 157 3.3 2.3 1 2.04
Table sorting on mobile 17 83 2.3 1.7 1 1.92
Enhanced Move Logs 10 96 2.7 2.3 1 1.79
Gadget: Who is active 26 71 1.3 4.0 2 1.76
Show recent block history for IPs and ranges 3 120 4.0 3.7 2 1.61
Reminders or edit notifications after block expiration 20 75 3.3 3.2 2 1.57
Autosuggest linking Wikidata item after creating an article 12 92 3.3 3.8 2 1.53
Full page editing 30 67 2.0 3.7 1 1.42
Allow filtering of WhatLinksHere to remove links from templates 6 106 5.0 3.3 2 1.40
Automatic duplicate citation finder 6 106 3.0 4.2 1 1.36
VisualEditor should use human-like names for references 22 74 3.3 4.0 1 1.12

In addition, if you are interested in viewing a more granular version of the sub-components that make the prioritization scores, we've made the individual sub-components public:

These are proposals which we found will be worked on by other teams at the WMF or third-party open source when we went through the process of estimating their complexities:

製品チームの他の班へタスク割り振り
要望 一般性の順位
Deal with Google Chrome User-Agent deprecation 15
Show editnotices on mobile 15
Categories in mobile app 18
Mass uploader 28

規模が大きめのご指摘

Thank you for 55 Larger suggestions, nearly 1200 votes you cast for them, and all the comments you added! You dedicated a lot of time, and this is a huge amount of important knowledge for us.

このカテゴリを使った理由と、次にこれをどうする予定か?

From the beginning in 2015, we have been explaining that the Community Wishlist Survey has a specific scope. Not every good proposal submitted in the first phase can become our project. We avoid committing to something we cannot do.

At the same time, it is impossible (and not fair!) to expect that submitted proposals that were great ideas but out of our scope should end up in the Archive. In past editions, we archived proposals not meeting the criteria before voting. This time, we decided to create the "より大きな提案" category and put it next to the regular categories. We wanted to respect the effort put into submitting them, and allow you to express your interest in these projects even if we won't be able to work on them. To avoid misconceptions, we didn't put the larger suggestions onto the Results page.

Now, having these suggestions and votes, we will be able to understand your needs better. We will share the results with our leaders and colleagues at the Product department of the Wikimedia Foundation. We can't promise they will work on these projects soon. They will be informed, though, and perhaps will be inspired when making their plans.

謝意

Shout Of Gratitude.jpg

We would like to express our deepest gratitude to all participants. The Community Wishlist Survey is your success as well.

Some of you helped us to improve the Survey before it began. Some spent an outstanding number of hours during the Survey. They were translating the documentation and the proposals, discussing the proposals, and encouraging others to take part. Some decided to take part for the first time, and among them, there were some who affected the final results in a way no one could have expected.

We are not able to make a full list of everyone who deserves to be mentioned here. Heartfelt appreciation to everyone who helped us on social media, within their own communities, and was less likely to be noticed by us.

  • MaxEntKwguldenD-KuruAleatoryPonderingsおよび Toadspike – 提案のまとめと提出に対して。 全員、初めての参加であり、提案5件は最終的にいずれも優先課題トップ10に残りました!
  • IznoTheDJおよびXaosflux – 提案の技術的評価における助力に対して
  • Putnik – 投票ガジェットの修正に関して
  • Dušan Kreheľ – 集票システムのバグを発見し報告したことに対して
  • 리듬 – 韓国語への1千単位超の翻訳に対して。
  • Pols12 – フランス語への翻訳およびよくある質問ページの改善への示唆に対して。
  • АтаSabelögaWargoDaud I.F. ArganaEdu!Bjankuloski06KaganerStangMohammad ebzEuro knowVamiMiroslav Ličkoআফতাবুজ্জামানSaederup92およびDr-Taher – 以下の多言語への翻訳作業に対して。ウクライナ語、スウェーデン語、ポーランド語、インドネシア語、ブラジルポルトガル語、、マケドニア呉、ロシア語、中国語、ペルシャ語、ヘブライ語、エスペラント、チェコ語、ベルガル語、デンマーク語、アラビア語
  • Minorax1234qwer1234qwer4 – 多言語による翻訳を呼びかけた貢献に対して
  • ウィキメディア・コロンビア協会、同イタリア協会はじめSNSで今回の投票を広報した協会の一覧
  • 提案が実行可能性かどうか評価するため、WMFの他のチームにはそれぞれの視点から助言を受けました。

次の機会に向けた提案がしたい

……それに忘れないうちになんとかしたい場合は、こちらのサンドボックスに投稿してください。そこに保存された提案は、正式な提案としては扱いませんが、読んだ人の頭に残るしおそらくは忘却されないはずです。

フォローはこちら

English cocker Jam.jpg

お疲れさまでした!

コミュニティ技術チーム一同—Natalia、Karolin、Dayllan、MusikAnimal、Sam、Harumi、Szymon、Nicolas、Dom、Ima、James –