コミュニティ要望調査/更新情報/2022年結果

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

皆さん、こんにちは。

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

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

2022年分の集計結果

投票

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

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

開票結果はコミュニティ要望調査2022年/結果をご参照ください。

優先順位付け

Main article: Special:MyLanguage/Community Wishlist Survey/Prioritization

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. [[Community Wishlist Survey 2022/Editing/Autosave edited or new unpublished article|Autosave edited or new unpublished article