2020年社群願望清單調查
2020年度嘅 ｢社羣願望清單｣ 完咗…… 目前總共有: 72 個建議、423 個人有份參與、1749 票係支持票
以下日子一律以世界協調時當日1800為準
- 提交、討論同修訂提案: 10月21號 – 2019年11月11號
- 由社群技術小組審查同整理提案 （包括咗留畀維基媒體技術會嘅時間設定）: 11月5號 – 2019年11月19號
- 提案投票: 11月20號 – 2019年12月2號
- 公佈結果: 2019年12月6號
哈囉，大家好！
我哋好開心可以分享2020社群技術願望清單調查嘅最新動態。今次亦係我哋嘅第五次年度社區願望清單調查，而喺今年，我哋決定採取第二種嘅方法。喺之前，我哋都係邀請大家為佢哋想見到嘅功能或者修復去寫提案，最高票數嘅十個願望就會交畀社區技術團隊嚟做。今次，我哋就會專注喺非維基百科項目（如：維基書本、維基辭典、維基語錄、維基文庫、維基學府、維基物種、維基遊埠同埋維基新聞），我哋淨係會處理最高票數嘅五個願望。同以往有好大嘅唔同，但係下一年（2021年），我哋就可能回復返傳統嘅格式。
問題嚟喇，點解我哋今年要將格式轉咗呢？咁多年嚟，我哋都一直用緊同一個格式。雖然佢會為我哋帶嚟好多好處，例如，我哋整出咗更方便嘅工具，提供咗有用嘅更改，並且對呢個多元化嘅社區產生咗影響。但係，格式嘅重點性質傾向於目前最大嘅項目（維基百科）。咁樣嘅話，其他比較少嘅項目，就會比較難為佢哋提供服務，而佢哋亦都從未出現喺願望清單入邊。作為社群團隊，我哋希望支持所有嘅項目。因為咁，我哋希望喺2020年，對非維基百科項目做出改善。
另一方面，我哋今次淨係會接收並實行五個願望。幾年之內，我哋都喺度做緊比較大嘅願望（例如頁面自訂喜好同埋邊個寫咗），呢啲都係一啲好好嘅項目。但係同時佢都有一個較長嘅時間去進行研究，同埋將佢做好。2019年嘅願望清單入邊，亦都有好多願望仲未實現。所以我哋希望將2020年嘅願望清單縮短，方便騰出空間去解決更多願望（包括新嘅同埋2019年剩低嘅願望）。
作為一個團隊，我哋用咗些少嘅時間嚟考慮適合今年調查嘅指引。我哋做出咗以下嘅決定：
- 每個願望都應該針對沒有專門團隊嘅非維基百科項目（即維基書本、維基辭典、維基語錄、維基文庫、維基學府、維基物種、維基遊埠同埋維基新聞）。
- 全域項目（即係針對所有維基項目做出）嘅願望，並唔可以作出提案。
- 包括或者僅適用於維基百科嘅願望，並唔可以作出提案。
- 包括維基數據或維基同享嘅願望，並唔可以作出提案。
- 社群技術團隊可以做出佢範圍入邊最後決定，而且佢嘅決定需要同指引保持一致。
點解唔可以有全域項目願望：我哋用咗好多時間嚟討論，係咪應該將全域項目納入可以提交嘅願望入邊。一方面，我哋想去了解大家對全域項目願望嘅渴望。但係另一方面，我哋唔希望全域項目願望佔據咗主要嘅地位，並且破壞咗我哋支持小型項目嘅目的。我哋仲討論咗某啲全域項目願望嘅可能性。整體嚟講，我哋決定，因為今年我哋淨係接受五個願望，我哋唔想再去限制小型項目可以用嘅資源。但係我哋亦都會繼續去解決舊年嘅願望清單，入面嘅全域項目願望（例如，監視列表到期，編輯差異入邊嘅名）。
點解唔可以有維基數據同維基同享嘅願望：因為以下嘅原因我哋決定排除呢兩個項目。首先呢兩個項目都有專門嘅團隊，或者有團隊進行咗重大嘅更改（即係維基數據嘅WMDE團隊；維基同享嘅結構化數據團隊）。但係其他項目就冇專門嘅團隊，我哋亦一直努力，去尋求團隊嘅支持。第二，維基數據同埋維基同享實際上係傾向全域項目，但係唔係2020年願望清單入邊。
呢個可以叫做一場實驗，我哋希望可以喺入面學到嘢。喺來年，我哋就可以同一系列嘅社群互動，之前一啲冇代表性嘅項目，並且鼓勵所有維基友（包括我哋自己），考慮點樣去進一步授權比較細嘅維基項目。另外，我哋都好希望去解決舊年嘅願望清單入邊嘅全域項目願望。最後，我哋想多謝你畀嘅意見，亦都好期待見到你哋嘅提議。多謝！
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.
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 Specialists team.
呢個係我哋第五次嘅年度社群願望清單調查。請睇下舊年願望嘅最新消息！
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 2020. 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, Wikisource editors, 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.
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.
社群技術團隊可能會以唔符合下面嘅標準為理由而拒絕某啲提案：
- 提案應該同技術變更有關，而唔是同方針或者社群變更有關
- 提案應該同問題有關，而唔一定係查詢某啲特定解決方案
- 提案應該係要有充分定義嘅問題，而唔係堆砌各種毫無關聯嘅問題
- 提案唔係系其他團隊嘅路線圖入面，或者冇俾其他團隊拒絕過
- 提案冇俾社群技術團隊拒絕過
- 提案應該要符合團隊的範圍
The Community Tech team may decline proposals that fail to meet the above criteria.
支持投票排名創建一个優先嘅愿望，社群技術團隊會去評估同解决頭5個愿望。要做到呢一點，我哋會睇下所有嘅愿望，並且會參考技術和社會/政策風險因素。
反對票同中立票非常有用於提高潛在嘅負面影響。對於有爭議既願望，我哋會通過更加有共識的審核黎平衡投票。用2015年的調查工作黎做個例子：希望“添加用戶觀察名單中”都收到咗好多嘅選票，但都有收到一啲反對嘅投票。我哋會聽各方嘅意見，決定會唔會繼續呢個項目。
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. Community Tech listened to all sides, and made a decision on whether to pursue the project or not.
The 2020 Community Wishlist Survey is now complete! We want to thank everyone for their participation in this year’s survey. It was a very civil and smooth process, and we appreciate all of the help that we received. Now, we’re delighted to announce the top 5 wishes from the survey:
- Improve export of electronic books (Wikisource)
- New OCR tool (Wikisource)
- Migrate Wikisource specific edit tools from gadgets to Wikisource extension (Wikisource)
- Inter-language link support via Wikidata (Wikisource)
- Insert attestation using Wikisource as a corpus (Wiktionary)
Here’s what comes next: We’ll begin analyzing these five wishes after the new year. During our analysis, we’ll consider various factors, including possible dependencies and risks. Once we’ve completed this analysis, we’ll determine which wish to address first. We’ll create a project page on Meta-Wiki for that wish, which will outline the project vision. We’ll also ping all the wish voters, so everyone can share their suggestions and questions on the Talk page. From that point, updates will be found on the project page. The first project page should be launched in the next few months (no set date yet), but you can visit the Community Tech page for updates in the meantime.
As a team, our goal is to address every top wish in the Community Wishlist Survey. This means that we analyze each wish and determine if it’s workable (i.e., within scope, no major conflicts with other teams, etc). In many cases, the wish is workable. We then continue with the research and planning, followed by development, testing, and deployment. However, we sometimes identify significant issues or risks associated with a wish. In such cases, we investigate alternatives and ways to mitigate the risks. As a last resort, we sometimes decline certain wishes, but only after we rule out other options. Above all, we make sure to address each wish and share our findings with the community.
As this year draws to a close, we want to thank you, again, for participating in the survey! It was a fantastic experience for the team (and we hope for you too!). After the new year, we’ll begin reaching out with plenty of questions, ideas, and updates. We’re excited to begin the work to improve Wikisource and Wiktionary. Until then, we wish you a happy new year, and we look forward to collaborating with all of you!