Stand-up

Alex

Did:

• Marked project part 2 ( :) )
• UML feedback

Will do:

• Mark UML (can look at it this meeting)
• Other feedback

Blockers:

• None

Adam

Did

• Sat in room on sunday doing work on UML

Will Do

• Contribute planning of iterations (distribute tasks)
• Set up HuBoard

Blockers

• None
• Guessing what he's gonna do

Tristan

Did

• Sat in room worked on UML
• Helped convert to Dia
• Added Mockup

Will Do

• Whatever is decided after the meeting

Blockers

• None

Sarah

Did

• Was not in the meeting, was in Hawaii
• Addressed some feedback
• Converted UML to Dia

Will Do

• Do what's assigned for the next part

Blockers

• None

Oleg

• Was in on Sunday

• Do what's assigned

• No blockers

Ramish

• Also in said room on sunday

• Addressed missing use case/feedback

• Whatever's assigned

• No blockers

Rajan

• Was in the room on Sunday

• Whatever's assigned

• No blockers

UML Feedback

• Looks good

ElasticSearch

• JEST Library
  • Not-raw HTTP way to deal with ElasticSearch
  • Still use Gson, etc.
  • Normal version doesn't work on android
  • Might not be approved, may need to ask

Offline?

• Data not exclusively stored in ElasticSearch
• Will we need to sync?
  • Need to look in the User Stories
  • Up to interpretation
  • There is a mechanism in elastic search that lets you only update with new info
    • "Sorry user!" or work every time
• Cache advice:
  • Keep it simple
  • Don't try to replicate ES, use linear search if needed

Other Questions?

• Everyone's looking at each other....
• Red pants on Tuesdays? Maybe.

Are we starting soon?

• Foundations
• Meeting... :(

Question: Are we using the same ElasticSearch server?

• URL on eClass (index for each time)
• No backend! Yay!!
• ElasticSearch is RESTful. Eventually consistent.

Next Part - March 16, 2015

Meeting (minus Alex)

Dividing up work

• Need to make more usable tests
  • Use the tests to write the code
  • Write tests, make it pass, refactor
  • Some tests will not be usable
    • Comment out that can't be used.
    • Use as inspiration

Need foundation laid

• Might be overlap
• Need "backend" works, talking to elastic search, etc.

We will assume that things are Json objects in shared preferences or something.

• Generic local exporter that can be replaced later

What can be done?

• Objects rather than interfaces
• Claims, Expense Items, Tags

Start

• Try to do ExpenseClaimList.
  • As we find things to do, do it.
  • Assign things to yourself to keep others from doing the same work.

HuBoard

• Fancy issue tag thing
• Every week, put what we want to get done in the backlog
• Backlog has all of our crap
  • drag things we want to do into ready.
  • Move things from ready to working and assign self.
• When done, make a pull request for peer review.
• When pulled, move it into done.
• HuBoard puts the information in a comment and adds a tag.
• Things in Ready column should be what we want done before next Tuesday
• Can mark things as blocked. Please comment on why it's blocked.

Try to order in terms of priority of the task

Adam will fiddle around and set up HuBoard.

Check the Home page of the Wiki for important info

TODO

Adam

• Set up HuBoard

Everyone

• New issue for setting up Saving to a local file

Regular Meetup Friday