Komunitas Teknis

This page is a translated version of the page Community Tech and the translation is 15% complete.
Outdated translations are marked like this.

Tim Komunitas Teknis adalah tim produk Wikimedia Foundation yang berfokus pada pemenuhan kebutuhan kontributor aktif Wikimedia untuk alat kurasi dan moderasi yang lebih baik dan berfokus pada ahli. Pembentukan tim Komunitas Teknis merupakan hasil langsung dari permintaan kontributor utama untuk peningkatan dukungan pada alat moderasi, bot, dan fitur lain yang membantu proyek Wikimedia berhasil. Tim bekerja sama dengan kontributor, pengembang relawan, dan departemen Keterlibatan Komunitas.

Proyek saat ini

Proyek Status proyek
Salin dan tempel dari diff
Menghapus dan mengembalikan halaman pembicaraan yang terkait
Memperingatkan ketika menautkan ke halaman disambiguasi
Pratayang real-time untuk teks wiki
   In development
Generate Audio for IPA
   In development
Bot daftar pustaka untuk Wikidata

Lihat pula: Survei Harapan Komunitas 2021 · hasil tahun 2021

Team Mission

We surface the movement's technical platform needs and build and support needed tools with engaged contributors.


  • KNOWLEDGE: The fact of knowing about something; general understanding or familiarity with a subject, place, situation etc.
  • KINDNESS: Having a benevolent, courteous, friendly, generous, gentle, liberal, sympathetic, or warm-hearted nature or disposition, marked by consideration for – and service to – others.
  • COLLABORATION: To work together with others to achieve a common goal.


May 3, 2022: Real Time Preview launching to partner projects

We have launched a version of the Realtime preview feature to Polish Wikipedia. Its community has agreed to partner with us and give us feedback on how to improve it before we launch to the rest of the users. Please find our complete Release Plan. Baca lebih lanjut

15 Februari 2022: Hasil tahun 2022

Survei Harapan Komunitas 2022 telah usai! Kami ingin mengucapkan terima kasih kepada semua yang telah berpartisipasi pada edisi tahun ini dan khususnya berterima kasih kepada mereka yang telah berkontribusi banyak kepada survei di bawah hasil. Kami tidak bisa melakukan ini tanpa kalian semua!

Penasaran akan terjadi apa selanjutnya? Mari belajar tentang proses penentuan prioritas dan bacalah peringkat hasil yang telah diprioritaskan untuk tahun ini. Baca lebih lanjut

8 November 2021: Memperingatkan ketika menautkan ke halaman disambiguasi

We have an update about the wish. We have finished user tests. Baca lebih lanjut


We mainly work on the Community Wishlist Survey. It's an annual project which contributors from all Wikimedia wikis can ask for changes that they would most like to see.

Tim ini terutama akan mengerjakan tugas-tugas pengembangan yang dapat diulangi dengan cepat dan yang akan memberi manfaat langsung bagi kontributor paling aktif yang berpartisipasi dalam lapisan kuratorial dan administratif proyek Wikimedia, serta kontributor yang mengerjakan fitur teknis untuk proyek seperti kerangka, modul, gadget, skrip pengguna, dan bot.

Occasionally, we also work on other projects. We do that to help smaller groups that may not have enough support in the Survey. This is how we have worked on:

Tugas yang berada dalam ruang lingkup termasuk:

  • Membuat gadget, bot, dan wizard untuk menyederhanakan jalan kerja komunitas yang ada
  • Memodifikasi gadget dan bot yang ada agar dapat bekerja di banyak proyek
  • Mengonversi gadget dan skrip pengguna yang sering digunakan menjadi ekstensi MediaWiki
  • Membangun alat kurasi dan pemantauan artikel untuk ProyekWiki
  • Mengidentifikasi dan memperbaiki masalah dengan perkakas pengguna daya kritis yang telah dikembangkan, tetapi tidak dipertahankan secara aktif, seperti AbuseFilter atau Citation bot
  • Membuat dokumentasi yang lebih baik untuk perkakas dan fitur pengguna daya sehingga dapat digunakan dengan lebih baik di semua proyek

Tugas yang tidak dalam cakupannya meliputi:

  • 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.

We uphold the civility standards set by the Terms of Use. We observe and maintain the friendly space expectations for Grants spaces in our interactions. We ask that all contributors to Community Tech spaces do the same.

For a more detailed breakdown of the team's current work, check our Kanban board in Phabricator.



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.

Engaging with Community Tech

We triage and track our work in Phabricator. Outside the annual Community Wishlist Survey, use the following Phabricator templates to log feature requests and bugs for the tools we maintain:

We review and triage new requests on a biweekly cadence.


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.

Our process for defining our Values and Mission

In a collaborative session we all came together as a team to work towards being able to formulate our mission statement. To get there we first tried to think about which values we most care about individually to then see where they overlap, because we wanted to make sure that they are truly with us as a group of humans.

Three values stood out to us, which are: Knowledge, Kindness and Collaboration

Values statements itself are pretty broad and can be interpreted differently so we discussed them thoroughly to understand what behaviours they actually translate to, we’ll summarise here quickly what we mentioned:

Why do we care about Knowledge?

We do not want to be protective of our knowledge. If we discover something or implement something new we would like to write about it, let others know compassionately. If we make a decision, document it and explain the reasons. This is especially important because we want to be welcoming people to join the movement as new contributors or team mates.

Why do we care about Kindness?

We are conscious that we can never know what struggles others might be facing, always remember that we may not be aware of the whole picture. By being considerate and courteous to one another we ensure that we all feel included and encouraged to work more openly with one another. In addition to that being kind can mean being clear about if and how we can help or resolve a problem.

Why do we care about Collaboration?

Collaboration is the backbone to what we do and fosters innovation by combining ideas from different viewpoints. When giving explanations we want to be detailed and link to more info wherever possible, to make sure our explanations are meaningful to others. We welcome and actively seek ideas & feedback and questions from each other, WMF, and the community.

Mission statement

Having our values and beliefs in mind we further thought about what our mission statement might be. What are our responsibilities towards the movement, the community and towards each other and what connects us to the CommTech team. Are we just building some tools or is there any greater duty that motivates our work? This one summarised our opinions best:

We surface the movement's technical platform needs and build and support needed tools with engaged contributors.

As we want to contribute to the increase of the movement’s inclusiveness and growth, we surface the needs of the contributors, as long a they are of technical nature. Some of the tools we build ourselves, while we communicate others to the foundation to increase awareness of these needs across different teams.


One of the challenges our team faces is that we touch many different codebases and existing tools, that we don’t know well, therefore we currently have two main initiatives:

Collaboration Initiative

The need to collaborate and work closely with others at higher frequency than other teams is quite evident to understand other team’s work, if we touch existing codebases, and to make sure our tools are implemented in a way that matches their way to work.

The goal of this initiative is to improve knowledge sharing and collaboration across teams and within teams and find ways to check in with other devs before implementing work to make sure we don’t build things from scratch that have previously been implemented. In addition to that we know we can build more innovative solutions by allowing for more collaborative programming sessions. We thought of ways to encourage for more cross team collaboration for engineers i.e. by allowing temporary exchange for engineers across teams, by reserving weekly internal collaborative programming sessions that engineers from other teams can visit and add to the agenda of these sessions.

In April 2022 we had an internal hackathon where we work on a series of proposals from this years wishlist and invite other teams to join us for a week. Often times specialists for certain fields are already existent in other teams and working on different projects for a week can increase the sense of belonging within the engineering team and have a positive impact on collaboration in the future.

Maintenance Initiative

With a growing list of projects we maintain, we are left more and more distracted from our priorities.

We do want to provide maintenance for our work, but want more structure for how we provide it. We are currently reviewing our approach to maintenance and are considering restructuring out strategy towards maintenance. We will continuously update you about our approach and we are discussing here.

We internally decided how to make these changes happen and are tracking our decision making progress.

Documentation Initiative

With the intention to understand the work of other teams we often look at codebases that are new to us. A good documentation is absolutely essential to get an understanding of the implementation details, goals and challenges of other's work. As a team we want to be exemplary in writing really good documentation, ideally documenting first before implementing and frequently updating others about the status of our work. To achieve that we are currently looking studying how other teams document their work to make sure we find a way that is aligned with other teams. We want to keep documentation close to our code.

When organising collaborative programming sessions we collected recommendations and wrote it down in a guide.

As it seems currently documentation lives separate from the code in Mediawiki.org and gets there manually. Because one of our team values is “knowledge” we want to provide outstanding documentation, as we appreciate other teams sharing their knowledge i.e. implementation details of tools they build, setup guides, usage example. To achieve this goal there are the following steps we want to take: we want to value code contributions as much as documentation, we want to keep documentation in the same repository as code and make documentation requirement for release and have a consistent contribution process for code and documentation, to make sure documenting your work is easy and is done just while we write code.

Users Guide

Template for Reference

  • Preferred Name:
  • How to talk to me:
  • (Optional) Pronouns:
  • (Optional) Things I like:
  • (Optional) Things I’m bad at:
  • (Optional) Annoying things I do:
  • (Optional) How to cheer me up when I am grumpy:
  • (Optional) Hot takes:
  • (Optional) Anything else you should know about me:

Find our user guides here:

Further information

Daftar subhalaman

Pages with the prefix 'Community Tech/id' in the 'default' and 'Talk' namespaces: