Community Tech
Community Tech
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.
The team
🛠️ How We Work
[edit]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.
Current selected projects
[edit]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.
| Projects | Project status |
|---|---|
| Multiple Watchlists |
 In development |
| Multiblocks |
 Done |
| Template recall and discovery |
Done |
📢 Latest Updates
[edit]December 1, 2025: Results of our last Wishathon sprint
[edit]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.
Further information
[edit]- Team Processes
- Development
- Maintenance
- Team Documentation (Drafts in progress)
- Community Tech/Phabricator criteria
