Meeting Info
- Meeting Type: Kickoff Meeting
- Date: April 9, 2026
- Time: 6:30 PM - 7:00 PM
- Location: CSE Building, Discussion Section Room
- Minutes Recorded By: Evan Marriott
Attendance
Agenda
- Introductions — personal interests and coding strengths
- Role assignments for the project
- Establish recurring meeting time and film intro shots
Additional Meeting Notes
- All members were present and participated in introductions
- Each member filmed a short intro clip for the team introduction video
- Meetings are held during the Monday discussion period going forward
Unfinished Business
No old business - this is the first meeting.
New Business
Item 1: Introductions
- Introduced by: Evan Marriott
- Discussion: Each member introduced themselves, shared personal interests, and described their coding background and strengths. Members highlighted experience across frontend, backend, QA, DevOps, design, data, and documentation.
- Resolution / Status: Resolved
Item 2: Role Assignments
- Introduced by: Evan Marriott
- Discussion: Based on introductions and stated strengths, the team discussed and confirmed role assignments. Roles are treated as primary ownership areas rather than hard boundaries.
- Resolution / Status: Resolved
Item 3: Recurring Meeting Time
- Introduced by: Nicole Sutedja
- Discussion: Team reviewed availability and agreed on a standing weekly meeting time during the Monday discussion period.
- Resolution / Status: Resolved
Decisions Made
Decision 1: Role Assignments
- Decision: Roles assigned as follows — Team Leads: Evan Marriott, Nicole Sutedja; Frontend: Prakhar Shah, Kaley Chung, Benedict Luis, Bethany Miyamoto; Backend: Aron Wu, Jensen Guo, Xuanye Wang, Han Yang-Lin; Data: Hudson Gehrke
- Reasoning: Assignments based on each member's stated strengths and interests from introductions
- Dissenting Opinions: None
- Why the group proceeded anyway: N/A
Decision 2: Recurring Meeting Time
- Decision: Mondays 4:00 – 5:00 PM during discussion period
- Reasoning: Consistent with everyone's existing schedule and a dedicated block already reserved for the course
- Dissenting Opinions: None
- Why the group proceeded anyway: N/A
Slack as Primary Communication Channel
- Decision: Slack will be used for all async team communication; responses expected within 24 hours on weekdays
- Reasoning: Centralizes communication and integrates well with GitHub notifications
- Dissenting Opinions: None
- Why the group proceeded anyway: N/A
Deferred Items
- Project idea and scope: Not yet assigned — carry to next meeting
- GitHub repo and branch protection setup: Pending role confirmation first
Action Items
Task 1: Draft and circulate team charter for signatures
- Assigned To: Evan Marriott, Nicole Sutedja
- Due Date: TBD
- Status: In Progress
Task 2: Set up GitHub repo, project board, and branch protection rules
- Assigned To: Kaley Chung
- Due Date: TBD
- Status: Not Started
Task 3: Edit and publish team introduction video
- Assigned To: All Members
- Due Date: TBD
- Status: In Progress
Task 4: Join team Slack and confirm access to GitHub org
- Assigned To: All Members
- Due Date: TBD
- Status: Not Started
Media