Talkilla/Status Meetings/2013-07-09
From MozillaWiki
< Talkilla | Status Meetings
Contents
Development Summary and Future Iterations
The future weeks are our goals for the iterations, so that we can assess in the retrospectives.
- Last Week
- Lots of foundation work for reworking the conversation window and implementing file transfer
- This Week
- Finishing conversation window rework
- Finish file transfer (first version)
- Finalise our functional testing story
Social API
- examined push api, decided to change direction
- need to discuss SPA inter-provider communication
- working towards enabling multiple provider frameworkers w/chat
- have a generally good plan for "secondary" providers
- have not got around to testing marrionette :(
UX
- nearly done with first draft of talkilla specs, plan to finish this week & seek review
- still working on "whole lifecycle of call" work, some of which was blocking on agreement on specs
- met with ria last week and ekr this week to discuss strategy - ria likes our direction but wants more clarity on how partners could get involved, working on that now. ekr helped with pointing out some areas we need more clarity, particularly around how partners get value, what they expect, and how they see themselves as monetizing
Product
Goals & Roadmap Priorities
- Recommend main focus is on the dogfooding, with cards inserted into backlog at appropriate points for the non-dogfood goals.
Meet-ups
- July:
- Date: 15 - 19th,
- Location: Paris
- Possible Goals
- Revise backlog for Q3 goals
- Pairing
- Making talkilla usable for more users, usable being:
- Resizing the chat window should resize video
- Get functional testing up and running
- Social/Platform: get everything that we need for FF 25 in patches/known quantities
Any other issues
- What to do about the conversation logging?
- Getting blocked by doing something future looking which is big, or something small which will be thrown away later.
- Decided we don't need it at the moment for dogfooding, and rather than keep blocking or extending the time, to delay the card to later, re-estimate what we're doing on it, and bring it back into the todo list in a couple of weeks.