Talkilla/Status Meetings/2013-10-29
From MozillaWiki
< Talkilla | Status Meetings
Product
- New Product and Estimation meetings being setup
- William helping with setting up the process
- These came out of process discussions between RT and others last week
- More partner discussions today for JB
- We need to have a discussion relating to requirements for being signed in, do you need to log into Talkilla services, before logging into third party providers?
Goals & Roadmap Priorities
- Deliver a comprehensive and fully functional BYOS demo.
- Build out the Talkilla platform into a stable, scalable and extensible platform, offering voice/video calls, InstantShare, chat, web content and file sharing in Firefox Desktop. Stretch: Build PSTN breakout.
- Define Talkilla vision and plan for other Firefox products (Firefox Android and Firefox OS) and other WebRTC browsers.
- Build communications and distribution channels to engage on the Talkilla value proposition, and ...find a decent name.
- What channels do we want? RT is taking to Marketing about various possibilities
- How should we 'launch' this? (Action: RT / Jb ?)
- Are we in a place to actually launch the product? (stability & feature-wise); Do we have an official roadmap we can refer to?
Risks
- Enabling of Multiple Social Providers
- Still looking at test failures, sometimes still fails on Linux asan
- Hoping to get landed and within 2 weeks, so that it can get onto 27
- (long-term) Headless Social Providers
- JSON crash when using real sub-workers vs. 25/27 interop issues
- Still in progress, hoping to get something on it by the end of the week
- AddressBook: Google OAuth2 integration
- "installed apps" strategy proved to be the only viable solution (what is an installed app ?) (this https://developers.google.com/accounts/docs/OAuth2InstalledApp - see reference discussion on the ML)
- still have to work out how to retrieve refresh tokens using their mechanism within the Talkilla technical environment
Meet-ups
- Other meet-ups in Q4:
- Arrange small hack meetings during the quarter
- WebRTC Santa Clara (Nov 19th-21st)
Any other issues/discussions
- Data channels
- Currently platform is incompatible for connecting data channels between FF 25 & 27 (25 - 26 works, and 26 - 27 works).
- We won't bump the minimum requirement at the moment until the crash bug is fixed
- Agile Velocity
- Current Velocity: 2
- Probably slightly lower than expected at the moment, as we haven't had the feed of estimated cards coming through the backlog.
- maybe show this graph at the retrospective each week?
- Load testing
- This has been started, there's currently a 1.6s response lag with 100 users in the system.
- The pain points appear to be in the presence system, solution being looked at and will be integrated into trello
- We need to make a decision on how many users we want to support "initially".