2019年社群願望清單調查

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 2019 and the translation is 100% complete.

Other languages:
Bahasa Indonesia • ‎Bahasa Melayu • ‎Basa Jawa • ‎British English • ‎Deutsch • ‎English • ‎Esperanto • ‎Gaeilge • ‎Nederlands • ‎Tiếng Việt • ‎Türkçe • ‎asturianu • ‎azərbaycanca • ‎català • ‎dansk • ‎eesti • ‎español • ‎euskara • ‎français • ‎galego • ‎hrvatski • ‎italiano • ‎lietuvių • ‎magyar • ‎norsk bokmål • ‎occitan • ‎polski • ‎português • ‎português do Brasil • ‎română • ‎suomi • ‎svenska • ‎čeština • ‎Ελληνικά • ‎беларуская (тарашкевіца)‎ • ‎български • ‎македонски • ‎монгол • ‎русский • ‎српски / srpski • ‎українська • ‎עברית • ‎العربية • ‎سنڌي • ‎فارسی • ‎हिन्दी • ‎বাংলা • ‎মেইতেই লোন্ • ‎ਪੰਜਾਬੀ • ‎தமிழ் • ‎മലയാളം • ‎ไทย • ‎ဖၠုံလိက် • ‎ქართული • ‎中文 • ‎日本語 • ‎粵語 • ‎한국어


Magic Wand Icon 229981 Color Flipped.svgThe 2019 Community Wishlist Survey is over...Magic Wand Icon 229981 Color Flipped.svg
Here are the Community Wishlist Survey 2019 results!

Total: 212 proposals, 1387 個貢獻者, 7282 support votes

睇下隨機提案

分類
撳一個分類黎睇下入邊啲提案。

Admins and patrollers
15 proposals
防止騷擾
4 proposals
機械人同小工具
10 proposals
分類
12 proposals
引用
13 proposals
編輯
27 proposals
Maps
13 proposals
雜項
17 proposals
移動版同應用程式
12 proposals
多媒體同共享資源
20 proposals
Notifications
4 proposals
方案同活動
2 proposals
閲讀
8 proposals
搜尋
6 proposals
Watchlists
12 proposals
Wikidata
19 proposals
Wikisource
11 proposals
Wiktionary
7 proposals

 

All phases of the survey begin and end at 18:00 UTC.

  • 提交、討論同修訂提案: 2018年10月29號至11月11號
  • 社群技術審查同組織提案: 2018年11月13號至11月15號
  • 提案投票: 2018年11月16號至11月30號
  • 結果公佈: 2018年12月3號

 

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 primarily 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 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.

呢個係我哋第四次嘅年度社群愿望清单调查。请睇下舊年愿望嘅最新消息

 

我哋每年年底都喺度堅持調查,但我哋次次都喺第二年先開始喺呢啲願望上面做嘢,有時仲會拖到第三年添。噉樣導致人哋以為我哋喺2016~2017年間嘅願朢清單調查入邊做嘢,而而家我哋已經喺2018年,要忽略呢種誤解,而且可以令我哋喺今年做嘢期間感到心態良好,我哋決定將調查年份重命名為第二年,即係2019年,而唔係調查進行嘅今年。

 

The Community Tech mascot: a dog wearing a Santa hat.

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 2019. 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:

  • 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 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!

 

社群技術團隊可能會以唔符合下面嘅標準為理由而拒絕某啲提案:

  • 提案應該同技術變更有關,而唔是同方針或者社群變更有關
  • 提案應該同問題有關,而唔一定係查詢某啲特定解決方案
  • 提案應該係要有充分定義嘅問題,而唔係堆砌各種毫無關聯嘅問題
  • 提案嘅工作量對社群技術團隊合適,方便同其它頭10願望一齊做
  • 提案唔係系其他團隊嘅路線圖入面,或者冇俾其他團隊拒絕過
  • 提案冇俾社群技術團隊拒絕過
  • 提案應該要符合團隊的範圍

 

支持投票排名創建一个優先嘅愿望,社群技術團隊會去評估同解决頭10個愿望。要做到呢一點,我哋會睇下所有嘅愿望,並且會參考技術和社會/政策風險因素。

反對票同中立票非常有用於提高潛在嘅負面影響。對於有爭議既願望,我哋會通過更加有共識的審核黎平衡投票。用2015年的調查工作黎做個例子:希望“添加用戶觀察名單中”都收到咗好多嘅選票,但都有收到一啲反對嘅投票。我哋會聽各方嘅意見,決定會唔會繼續呢個項目。

 

每一隻戴住聖誕帽嘅狗都為社群技術團隊努力做野。

……而唔係著手去年嘅調查中,除了頭10以外的嘅每一個項目?

我哋每年做一次調查嘅原因你我哋希望更多嘅人加入!而家更多嘅人瞭解左呢個團隊同呢個調查,而且一年之後大部分排係前面嘅愿望已經完成,我哋希望每個人都更加對參與呢個調查更加感興趣同激動。我哋想俾每個人一個帶黎新想法嘅機會。

如果舊年的调查入面有您覺得好值得再次提出嘅話,請睇下上面嘅“我可唔可以提交以往調查嘅提案?”。