Welcome to the zypher-events wiki!

Meeting Logs

Meeting one

Attendance

• Arunavo
• Aaron
• Britney
• Elliot
• Noordeep
• Tom

Takeaways:

• Try to get planning done sooner than later, more time to code!
• Turn user stories into GitHub issues (everyone do their part)
• Elliot doing CRC cards, others please review and give feedback

Meeting two

Attendance

• Arunavo
• Aaron
• Britney
• Elliot
• Noordeep (Left Early)
• Tom

Takeaways:

• Make sure that we are committing to what we are going to do at the end of each meeting. (Stay until the end!!)
• Britney and Tom are doing the remaining User Stories (Then helping label UI once they are done)
• Elliot and Aaron are taking drawing mockups of UI and digitizing them in Draw.io DONE BY THE END OF FRIDAY!!!
• Britney, Tom, Arunavo, Noor, doing storyboarding and adding user stories to UI
• Tom will create a milestone and get the 23 issues in.

Meeting three

Attendance

• Arunavo
• Aaron
• Britney
• Elliot
• Noordeep
• Tom

Takeaways:

• Feedback for part two will be given next week

• Deliverables are codebase

  • Code and UI for every user story completed (acceptance criteria)

• Everything should be commented with Javadocs (Should be able to read comments and understand everything)

• Testing

  • With each merge request, add test cases (UI and otherwise)!!
  • Dont leave them for the end

• UML Diagrams

  • we need those now in the wiki!
  • representative of current project state

• Backlog

  • User stories assigned to people, move from backlog when working on stuff!!
  • in progress -> PR review -> done

• Update CRC cards to be more android specific

• Update Mockups & Storyboard with XML as we make it

• 2 User stories per week ish!

• Sprint Planning?

  • What have you done for the week, what are you planning, what are your blockers
  • In wiki!

• Demo of halfway at some point in a lab session. Should be a smooth user experience of what has been implemented.

• UI testing with firebase, fake database?? In lab notes for this week

• Database should be first priority!! Everything relies on this.

Try to get the database done over the weekend!!

Stuff we are doing for the following week.

XML UI needed:

First 2 UI elements & settings page for entrant: Noor

All events & Joined Events & Organizer events (Admin and Organizer, two seperate): Brittney

Popup XML: Tom

Admin stuff: Arunavo

Database class working: Elliot & Aaron

User stories in order, just for group discussion

US 01.07.01 [Machine device identified, user can define what role they are]

US 01.02.01 [Provide personal info into database]

US 01.01.03 [See list of events as entrant]

US 01.01.01 [Join waitlist for event]

US 01.01.02 [Leave waitlist for event]

Meeting Four

Attendance

• Arunavo
• Aaron
• Britney
• Elliot
• Noordeep
• Tom

Completed:

Elliot: Completed objects for database, user types, event, notification. Fixed up things TA suggested in feedback. Started on UML Diagram and US 01.07.01.

Aaron: Set up and implement database tests, added some functionality to existing database classes.

Arunavo:

Tom:

Britney:

Noor:

Planning:

Elliot: Continue UML Diagram work, complete user stories assigned to me (US 01.07.01, US 01.02.01, US 01.02.02) And check into firebase permissions!

Aaron: Complete user stories US 02.01.01, US 02.01.04, US 02.02.01 and US 02.03.01

Arunavo: Completed User Stories: US 01.05.04, US 01.01.01, US 01.01.02, US 01.01.03, US 03.01.01, US 03.02.01, US 03.04.01, US 03.05.01, US 03.07.01, US 03.08.01.

Tom: Complete user stories US 01.02.03, US 01.02.04, US 01.04.01, US 01.04.02, US 02.07.01, US 02.07.02, and US 02.07.03.

Britney:

Noor:

Blockers:

Elliot:

Aaron:

Arunavo:

Tom:

Britney:

Noor:

Takeaways:

4 User Stories per person (3 for Elliot + UML)

User stories are complete IFF whole process is complete (should be able to get there only from UI. Start to finish) & tests are written (if applicable).

Only create PR if tests are passing, and code does not error out!!

TA: Attendance mandatory for labs, attendance mandatory for demo.

Meeting Five

Attendance

• Arunavo
• Aaron
• Britney
• Elliot
• Noordeep
• Tom

Completed:

Elliot: Completed and working in Main: US 01.02.01, US 01.02.02, US 01.07.01. UML Diagram of code structure for Part 3

Arunavo: Completed and working in Main: All user stories planned

Aaron: code for us02.03.01 but not in main, and checking that registration occurs within window and tests

Tom: Completed and working in Main: Assigned user stories, except for integrating with the rest of code

Britney: US 01.05.05 but not commited to main through PR, 90% done US 02.05.02 in own branch.

Noor: US 02.06.01, US 02.06.02 Started work but not in main branch yet

Planning:

Elliot: US 01.04.03, US 01.06.01, US 01.06.02, Take a look at Firestore permissions so that we don't expire

Arunavo: 2 more US from admin, images stuff

Aaron: (Prioritize US 02.02.01 for Tom) US assigned

Tom: New user stories, change organizer notification page to fragment (or popup) and implement push notifications to entrants.

Britney: (Prioritize US 02.05.02 for Tom) assigned user stories for friday

Noor: User stories for friday

Blockers:

Elliot:

Arunavo: Dates needs fixing

Aaron: Complete user stories assigned

Tom: US 02.05.02 (Britney) and US 02.02.01 (Aaron)

Britney: potential merge conflicts

Noor:

Takeaways:

For part 4 (and kinda part 3):

In short, part 3 deliverables but with sprinkles. Everything is expected to be complete. Address feedback, Maintain source code (Commented!!!!), Javadocs (just in classes, not generated for real) (include bugs in the java doc headers!!!!!), Test Cases for Models and Controllers, UML updated, Product backlog should be updated with progress, running app!!!, Story boards CRC cards Mockups reflect app. Sprint planning updated.

For the Demo of part 4 is in front of everyone (4 min total live presentation). Make sure you can connect to the screen for presentation. The slideshow should exist as a backup.

Meeting Six

Attendance

• Arunavo
• Aaron
• Britney
• Elliot
• Noordeep (Dropped Course)
• Tom

Completed:

Elliot: US 01.01.04, US 01.04.03, US 02.02.02, US 02.02.03

Tom: US 01.04.01, US 01.04.02, changed activity to fragment, added notification page.

Arunavo: Assigned user stories

Planning:

Elliot: EVENT DETAILS FRAGMENT! US 02.06.05, Finish (push) refactor of code to eliminate duplicate objects, Fix up phone number optional at sign up, Fix up waitlist Entry in UML, Update UI Mockups and Story Board

Tom: US 02.07.01, US 02.07.02, US 02.07.03, push notifictions (local notifications), link up these fragments. Halfway point correction

Arunavo: two user stories

Aaron: Assigned user stories

Britney: Assigned user stories

Blockers:

Takeaways:

Marking may be a little more lenient because of Noor dropping out.

Meeting Seven

Attendance

• Arunavo
• Aaron
• Britney
• Elliot
• Noordeep (Dropped Course)
• Tom

Completed:

Elliot: Basic event details fragment, pushed the refactor, fixed the optional phone number, added waitlistEntry to UML (and updated UML), update mockups and storyboards (still a few to do once the UI is done), changed lottery from moving to accepted to moving to invited, fixed a couple bugs that tom noticed, US 02.06.05, US 02.06.01 (Was done by Arunavo)

Tom: Completed local notifications using a foreground notification service of different priority levels (NotificationService and NotificationHelper). User stories for Organizer to send custom notifications to selected entrant group using the NotificationService (Including new xml, preset template notification message). User story that allows the organizer to cancel invited entrants (also sending a notification to alert the canceled entrants).

Planning:

Elliot: Polish the UI, Change the Joined Events fragment to be more useful, update the joined events fragment in mockups and storyboarding, add event details page in mockups and storyboard, Create dummy data and APKs for demoing

Tom: change the storyboarding and mockups in drawio for notifications, navigation error

Arunavo: More testing! Video backups.

Aaron: More testing! Fix conflict

Britney: poster URL in the event creation and edit menu, description in add and edit

Blockers:

Takeaways:

Things to get done:

Demoing next week (Attendance mandatory, tell TA beforehand if there are schedule conflicts) random assignment of time.

1 min setup 3 mins demo 1 min teardown and Q/A

10 min break halfway through the demo lab session

Sell / Show off the app