...
- What does Candide need to learn from Eric?
- Name/branding
- From Candide's Evernote:
- Sync bodytrack's concept of a 'source' and fluxtream's 'connectors'
- Strategy for handlng the disconnect between fluxtream's timeline and bodytrack's timeline in terms of source code
- Understand what exactly people external to bodytrack/fluxtream expect from the "timeline component" and how can we externalize the existing code -> EP says: use require.js / how is it going to interact with the backend?
- do we keep rails stuff in the 'official' merged version of the software for OSCON / the next milestone? EP: reimplement proxied ajax calls natively in the 'fluxtream' part
- do we keep the base station, user importers, etc… in the 'official' merged version of the software? AW: Yes, should maintain support for upload API
- what about mymee? problem: not everyone can use it… AW: cultivate additional observation capture options, such as Paco, Tapforms, ohmage, etc.
- migrating fluxtream users…
- screencast video, design for the home page
- write a retro-calendar for next milestone and OSCON
- IntelliJ
- Get beefier replacement for EC2 test instance : Ask Thomas about Belgian hosting company
- HTTPS->Security audit->bodytrack rails app in same github repo with fluxtream-app
- Define milestones between now and OSCon
- Evaluate server tools: New relic?
- Evaluate continuous deployment strategy: Evaluate Live rebel? Cost? Open source discount?
- Issues to discuss with Ray
- Change "Load View"/"Save View" buttons to be dropdown? How do we support time only/channel only loads?
- Margins: fluxtream-app has big margins, bodytrack takes up full width, what do we standardize on?
- How do we navigate between log application (day view/week view) and bodytrack application?
- How to add share link on timeline
- Where should fluxtream.com be hosted: Candide is not happy with standing cloud
...