社群願望清單/近況更新
December 1, 2025: Results of our last Wishathon sprint
Hello everyone! We wanted to share with you the results of the recently closed “Wishathon”, our internal hackathon organized by Community Tech to help fulfill more wishes from Community Wishlist.
The second Wishathon of 2025, which ran from Monday 17 to Friday 21 November, engaged 13 Wikimedia Foundation staff members to help fulfill more wishes, and also foster cross-team and cross-departmental collaboration.
15 patches were written during the week, and 5 have been merged. This allowed us to grant one wish from the community ("Preview page with this template" should not work with pages that do not transclude the template), and to have a clearer path ahead for three more. We may consider these again in the future, given what we learned.
These are the wishes we worked on:
- Revamping the page navigation (phab:T410338), thanks to Dayllan Maza, Cormac Parle and Katie Filbert
- Edit introduction instead of the entire article (phab:T2156), thanks to Sam Wilson and Bárbara Martínez
- "Preview page with this template" should not work with pages that do not transclude the template (phab:T279736), thanks to Tim Starling, Sam Wilson and Santiago Faci
- Allow editors to subscribe to community wishes (phab:T406286), thanks to MusikAnimal
- Make the Chart extension beginner-friendly (phab:T393637, phab:T401990 and phab:T401719), thanks to Clare Ming, Harumi Monroy, Katie Filbert and MusikAnimal
- Improve notification of edit conflicts (phab:T329975), thanks to Adam Baso
As it usually happens, wishes are very different in complexity and feasibility, so in some cases (such as the template preview wish) we were able to resolve all of it, while in others (such as the Charts extension wishes or the editing the introduction wish) we could only do some improvements without resolving it completely. Our work will be used to guide the direction of teams in this regard. Feel free to subscribe to the wishes to get more updates or ask Sannita (WMF) for more information.
September 25, 2025: A new extension for the Community Wishlist
Hello everyone! We are happy to announce that we will deploy the new Community Wishlist extension on October 1! We hope this extension and the upcoming improvements will help you in submitting and translating your wishes to the Community Tech team, while also streamlining the influx of new wishes and navigation of the Wishlist.
The new extension comes with an updated intake form that will standardise the way wishes are categorised. We have introduced a concept called “tags”, which are keywords or phrases that associate a wish with a high-level concept. This essentially brings back the “Categories” that users may remember from the Community Wishlist Survey of years past. The older “Projects” field for wishes will be removed and replaced with tags.
As requested by the community in many instances, and as we already announced, it will be possible to support individual wishes again. This will help WMF teams prioritize their work when assigning a wish to a new or existing focus area, and choosing a new focus area to work on.
Another notable change is we will no longer be using the wish title as part of the page title. We’ve learned that wishes and their meanings can evolve, but moving pages to reflect the change in meaning isn’t particularly easy, and in some cases it is impossible. Instead, we will assign autogenerated IDs to each wish and focus area, i.e. W1, W2, W3, and FA1, FA2, FA3, etc. This is similar to how Phabricator and Wikidata work. This way, links to a particular wish or focus area are guaranteed to always be the same.
Browsing through wishes will now be done using pagination, as opposed to having all wishes listed on one long page. You will be able to sort by vote count, title, and creation date. The old system, which was powered by a bot, will be permanently retired. There will be a brief period of downtime while the extension is deployed and wishes are migrated to the new system.
Wishes will continue to be grouped and assigned, after review, to focus areas, by identifying the common themes across wishes. This will help teams to see if they can address related issues which could significantly improve your editing experience.
Within a week or two following deployment, we will add the ability to filter the existing wishes by status, tags and focus areas.
We hope this new extension will be welcomed by you, and we are interested in your feedback. This will be the first part of a series of new releases regarding the Wishlist, so stay tuned for other changes. Please do not hesitate to contact us in our talk page, and share with us your thoughts! We hope that you appreciate the changes we’re making based on your feedback, and that you want to continue being part of this process together with us.
Also, we remind you that we are collecting feedback around our next feature, Watchlist labels (formerly known as “Multiple watchlists”). We already have announced in the last update that we were looking for feedback regarding how watchlists and recent changes pages are used across projects, and we are still looking for input from you! In particular, we are interested in knowing how users would want to create multiple watchlists, and what each watchlist might be used for.
Thank you in advance for your help!
August 21, 2025: Back from Wikimania and next steps
Hello everyone! We’re back from Wikimania, where we had a presentation about the Community Wishlist. You can read our slides and follow the recording of our presentation on Wikimedia Foundation’s official channel.
We were also pleased to notice that our work of the last months was well received by people at Wikimania, and by the Wikimedia community at large: we had users with extended rights thanking us for our work on Multiblocks, and we noticed that the number of users adopting the Favourite Templates feature is rising. Right before Wikimania, on August 4, 3,916 users were using the feature, with 591 users adopting more than 5 favourites.
As we are back from Wikimania, we are now fully working on the deployment of the new Community Wishlist extension, which will likely be deployed at the beginning of September. The new extension will allow users to add tags to their wishes to better categorise them, and (in a future iteration) to filter them by status, tags and focus areas. It will be possible to support individual wishes again, as requested by the community in many instances. This may help the CommTech team to prioritize a wish within a focus area.
In order to ensure a connection between community wishes and WMF Annual Plan, and allow for a better prioritization of developers’ work, WMF staff will review and assign statuses to incoming wishes on an ongoing basis, and every three months statuses will be re-assessed in their product domains, to create focus areas, and prioritize the work as necessary. You can consult the current documentation on MediaWiki.
Lastly, in the upcoming weeks we will start working on our next feature: Multiple watchlists under the Task Prioritization focus area. We already have announced in the last update that we were looking for feedback regarding how watchlists and recent changes pages are used across projects, and we are still looking for input from you! In particular, we are interested in knowing which filters you use to select relevant edits, when doing your activities. What is considered best for patrolling, for example?
Thank you in advance for your help!
2025年7月24日:監視清單和近期變更頁面
Hello everyone! The Community Tech team is looking for feedback on a critical aspect of Wikipedians’ day-by-day activities – Watchlists and Recent Changes pages – and we’ve captured a lot of requests via the Task Prioritization focus area.
Watchlist (on larger wikis) and Recent Changes (on smaller wikis) are critical surfaces that are the “first stop” on Wikipedia, and for some users are the powerful landing pages when editing (see the findings of our latest report). Their feed receives regular review from many users, ranging from quick scans to extremely thorough explorations. Administrators, patrollers and established users rely on their watchlist as their main way to follow pages they care about—whether for governance, content, or communications tasks. Still, these pages have largely been untouched throughout the years, and volunteers often feel like they’re an “overflowing inbox.”
As we received lots of wishes pertaining to this focus area, we decided to make it into our main focus for the upcoming months. Our goal in this effort is to increase the click-through rate from watchlist to an edit. To achieve this goal, we initially want to focus on a core problem: watchlists can be overwhelming for editors with 100+ watched items, and they need ways to “break” their watchlists into component parts. We’ve seen at least 5 wishes that speak to this core issue. We also heard volunteers ask for better filtering mechanisms, performance improvements, and ability to view diffs in their watchlists.
We recognise that those two pages are the starting point of many wikipedians in their moderation activities, and we want to make them a better place to find the edits that need review. We also recognise that there are a plurality of use cases for watchlists and Recent Changes pages, so we need to balance the needs of users with less than 100 items in their watchlists and more than 100. Lastly, we will be facing substantial technical constraints that we will need to take into account when working on your wishes, which we are prioritizing in this quarter and the next.
We welcome you to review the task prioritization focus area and, if another idea comes to mind on how to improve recent changes or watchlist, we suggest you submit a wish!
2025年6月18日:願望松衝刺的成果
大家好!我們想跟各位分享近期落幕的「願望松」(Wishathon)的成果。「願望松」是我們內部的黑客松,由社群技術團隊舉辦,旨在幫助實現更多社群願望清單中的願望。
願望松活動從5月19日(一)開始至5月23日(五)結束,吸引維基媒體基金會職員參與,幫助實現了更多願望,同時也促進了跨團隊跨部門的合作。
本週共編寫了22個補丁,其中4個已合併。這讓我們實現了三個社群願望,而且我們也對另外五個願望有了更明確的方向。
這次願望松實現了以下願望:
- 提交補丁,實現了設定監視清單的預設到期日的功能(phab:T265716;感謝This, that and the other、MusikAnimal和Susana Cardenas Molinar)
- 修復了編輯預覽的重新載入按鈕遮擋導覽框的「[展開/合併]」按鈕的錯誤(phab:T315894,以及需先修復的phab:T394078;感謝Sam Wilson和Joydeep Sengupta)
- 提交了七個的CSS過濾器補丁(phab:T324526、phab:T394619、phab:T277755、phab:T360725、phab:T368089、phab:T293633、phab:T371809),目前正等待Code Review,另外還有幾個想法有待評估(phab:T394963、phab:T394964;感謝Tim Starling和MusikAnimal)
除此之外,我們還對以下工單和願望做了一些努力:
- 改進了翻譯在願望討論頁的運作方式(phab:T295862和phab:T363306;感謝Nik Gkountas和Joydeep Sengupta)
- Realising a functional prototype to select templates by categories, related to Template recall and discovery (phab:T392553, thanks to Sam Wilson)
- 完成了設計和開發中的實作,以改造頁面導覽的分頁方式(phab:T394637,感謝Michelle Horsey和Bárbara Martínez)
- 改進了維基媒體面板的模組(感謝Arina Igumenshcheva、Dayllan Maza、Harumi Monroy、Jack Wheeler、Julieta Fernandez和Katherine Graessle)
As you can see, wishes are very different in complexity and feasibility, so in some cases (such as the “[show/hide]” dropdown button and the CSS sanitizer) we were able to resolve all or at least most of the it, others (such as the Wikimedia Dashboard modules) are more experimental in nature, and we could only do some improvements without resolving it completely. Our work will be used to guide the direction of teams in this regard.
2025年5月14日:多重封鎖、收藏模板、即將推出的願望清單改進
2023年社群願望清單調查中排名第14位的多重封鎖已順利部署至4個維基站點(波蘭語、德語、義大利語和希伯來語維基百科),並將依以下排程持續大批部署至更多維基站點:所有非維基百科專案以及加泰羅尼亞語維基百科將於5月26日當週部署,其餘維基百科將於6月2日當週部署。參見Phabricator上的部署時間表。
有了多重封鎖,管理員可獲得更多封鎖選項:全站封鎖和部分封鎖可同時實施,並設定不同期限。如此一來,就不需要等到其中一筆封鎖到期才實施另一筆封鎖。管理員可能想要先對破壞性使用者實施臨時全站封鎖,然後再繼續限制其編輯特定頁面或命名空間。這在需要防止維基人大量編輯特定命名空間或頁面時可能很有用。
We are also working on Favourite Templates, a new feature that was suggested by several users, that will provide a better way for new and experienced contributors to recall and discover templates via the template dialog. We hope this will increase dialog usage and the number of templates added.
Since 2013, experienced volunteers have asked for a more intuitive template selector, exposing popular or most-used templates on the templates dialog. At this stage of work, we are focusing on allowing users to put templates in a “favourite” list, so that their reuse will be easier. We are currently exploring additional ways to help users discover or find templates, and welcome your ideas and feedback.
We will involve Polish and Arabic Wikipedias for piloting this new feature, and we are already evaluating involving other projects for a second phase of piloting. We will keep you posted about this.
最後,我們正在對願望清單做以下幾點改進:
- 我們正在探索新的方式來更新重點領域和願望的狀態,讓使用者更容易理解;
- 應要求,我們將以更好的方式分類願望,此外,我們將依建立日期排序願望,方便使用者瀏覽;
- 最後一點,我們將於未來數月內(可能是2025年7月—9月)推出讓使用者對個別願望表達支持的方式,而不僅限對重點領域。
We also want to discuss one more consideration for the Wishlist, which we’d like your input. As WMF product teams and developers work off Phabricator to prioritize tasks, some teams have asked for a tighter integration between the Wishlist and Phabricator, so they can evaluate wishes and Phabricator tasks when they prioritize work. We’ve evaluated the data, and approximately 30% of wishes have a Phabricator task already. What is the ideal relationship between the Wishlist and Phabricator, and how should that be represented?
2025年3月12日:「多重封鎖」試行
2023年社群願望清單調查中排名第14位的「多重封鎖」將於2025年3月底在波蘭語維基百科進行試用。我們也在尋找其他的維基進行試用。參見Phabricator上的部署時間表。
有了多重封鎖,管理員可獲得更多封鎖選項:全站封鎖和部分封鎖可同時實施,並設定不同期限。如此一來,就不需要等到其中一筆封鎖到期才實施另一筆封鎖。管理員可能想要先對破壞性使用者實施臨時全站封鎖,然後再繼續限制其編輯特定頁面或命名空間。這在需要防止維基人大量編輯特定命名空間或頁面時可能很有用。
目前,管理員須等待第一筆封鎖到期後才能實施另一筆封鎖。這讓管理員需要尋找其他替代方案,例如設定提醒,再返回操作頁面手動更新限制。有了多重封鎖功能,就不需要這些額外步驟了。為準備建置多重封鎖,社群技術團隊使用Codex重新設計了Special:Block頁面。封鎖日誌已移至頁面頂部,讓管理員可以更容易根據日誌決定後續封鎖的性質。
現在可以用確切日期選項來實施封鎖,提供比時間段(例如「兩星期fortnights」)更清晰、更一致的期限設定。這些設計變更是多重封鎖功能實現的基礎步驟。
在Special:Block的URL尾端加上參數
有些社群可能需要更新使用多重封鎖功能的方針指引。如果您的社群符合描述,我們鼓勵您開始討論相關規範。社群技術團隊會支援您的討論,也會聆聽社群希望如何處理此事。
感謝您的耐心等待,我們正努力提供這項有用的新功能。
2025年2月20日:Special:Block的Codex設計徵求測試員
隨著社群技術團隊準備實現多重封鎖(Multiblocks)願望,我們正在利用Codex重新設計Special:Block頁面。由社群技術團隊的首席UX設計師Joydeep Sengupta主持的使用者測試中,我們邀請管理員測試煥然一新的封鎖頁面的原型。若要報名,請造訪Multiblocks的討論頁,我們有一些時間段可供預定。
2024年12月16日:「改善共享資源與其他專案之間的縫合」重點領域開放討論與支持
有多個願望是關於請求改善維基共享空間與其他維基媒體專案之間的連結,社群願望清單已從中整理出一個重點領域。該重點領域的標題為「改善共享資源與其他專案之間的縫合」。該重點領域也已開放供討論與支持。
2024年10月27日:「條目建立」重點領域開放討論與支持
隨著時間推移,社群願望清單建立了一系列願望和建議,強調新手建立條目時需要更好的支援和指導,同時也旨在減少挫折和回退。這些想法已歸入「條目建立指南」重點領域。
您若對改善新手工作流程感興趣,邀請您探索這些願望並參與重點領域討論,如果這個主題引起您的共鳴,請給予支持。
這則公告已發送至:
- 茶館(Teahouse)
- 非洲維基媒體人(African Wikimedians)Telegram
- 活動籌辦人員(Event Organizers)Telegram
2024年10月16日:編輯恢復的近況更新
感謝各位對「編輯恢復」功能的寶貴意見!根據您在討論頁提供的意見,我們做了一些重要的改進。過去,該功能預設會在回到編輯介面繼續編輯時自動「恢復」變更,然後再提供捨棄變更的選項來回退「恢復」。在這次更新後,該功能會先詢問您是否要恢復變更。現在,編輯者對工作流程有了更多的控制權。
直觀演示請參閱以下螢幕截圖:
-
舊版本:變更會自動恢復,若編輯者不想恢復則需捨棄變更
-
新版本:編輯者會收到未儲存變更的提醒,並可選擇恢復或捨棄變更
2024年10月16日:對話變得更輕鬆:機器翻譯的願望來了!
社群願望清單正在測試願望清單內容的機器翻譯。志願者現在可以閱讀願望的機器翻譯版本,甚至可以在譯者翻譯內容之前就投入討論。我們的目標是讓人們能無障礙存取願望清單內容。我們邀請您啟用元維基上的「WishlistTranslation」小工具偏好設定來試用該功能。以下螢幕截圖說明您可以在何處啟用該功能。

請切記,這些機器翻譯未經人工審核,以致翻譯品質有所差異。我們歡迎您在社群願望清單討論頁提出任何意見回饋。
此功能由MinT提供,MinT是託管於維基媒體基金會基礎架構的機器翻譯服務,旨在提供來自多個開源翻譯模型的翻譯。
2024年9月16日:「編輯恢復」回饋請求
社群的各位好,自2024年春季起,「編輯恢復」功能已於Special:Preferences §編輯啟用,根據意見回饋,我們想詢問這項功能未來應該如何運作。
目前,「編輯恢復」假定使用者在重新載入或重新開啟頁面時想要恢復他們的編輯,並詢問使用者是否丟棄他們的編輯。但是,根據我們討論頁上的回饋,部分使用者反而希望「編輯恢復」假定使用者不想要恢復編輯,應該詢問他們是否恢復編輯。
社群技術團隊在本階段正在尋求社群意見,以了解「「編輯恢復」是否能如預期般運作,或使用者是否偏好「編輯恢復」詢問他們是否恢復編輯。
請在討論頁提供意見回饋。我們希望在2024年9月26日(三)前做出決定。
