Collaboration/Team

The Flow team focuses on delivering a delightful experience for user-to-user interactions. WMF's Collaboration team (formerly named "Core Features, the team formerly known as 'Editor Engagement'") mainly works on Flow.


 * Stephane Bisson - engineer
 * Matthew Flaschen (matt_flaschen) - engineer
 * Pau Giner (pginer) - UX designer
 * Danny Horn (dhorn)- product owner
 * Roan Kattouw (RoanKattouw) - tech lead
 * Kunal Mehta (legoktm) - Engineer
 * Matthias Mullie (mlitn) - engineer
 * Quiddity (quiddity)- Community liaison
 * Moriel Schottlender (mooeypoo) - Engineer
 * Elena Tonkovidova - QA Engineer

And some much-appreciated contributions from Facebook Open Academy students bencmq and wctaiwan, and other community developers.

See our pictures at Staff and contractors page. We're on IRC most of the time in

Team members share responsibility for the QA analyst role, roughly as follows:
 * engineers - maintaining regression test suite
 * spage - manual integration testing, reviewing browser tests (mostly developed by QA team especially Chris McMahon
 * all - exploratory testing
 * DannyH - assisting (himself) in acceptance criteria definition
 * ErikB - training and otherwise working with engineers in best-practices for assuring code and product quality

Team responsibilities

 * See Collaboration/Team/Roles and responsibilities.

Team documents

 * Collaboration-Team backlog board on Phabricator
 * Sprint boards are linked from the board information page
 * Flow team development workshops
 * /Processes we use
 * mailing lists
 * The  mailing list is a private list for Flow team, plus some other WMF staff, contractors, and admins.
 * is a public mailing list for general discussion of editor engagement, including Collaboration (Flow, Echo, Thanks) work.

Archived Etherpad notes
http://etherpad.wikimedia.org/p/FlowTeamDevelopmentWorkshop31July2013