Tim Wikipedia Abstrak
|
Abstract Wikipedia
|
The Abstract Wikipedia team is part of the Product and Technology department at Wikimedia Foundation. Tujuan kami adalah untuk membantu gerakan Wikimedia dalam upayanya untuk lebih mendukung, menyertakan, dan menyediakan akses ke bahasa, komunitas, dan budaya di seluruh dunia.
Most content about the team's work is covered in the Abstract Wikipedia pages on meta.
Mission
Tujuan utama dari upaya Wikipedia Abstrak adalah untuk membuat pengetahuan lebih mudah diakses dan digunakan oleh semua orang, tanpa memandang bahasa atau latar belakang mereka.
Vision
Untuk melakukan ini, kami sedang membangun anjungan dan sistem untuk menciptakan artikel yang dihasilkan melalui alat yang dijalankan komunitas dari data terstruktur bersama yang akan menyebarkan penciptaan dan penerjemahan konten yang lebih efisien dan kolaboratif lintas bahasa Wikipedia.
Tujuan pertama kami adalah menyediakan anjungan yang multibahasa, terukur, dan andal yang akan menjadi dasar semua pekerjaan kami lainnya: Wikifungsi. Wikifungsi akan menjadi mekanisme inti yang memungkinkan komunitas Wikimedia untuk berbagi bentuk pengetahuan baru, yaitu fungsi. Ini akan memberdayakan masing-masing komunitas untuk menggunakan alat-alat seperti yang sebelumnya sebagian besar hanya tersedia untuk bahasa-bahasa yang mempunyai sumber daya lebih banyak. Dengan membangun fokus yang inklusif, ramah, dan berkelanjutan untuk pekerjaan teknis gerakan ini, lebih banyak komunitas akan mendapatkan manfaat baik untuk saat ini maupun dalam jangka panjang. Wikifunctions is powered by the WikiLambda extension.
Tujuan jangka panjang kami adalah Wikipedia Abstrak, sebuah proyek untuk menggunakan Wikifungsi yang dikombinasikan dengan kerangka kerja umum yang luwes dan mandiri dari bahasa untuk mewakili data terstruktur dan konsep abstrak yang terdapat dalam artikel Wikipedia, yang akan memungkinkan kolaborasi lintas bahasa yang lebih mudah dan mengurangi duplikasi upaya yang saat ini diperlukan untuk menciptakan dan memelihara versi bahasa Wikipedia yang terpisah. Ini akan memungkinkan terciptanya jenis konten baru, seperti artikel yang dihasilkan mesin, dan mempermudah pemaduan dengan anjungan dan alat lain.
Team
The Abstract Wikipedia team is a collaborative group working together to build a system that enables language-independent knowledge creation. Our team encourages open discussions and shared decision-making.
Here you can find a list of our team members, their roles, and areas of expertise of our team:
Product
-
Amy Tsay (Director of Product) -
Denny Vrandečić (Head of Special Projects)
Design
-
Gregory Onyeahialam (Senior UX Designer)
Communications
-
Luca Martinelli (Movement Communications Specialist)
Engineering
Meeting Plan
Regular team meetings help us stay aligned, collaborate effectively, and address challenges together. Meeting notes and agendas are documented in our Meetings plan for transparency and easy reference.
The Abstract Wikipedia team runs a 45-minute retrospective every two weeks to reflect on what went well, what needs improving, and give each other shoutouts and props. The goal is to maintain engagement and understanding, and to continuously improve our culture and product development processes.
Chores
To maintain system stability and ensure a well-functioning development environment, our team shares responsibility for engineering chores—recurring tasks that keep our infrastructure, codebase, and workflows in good shape. These include monitoring and addressing technical debt, improving test coverage, reviewing and updating documentation, maintaining observability tools, and handling infrastructure upkeep. Engineers rotate through these tasks to ensure an even distribution of workload and to provide everyone with a deeper understanding of our system.
Product Development Process
The Abstract Wikipedia team plans work on a quarterly basis. Our Product Development Process defines how we plan, make decisions, and manage projects. We strive for a robust development process so our team can be more resilient, and we can ship more predictably. We continuously iterate on these processes as we learn.
Our workflow begins with work estimation, where we assess the complexity and effort required for tasks. You can find details on our approach in the Work Estimation Guide.
Finally, to ensure that completed work meets our standards before it is considered finished we maintain a clear Definition of Done.
To measure our progress and impact, we align our work with Objectives and Key Results (OKRs) and track our achievements using our OKR Scoring Framework.
Roadmap
Our planned deliverables for the year support the following strategic goals:
| Platform | Performance | Community |
|---|---|---|
| Build the platform capabilities needed to validate that we can support the Abstract Wikipedia vision at scale. | Remain performant in broad rollouts, in alignment with agree-upon service level objectives. | Output rich, multi-lingual encyclopedic content that is controlled by the Wikimedia community. |
Workflow
We track our work using Phabricator, following a structured approach for task creation, prioritization, and status updates. To ensure consistency, we adhere to our Phabricator Style Guide.
New to the team
Engineering Onboarding
This section will guide you through key technical aspects of our system, helping you get up to speed quickly.
Team Architecture
Understanding the architecture of Abstract Wikipedia is essential for contributing effectively. We encourage new engineers to review our Architecture Overview to familiarize themselves with our core components, services, and dependencies.
Observability
Maintaining a high level of observability is crucial for monitoring system health, debugging issues, and ensuring smooth operations. Our team relies on a combination of logging, metrics, and tracing tools to gain insights into system performance and behavior. New team members should explore our Observability Guide to understand how to access and interpret these insights.
Runbooks
We maintain a collection of runbooks—structured guides that outline common operational tasks, troubleshooting steps, and incident response procedures. New team members should familiarize themselves with our Runbook Repository and contribute updates when needed to keep them relevant and up to date.
Testing Status
Testing is an integral part of our development process to maintain code quality and system stability. New engineers are encouraged to review this and follow our Testing Guidelines when writing and reviewing code.
Git Workflow
At the Abstract Wikipedia team we have implemented a code-review workflow called "Mode eyes on code review" to ensure that at least two team members get to review one patch before it's merged. The goal of this system is to help with knowledge sharing, help navigate delicate areas of the code, and resolve some conflicts between author and first reviewer by adding a third party. Detailed guidelines can be found in our Git Workflow Guide.
Versioning
Wikifunctions follows a versioning approach that differs the versioning that Wikimedia uses.
Team Culture
We are a team, distributed around the world, who mostly interact through online meetings, asynchronous communication channels, working alone or in pairs, reviewing each other’s work, and communicating externally with other teams, communities, and the media.
We share principles to guide our communication, such as avoiding assumptions, building a culture that encourages good behavior, and leading with empathy.
Our team values honesty, transparency, respect, and fairness in our communication, and will work to provide context, avoid making assumptions, and communicate clearly and empathetically while reviewing each other’s ideas, concerns, suggestions, and other work.
We also seek to recognise and respect our colleagues’ communication preferences and acknowledge their differences, such as culture and language.
Main page: Team Culture
Keep in touch
Subscribe to our Abstract Wikipedia Public Mailing List to stay informed about the latest developments in Abstract Wikipedia and Wikifunctions. Join the discussion, get updates on new features, and connect with the community. Sign up here!