Weekly Meeting 9 (10.05.2026)

Spring 2026 - Meeting Report #9

📅 Meeting Information

• Topic: Final Milestone Deliverables — status, missing pieces, and in-person coding session planning
• Date: 2026-05-10
• Time: 15:00 –
• Location: Google Meet
• Scribe: Mehmet Bora Sarıoğlu

---

👥 Participants

Name	Status
Burak Öğüt	Present
Amin Abu-Hilga	Present
Muhammet Sami Çakmak	Present
Övgü Su Afşar	Present
Mehmet Bora Sarıoğlu	Present
İbrahim Kayan	Present
Beratcan Doğan	Present

---

📑 Agenda

1. Walkthrough of the Final Milestone Deliverables wiki skeleton and the parent tracking issue #424.
2. Per-subgroup status update — what shipped this week, what is in-flight, what is still missing.
3. Schedule in-person coding sessions to close the remaining gaps before the 2026-05-12 release deadline.
4. Confirm individual contribution responsibilities and per-member AI prompt log expectations.

---

💬 Discussion

• Final Milestone Deliverables walkthrough: The team reviewed the structure of the official deliverables — a single wiki page covering Meeting Notes, Project Documentation, Executive Summary, Progress Based on Teamwork (sections 4.1–4.7), Individual Contributions, and Final Software Release & Setup. The deliverables are tracked under parent issue #424 with 11 section-level sub-issues (#413–#423), each with its own assignees, acceptance criteria, and links to the relevant wiki skeleton sections.

• Backend status: Most of the major Final Milestone surface has shipped on dev and main: the auto-ban system (#134, PR #380), mentorship milestones (#283, PR #378), shared-goal precondition (#335, PR #390), progress aggregation (#334, PR #391), unified mentorship timeline (#332, PR #392), social feed posts / interactions / feeds / search / push fanout (#347, #348, #349, #350), follow / unfollow + recommendations (#343, #344), and reporting & moderation (#135). All five Lab 8 backend bugs (#270–#274) are closed. Outstanding backend work for the deliverables is concentrated in §4.6 (HTML test report generation pipeline for Maven Surefire) and §4.5 (per-standard PR/code citations on the Use of Standards page).

• Web status: The web subgroup flagged that several Lab 6 and Lab 8 follow-up surfaces remain open: Active Mentorship Detail Page (#120), Conversations & Chat UI (#121), Chat Attachments (#122), Calendar View (#123), Meeting CRUD UI (#124), Task UI (#125), Progress Dashboard (#126), Mentee Cancellation UI (#127), Mentor Reporting UI (#128), Notifications Page (#129), Advanced Search Filters (#139), plus the post-MVP recommendation cards (#286), mentor-to-mentor messaging UI (#287), milestones UI (#288), reminder preferences (#289), and the location field on user profile (#291). The Sidebar / Dashboard count discrepancy bug (#255) and the Navbar dropdown counts bug (#266) are also still outstanding. The team agreed that not all of these can ship by 2026-05-12; the priority is the surfaces that the backend already supports and that the demo will exercise.

• Mobile status: The mobile subgroup confirmed that the progress tracking & milestones screens (#247) and native push notifications (#249) are the priority items for the in-person sessions. Social Feed mobile surfaces (refined per Lab 10 — feed tabs, post creation with hashtags, post interactions) are also in scope.

• Final SRS audit: The team agreed that linking the existing Requirements wiki page as the "Final SRS" requires an audit pass first — drop MVP-only language, ensure all post-MVP requirements that shipped (social feed, follow, milestones, ban system, progress aggregation, timeline) are present and accurate. The SRS audit is hidden inside #413; a half-day of one person's time is the rough budget.

• Test reports (HTML + XML × 3 layers, §4.6): The backend already emits JUnit XML via Surefire; HTML output requires either maven-surefire-report-plugin (run via mvn surefire-report:report-only) or the existing Surefire plugin's report goals. Web is on Vitest (which can emit JUnit XML and HTML via its built-in reporters). Mobile needs jest-html-reporter + jest-junit. Reports will land in a /reports/ directory at the repo root and be linked from §4.6.

• Per-member AI prompt logs: Seven Prompts-<Surname> wiki pages already exist as skeletons in the wiki. Every member is responsible for populating their own page with the prompts they used during the milestone (tool name, prompt text or summary, artifact produced, brief reflection). Sub-point 5.5.2 of each member's Individual Contributions subsection links to their prompts page.

• Live deployment & release artefacts (§6): The production HTTPS URL must be live, the final-milestone Git tag must point to a main commit, the 1.0.0 GitHub Release must be cut as a non-pre-release with the live URL in its notes, and the mobile .apk must be attached as a release asset. Hard deadline: 2026-05-12, 22:00 — this is four days earlier than the rest of the deliverables. Tracked in #423.

• README upgrade: The team noted that the current root README.md is short ("see CONTRIBUTING.md") whereas the spec requires a complete deploy-from-zero guide for both web and mobile, with docker-compose.yml, example .env, dev + prod setups, data seeding, default credentials, and database migration documentation. A teammate testing the README on a clean machine before submission was reaffirmed as a graded component.

• Future Work reference: A standalone Future Work wiki page was added to capture the Lab 9 19-phase roadmap items that won't ship in the Final Milestone (Communities, GDPR/KVKK, anti-abuse hardening, performance load validation, observability) plus stretch ideas. It is not a deliverable; it is a reference for any continuation of the project.

---

⚖️ Decisions

• Decision 1: Two in-person coding sessions are scheduled to close the remaining gaps before the 2026-05-12 release deadline:
  • Monday, 2026-05-11 — 10:00 AM
  • Tuesday, 2026-05-12 — 14:00
• Decision 2: The 11 sub-issues under #424 stand as the authoritative ownership map for the Final Milestone Deliverables wiki page; assignees confirmed during this meeting.
• Decision 3: Each member commits to populating their own Prompts-<Surname> wiki page during this week; partial logs are acceptable provided they cover the milestone's substantive AI usage.
• Decision 4: Web subgroup will prioritise UI surfaces that the demo plan exercises and that the backend already supports; remaining surfaces are tracked but not blockers for the Final Milestone Report sign-off.
• Decision 5: §4.6 HTML test report tooling will be configured before the Tuesday in-person session so the reports can be generated, committed to /reports/, and linked into the wiki page during that session.
• Decision 6: Daily async status updates in the team channel until 2026-05-16; in-person sessions take priority over async work on Monday and Tuesday.

---

🚀 Actions Taken

Task Description	Assigned To	Priority	Deadline	Issue Link
Audit and finalise the Requirements wiki page as the linked Final SRS	Mehmet Bora Sarıoğlu	High	2026-05-13	#413
Draft the Executive Summary (six sub-points)	Mehmet Bora Sarıoğlu, Beratcan Doğan	High	2026-05-14	#414
Compile per-member rows for the Team Contribution Summary table	All members	High	2026-05-14	#415
Re-audit Status of Requirements (Completed / In Progress / Not Started)	Mehmet Bora Sarıoğlu, İbrahim Kayan	High	2026-05-14	#416
Confirm live Swagger UI; write the four sample API scenarios (one search-related)	Beratcan Doğan, İbrahim Kayan, Mehmet Bora Sarıoğlu	High	2026-05-12	#417
Capture screenshots of new/modified web + mobile UIs since MVP	Amin Abu-Hilga, Muhammet Sami Çakmak, Burak Öğüt, Övgü Su Afşar	High	2026-05-14	#418
Add per-standard PR/code citations to the Use of Standards page (Compliance Summary + Deep Dive)	Mehmet Bora Sarıoğlu	High	2026-05-14	#419
Generate verbose HTML + XML test reports for backend / web / mobile and commit to /reports/	Beratcan Doğan, İbrahim Kayan, Muhammet Sami Çakmak, Burak Öğüt	High	2026-05-12	#420
Take notes during the Final Demo and write reflections within 24h	İbrahim Kayan, Beratcan Doğan	High	2026-05-16 (post-demo)	#421
Each member fills their Individual Contributions subsection and Prompts log	All members	High	2026-05-16	#422
Cut the final-milestone tag, publish the 1.0.0 GitHub Release with .apk, deploy production, upgrade README	Beratcan Doğan, Amin Abu-Hilga	Critical	2026-05-12 22:00	#423

---

Next Meeting Date: in-person session on 2026-05-11 (Monday, 10:00).