Skip to content

Activity Log

ANTI edited this page Feb 28, 2026 · 3 revisions

January 29, 2026 - Planning Meeting

Attendees: Ryan Hua, Joshua Philip, Simerjit Grewal

Subject: Planning Milestone 01 Submission

Minutes:

  • Discussion of division of work for Milestone 01
  • Thoughts of features to be added
  • Discussion of role assignment for Milestone 02

Task Assignments:

  • Joshua Philip: Document weekly meetings, project proposal outlines
  • Ryan Hua: User stories, wireframes
  • Simerjit Grewal: Data planning, GitHub setup

Decisions Made:

  • Technology stack: Node.js backend, MySQL , HTML/CSS/JS frontend
  • Weekly meetings scheduled

February 25, 2026- Development Kickoff Meeting

Attendees: Ryan Hua, Joshua Philip, Simerjit Grewal

Subject: Planning Milestone 02 Development

Minutes:

  • Reviewed Milestone 02 requirements and compared to Milestone 01 wireframes
  • Divided development work among team members
  • Set deadline to have frontend and database ready before submission

Task Assignments:

  • Ryan Hua: Frontend pages (landing, auth, dashboard), task CRUD, filtering, sorting
  • Simerjit Grewal: Database schema design, backend skeleton with Express route stubs
  • Joshua Philip: Database design PDF, README updates, activity blog, Kanban board and review code

Decisions Made:

  • Use localStorage with mock data until backend API is ready in Milestone 03

Challenges:

  • Coordinating the frontend layout to match the wireframes from Milestone 01

February 27, 2026 - Pre-Submission Review Meeting

Attendees: Ryan Hua, Joshua Philip, Simerjit Grewal

Subject: Reviewing Milestone 02 Deliverables

Minutes:

  • Reviewed frontend, database schema, and backend skeleton as a group
  • Verified all user stories from proposal are covered
  • Confirmed all deliverables ready for submission

Task Assignments:

  • Simerjit Grewal: Finalized schema.sql and backend route stubs, pushed to repo
  • Ryan Hua: Completed frontend testing (register, login, CRUD, filter, sort, logout)
  • Joshua Philip: Created Database Design PDF, updated Kanban board, wrote activity blog

Decisions Made:

  • ON DELETE SET NULL on Tasks table to preserve tasks if team or user is removed
  • ON DELETE CASCADE on Team_Members for automatic cleanup
  • VARCHAR over ENUM for status and priority for flexibility

Challenges:

  • Getting the backend route stubs to follow a clean folder structure that separates routes from controllers

Clone this wiki locally