Collaboration/Team

The Flow team focuses on delivering a delightful experience for user-to-user interactions. Most of WMF's Core features team (formerly named "Editor Engagement") now works on Flow.


 * Andrew Garrett (werdna) - Part-time engineer
 * Danny Horn (dhorn)- product owner
 * Brandon Harris (jorm) - UX designer (plus rest of UX team)
 * Erik Bernhardson (ebernhardson)- tech lead
 * Matthias Mullie (mlitn) - engineer
 * Quiddity (quiddity)- Community liaison
 * S Page (spagewmf) - scrummaster
 * Shahyar Ghobadpour (shahyar) - engineer
 * Matthew Flaschen - engineer

Also UX designers May Galloway (violetto) and Kaity Hammerstein (kaity).

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

Tech lead responsibilities
The tech lead guides and represents the engineering team. Responsibilities include:
 * Assisting in planning activities and representing the engineering team at planning meetings when the rest of the team is not present
 * Owning the maintenance of the quality and architectural coherence of the code developed by the project
 * Escalating significant architectural/technical issues for prompt resolution
 * Coordinating regular refactoring/code hygiene to prevent accumulation of cruft (including unused features) and technical debt
 * Communicating, educating, and enforcing best practices and standards
 * On-boarding of new team members
 * Bugzilla
 * Provide leadership to ensure tasks are triaged properly, become actionable and move forward
 * Be responsible for ensuring that appropriate tasks get WONTFIXED when there are technical problems
 * Responsible for ensuring that the team has a presence in important conversations on wikitech-l and EE mailing lists

Team documents

 * current iteration in Trello
 * backlog (in Trello)
 * 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 Core Features work.

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