Changes
Page history
Update Meeting Minutes
authored
Feb 13, 2025
by
Clifford Xing
Show whitespace changes
Inline
Side-by-side
Meeting-Minutes.md
View page @
e6666377
Meeting minutes
\ No newline at end of file
# CS346: Meeting Minutes
Team: Zuna
Members: Cliff, Ted, Ryan, Michelle
## Meeting 1 - Date: Wednesday, February 5th, 2025
### Present: Cliff, Ted, Ryan, Michelle
### Absent: N/A
### Agenda:
-Discuss the tickets that we deem "necessary" for this upcoming sprint
-Categorize each ticket (e.x frontend, database, etc.)
-Determine the priority of each ticket
-Discuss a "brief overview" of the instructions, features, and steps for each respective ticket
-Delegate high priority tickets to be finished by the weekend
### Notes:
-Before beginning any code features, it is imperative that we set up the project (blank activity for now is fine) and push to the repository
-All members need to have Android studio set up to develop
-A Firebase account should be set up and the project should be created
-The Google Firebase account should be "linked" to the android studio project
-The Android studio project should be configured with Firebase (ie. dependencies, plugins, etc.)
-We need a ticket to set up the firebase database, which seems high priority
-Firebase data models also needs its own ticket (defining collections)
-Database operations (CRUD) is also a separate ticket (this ticket may be larger)
-A ticket should be created for implementing Authentication features of our app
-Google sign in would be a great feature to have, so another ticket for that
-Along with the implementation, auth UI should also be its own ticket
-Less priority tickets seem like image storage, database testing, auth testing, security
### Decisions:
-We created high priority tickets for : firebase setup/config, database setup, email password auth, data models
-We believe that medium priority tickets include: google sign in, auth ui, database ops, image storage
-Low priority tickets that do not necessarily have to be completed this spring include: auth testing, security, testing
### Actions:
By our next meeting (Sunday February 9th) we have assigned the following (TO BE COMPLETED BY FEB 9th):
-Ted will setup the android studio project and work on auth
-Cliff will setup and configure firebase for the project, and work on auth
-Ryan will work on creating a "temporary" basic frontend interface for us to test auth on
-Michelle will begin setting up Google sign in on the firebase account and implement the fire store rules