2/17 Notes

[a-laughlin]

[a-laughlin]

meeting scheduling: once a week reschedule if we can't all be there meetings

• weekly sprint retrospective + sprint planning (sunday morning @ 9am)
• standups (daily slack message)
  • did yesterday?
  • doing today?
  • blockers?'

Tickets to create:

• add to readme

  
  # pulling process
  # in named branch
  git pull origin/master 

push process

git push

- dev process for code issues
- code repository breakdown (parts for mobile, api, pipeline)
- Intro everyone to a potential build/testing setup (actual commands to build/test code)
- dev process for admin issues (e.g., milestone 1) - editing readme/admin stuff in github is fine
- Ensure we have everything for milestone 1

TBD
- inital sprint planning
- Ensure we have tracker issues for the things we're working on.

Architecture Decisions:
- determine if Pytorch needs to determine our mobile framework (decision: pytorch outputs data on server, and mobile will get output data through api)