Talkilla/Status Meetings/2013-05-07

Preamble

Summary of yesterday
Moving forward today:
- Thinking about using SocialAPI: https://webrtc-apps.etherpad.mozilla.org/30
- how do we do automated testing on parts of the code that run in the SocialAPI context
  - Selenium?
  - (See last week's retrospective)

The future weeks are our goals for the iterations, so that we can assess in the retrospectives.

Last Week
- Front-end unit tests enabled & landed
- Improved handling of server connectivity
- pushes to talkilla-stage are now automatic, on push to the master of the github repo
This Week
- These are in the Trello:
  - Write first cut of pivoted user stories for the Trello
  - Decide & document how we've decided to pivot the code base
  - Research & propose a strategy for functional-testing in the SocialAPI world
  - (dropped for this week?) Scoping document for Social API possible features and issues for FF 22 and Aurora 24
Week of 13 May
- See Meet-ups section below

Goals general
- Social API is a Q2 goal, as this gives the architecture where we can start to investigate Website APIs, and enhanced user interactions.
- Chrome compatibility and/or Talkilla as a single-web page are not Q2 goals

May meet-up in Paris
- Goal proposals
  - Group has general agreement on technical architecture (Tues mtg?)
  - Pivoted user stories prioritized/grouped so we can execute towards goals
  - Shane has solid understanding of use cases for SocialAPI so they can land for Fx 24
Firefox Desktop Work Week

What are the next steps for UX? (Question for Boriss, who answers below)
- Decide what use cases we want to support & prioritize
  - Start with user stories
  - Look for lightweight help from user research team
  - Start into actual mockups