Global Collaboration
The Global Collaboration team has been re-split into two teams. Going forward, please check the Growth (previously: Collaboration) and Language team pages for updates and information. |
This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. |
The Global Collaboration team of the Wikimedia Foundation is part of the Contributors team in the Wikimedia Audiences group. We are currently transitioning into this new team by merging the Collaboration and Language teams.
See Also: FAQ
People
editThe Global Collaboration team has members from across the world. Most team members work remotely. The others work from the Wikimedia Foundation office in San Francisco, USA.
The team has a combination of various skills for front-end and back-end development, internationalization and language support, mobile technology, QA, dev-ops, product management, and community interactions. The Global Collaboration team has embedded cross-team support from Contributors' Product team, Contributors Design, and Community Engagement.
Most team members are also long-term participants in various Open Source communities, and have a combined working knowledge of nearly 25 languages.
-
Roan Kattouw
Lead Engineer -
Runa Bhattacharjee
Engineering Manager
_2013.jpg)
-
Amir E. Aharoni
Product Analyst -
Benoît Evellin
Community Liaison -
Elena Tonkovidova
QA Engineer -
Joe Matazzoni
Product Manager -
Kartik Mistry
Software Engineer -
Matthew Flaschen
Senior Software Engineer -
Moriel Schottlender
Senior Software Engineer -
Niklas Laxström
Software Engineer -
Pau Giner
Senior User Experience Designer -
Petar Petković
Software Engineer -
Santhosh Thottingal
Senior Software Engineer -
Stephane Bisson
Software Engineer
Annual Goals – FY2017-18
editPlease see the annual plan for the Contributors team. We will add more details in this section in the next few weeks.
Ongoing work
edit| Project | Details | Outcome |
|---|---|---|
| Content Translation | Replace the contenteditable editing component of Content Translation with VisualEditor and preserve the current CX functionalities | Content Translation is more stable in terms of article publishing, requiring less maintenance work from patrollers, and more ready to be enabled by default for all users. |
| Edit review improvements | Apply the new recent changes filters technology with Machine Learning to other contexts like watchlists and history pages | Roll out the recent changes filters to all users on all wikis. |
| Structured Discussions | Make the wiki discussion system more accessible for new users, more efficient for experienced users and encourage meaningful conversations that support collaboration. | Support the existing Structured discussions on wikis using it, by reviewing front-end or improving features like search. |
Team processes
editThe development teams working on the ongoing projects are using their existing process workflows at the moment. We will add more details in this section as we progress through the quarter.