This page is a translated version of the page Community Tech and the translation is 34% complete.

社群技術團隊

Community Tech manages the Community Wishlist, a forum for contributors from all Wikimedia projects to suggest and comment on product and technology changes and improvements.

We leverage the Wishlist to collaborate with editors, volunteer developers, and other Wikimedia teams to turn community-identified needs into real solutions, and work on priority wishes.

團隊

Jack Wheeler

Lead Community Tech Manager

Karolin Siebert

Engineering Manager

Cormac Parle

Principal Software Engineer

Dayllan Maza

Staff Software Engineer, Tech Lead

Tim Starling

Principal Software Architect

Joydeep Sengupta

Principal User Experience Designer

Harumi Monroy

Senior Software Engineer

MusikAnimal

Staff Software Engineer

Sam Wilson

Staff Software Engineer

TheresNoTime

Software Engineer

Sandister Tei

Movement Communications Specialist

Dom Walden

Test Engineer

George Mikesell

Test Engineer

🛠️ 工作方式

We are a small team with limited resources, and balance our efforts across three categories:

  • Building tooling to advance the Community Wishlist
  • Maintenance of existing tools and features supported by the Community Tech team
  • Delivering on wishes, primarily by adopting Focus Areas supported by volunteers.

When we say "no" to a given request, we are merely stating it goes against our current priorities.

When working and communicating with us:

  • Please be calm, civil, and assume we’re working in good faith.
  • We aim to respond promptly but can't guarantee immediate replies.
  • Sometimes, we may need to close a conversation if it takes too much of our time or attention.
  • We can not handle projects on another team's roadmap or ones that conflict with their work, but we will direct you to the right person when possible.
  • We can not discuss staffing or confidential issues.

目前選定專案

Community Tech is currently wrapping up carry-over work from the 2023 Wishlist. Beginning in 2024-25, the team will adopt community-supported Focus Areas via the new Community Wishlist.

專案 專案狀態
Multiblocks
  开发中
Sharing QR codes
  完成
Edit-Recovery Feature
  完成
Template recall and discovery
  开发中


📢 最新消息

2025年3月12日:「多重封鎖」試行

2023年社群願望清單調查中排名第14位的「多重封鎖」將於2025年3月底在波蘭語維基百科進行試用。我們也在尋找其他的維基進行試用。參見Phabricator上的部署時間表

有了多重封鎖,管理員可獲得更多封鎖選項:全站封鎖和部分封鎖可同時實施,並設定不同期限。如此一來,就不需要等到其中一筆封鎖到期才實施另一筆封鎖。管理員可能想要先對破壞性使用者實施臨時全站封鎖,然後再繼續限制其編輯特定頁面或命名空間。這在需要防止維基人大量編輯特定命名空間或頁面時可能很有用。

目前,管理員須等待第一筆封鎖到期後才能實施另一筆封鎖。這讓管理員需要尋找其他替代方案,例如設定提醒,再返回操作頁面手動更新限制。有了多重封鎖功能,就不需要這些額外步驟了。為準備建置多重封鎖,社群技術團隊使用Codex重新設計了Special:Block頁面。封鎖日誌已移至頁面頂部,讓管理員可以更容易根據日誌決定後續封鎖的性質。

現在可以用確切日期選項來實施封鎖,提供比時間段(例如「兩星期」)更清晰、更一致的期限設定。這些設計變更是多重封鎖功能實現的基礎步驟。

在Special:Block的URL尾端加上參數?usecodex=1,即可使用煥然一新的管理員封鎖頁面。歡迎嘗試,並在專案討論頁提供反饋意見。

有些社群可能需要更新使用多重封鎖功能的方針指引。如果您的社群符合描述,我們鼓勵您開始討論相關規範。社群技術團隊會支援您的討論,也會聆聽社群希望如何處理此事。

感謝您的耐心等待,我們正努力提供這項有用的新功能。

先前消息

更多信息