Skip to content

Standup Meeting 3.29

KarlHan edited this page Mar 31, 2022 · 1 revision

Standup Meeting Thuesday March 29

Attendance

  • jdumouch
  • ageolleg
  • tianming
  • yq4
  • egwhite

Note: Yuchen couldn't join Slack group because an error made by me (tianming), but was able to relay message to the meeting.

Background

After part 3, some work has been done:

  • jdumouch. Refactor login fragment, fix UI issues and working on most features of leaderboard. Maintain GitHub issues and project backlog.
  • ageolleg. Planning to work on the map fragment.
  • tianming. Fetch data in main view model and dependency injections. Planning standup meetings on Slack.
  • yq4. Some progress in capturing qr codes. Integrating zxing library to the project.
  • burgosot. Planning to work on the player profile fragment.
  • egwhite. Planning to work on the UI android tests.

What did we do

  • jdumouch. All leaderboard features required by assignment are in place.
  • ageolleg. Use OpenStreetMap for map. Fetch QRShot from database and display on map.
  • tianming. A class for getting User location and an example android test.
  • yq4. Upload qr shot after capture. Scan recognizes profile/login qr codes.
  • egwhite. Started working on android tests.

What will we do today

  • jdumouch. See if issue of search button on leaderboard can be fixed. Integrating player profiles to player list so click on a player opens the profile page. Also android tests to be done later.
  • ageolleg. Continue working on map features and commits to GitHub for reviewing progress.
  • tianming. 'Scrum master' (responsible for asking questions in meetings) and review code.
  • yq4. QR code scanning login. Record player's location and add javadoc comments to capture code.
  • egwhite. Continue writing intent tests and see if people need help on improving UI.

Impediments in the way

  • Some issues with search button on leaderboard.
  • Current profile fragment progress is unknown, which Jaydon will ask Jaime later.
  • Intent tests.
  • Evan wants to know what else on our app's UI component that needs to be done, but UI overlaps with other components (i.e. map, leaderboard, profile, etc.) a lot and it's not clear what to do.

Clone this wiki locally