The Community Tech is a Wikimedia Foundation team running the Community Wishlist Survey. It builds and improves curation and moderation tools for experienced users, supports bot operators, and more. The creation of the team is a direct outcome of requests from core contributors. The team works closely with editors, volunteer developers, and other Wikimedia teams.
Staff Software Engineer, Tech Lead
Aida A. Ramirez
Senior Technical Program Manager
- Watchlist Expiry
- Password Reset Update
- Who Wrote That revision search tool
- Page Curation and New Pages Feed improvements
- SVG Translation project page | SVG Translation tool
- E-Book Export Reliability (WSexport)
- Event Metrics project page | Event Metrics program (formerly Grant Metrics)
- Data Portability
- Article Alerts for more languages
- Template Wizard
- Deprecation of RelatedSites extension
- AfC Process Improvement May 2018
- Commons deletion notification bot
- Global preferences
- Thanks notification for log entries
- Auto-save edits
- Ping users from the edit summary
- Section heading URLs for non-Latin languages
- Edit summary length for non-Latin languages
- Popular pages bot
- Rewrite XTools
- Automatic archive for new external links
Proposal and prioritization processEdit
The main prioritization process for the Community Tech team is the cross-project Community Wishlist Survey. It's an annual project which invites contributors from all Wikimedia wikis to propose and support the changes that they would most like to see.
The team also takes on occasional projects to help smaller groups that may not have enough support in the Survey. For a more detailed breakdown of the team's current work, check our most recent Kanban board.
The team mainly works on development tasks that can be iterated on quickly and that have a direct benefit for the most active contributors who participate in the curatorial and administrative layers of the Wikimedia projects, as well as contributors who work on technical features for the projects such as templates, modules, gadgets, user scripts, and bots.
Tasks that are in scope include (but are not limited to):
- Creating gadgets, bots, and wizards to streamline existing community workflows
- Modifying existing gadgets and bots so that they can work across multiple projects
- Converting heavily-used gadgets and user-scripts into MediaWiki extensions
- Building article curation and monitoring tools for WikiProjects
- Identifying and fixing issues with critical power-user tools that have already been developed, but are not actively maintained, such as AbuseFilter or Citation bot
- Creating better documentation for power-user tools and features so that they can be better utilized across all projects
Tasks that are not in scope include:
- Maintaining orphaned/abandoned projects from other WMF teams.
- Supporting internal needs of WMF teams.
- Large, long-term development projects like converting Commons to use structured meta-data or creating an entirely new watchlist interface.
- Being the point of contact for all community technical requests.
- Sysadmin type tasks such as managing Toolforge, improving site performance, creating new wikis, managing IRC channels, etc.
The Community Tech team has a similar mandate to Wikimedia Deutschland's Community Tech team – Technischer Communitybedarf, or TCB – which provides technical assistance and software development for the German Wikimedia community. We will be collaborating with them on projects that overlap between our teams and assisting each other with technical assessment and code review. We will also be collaborating with other WMF development teams when high-priority community requests fall within their scope. In such cases, we will work with the leaders of the other teams to negotiate timelines, expectations, priorities, and ownership. We also spend a good deal of our time working with and supporting Wikimedia volunteer developers.
It's important to us...
- To work on projects that have a big impact
- To help large wikis and small wikis, in many languages
- To be open and communicative
- To be responsive to people's requests and concerns
- To be calm and civil, and to assume good faith
We're a small team, and there's a lot to do! We want to be as helpful and effective as we can, so we can't take everything on. Saying no to requests that we can't help with is an important part of our job, because it frees up time and energy for the requests that we can help with.
But "no" is hard to hear sometimes, so here are some guidelines about working and communicating with the Community Tech team.
- Please be calm and civil, and assume good faith on our part. We care about the projects too.
- We love our jobs and we work hard, but we don't work 24/7, and we can't guarantee an immediate response.
- If a specific person or issue is taking an outsized percentage of our on-wiki time, that takes time and attention away from other people. We'll sometimes have to close a conversation, and say that we can't spend more time on a particular subject.
- We can't take on projects that are currently on another product team's roadmap, or a project that directly conflicts with another team's work.
- If there's an issue with another product team's work, we can direct you to the appropriate person to talk to.
- We can't answer questions about staffing issues, or confidential matters.
- 2020 Wishlist Survey results
- Status report for 2019 wishlist
- Status report for 2018
- 2019 Wishlist Survey results
- 2018 results don't exist. We changed the naming scheme so the next survey is the 2019 survey.
- 2017 Wishlist Survey results
- 2016 Wishlist Survey results
- Community health initiative // Anti-Harassment Tools
- Status report #1 (January 2016)
- Status report #2 (May 2016)
- Status report #3 (Oct 2016)
- Status report #1 2017 (Oct 2017)
- Community Tech kanban boards (on Phabricator)
- Phabricator profile
- Community Wishlist Surveys: 2021, 2020, 2019, 2017, 2016, 2015
- Community Relations Specialists
- Tech Ambassadors
- Up-time status of our Toolforge tools