Skip to content

Individual Contributions Final

Jump to bottom
furkan kaan edited this page May 16, 2026 · 18 revisions

Individual Contributions — Final Milestone

Akif Emre Biçen (Frontend)

Responsibilities (Final Milestone):

  • Frontend development for post-MVP user-facing features: saved stories, "Stories Near Me" discovery, multi-location story posting, and anonymous story sharing.
  • Final milestone UI/UX pass across map, story, and profile surfaces for demo readiness.
  • Frontend bug fixing on the multi-location story popup and related map interactions.
  • UAT contribution and supporting documentation updates for the final release.

Main Contributions (Final Milestone):

  1. Saved Stories and "Stories Near Me": Implemented the full frontend save/bookmark logic and the "Stories Near Me" map button, including the saved-stories view and the proximity-based discovery flow [PR #268] .
  2. Multi-Location Story Posting: Built the multi-location story creation flow on the frontend so a single story can be pinned to multiple coordinates, and later fixed a related popup rendering bug on the map [PR #361]), [PR #394] .
  3. Anonymous Story Sharing: Implemented the anonymous sharing option in the story creation flow so users can publish stories without attaching their identity [PR #333].
  4. General UI/UX Pass and UAT: Delivered a final-milestone UI/UX consistency pass across core user surfaces and contributed UAT test coverage for assigned scenarios ([PR #363], [PR #392].

Significant Issues (Top 3 per category):

Code-Related:

  • [Issue #225]): Implement Saved Stories View — implemented the frontend save logic and the saved-stories listing for authenticated users (closed by PR #268).
  • [Issue #227]): Implement "Stories Near Me" Map — added the proximity-based discovery button and the radius-based listing on the map (closed by PR #268).
  • [Issue #241]: Multi-location story support — implemented the frontend flow for pinning a single story to multiple coordinates and the related map popup behavior.

Non-Code-Related:

  • Issue #304: Final milestone UAT contribution — contributed acceptance test coverage for assigned scenarios as part of release readiness (PR #392).
  • Final milestone UI/UX pass — coordinated and delivered the consistency improvements across map, story, and profile surfaces for demo readiness (PR #363).
  • Final delivery documentation — updated the project README for final submission (PR #397).

Pull Requests:

  • [PR #268]: Feat/frontend saved stories and stories near me — implemented the frontend save logic and the "Stories Near Me" map discovery flow.
  • [PR #316]: anon sharing imp — initial implementation pass for anonymous story sharing on the frontend.
  • [PR #333]: anon sharing imp — completed and merged the anonymous sharing flow.
  • [PR #361]: Feat/frontend multi location — implemented multi-location story posting on the frontend.
  • [PR #363]: general ui ux pass — final-milestone UI/UX consistency improvements across the application.
  • [PR #392]: Feature/uat akif tests — contributed UAT coverage for assigned acceptance scenarios.
  • [PR #394]: multiple-location-story-popup-fix — fixed popup rendering for stories that have multiple locations on the map.
  • [PR #397]: Update README.md — README updates for final delivery.

Conflict Resolution

  • The main conflicts during the final milestone came from features touching the same map and story surfaces in parallel (multi-location, saved stories, near-me, anonymous sharing). I resolved these by rebasing onto dev before merging, coordinating popup/marker interactions with the teammates working on tagging and reporting UI, and following up with a dedicated fix PR (#394) when the multi-location popup regressed after another merge.

AI Transparency & Documentation

  • I used AI coding assistants during the final milestone for implementation drafts, debugging, and reviewing my own diffs before opening PRs. Every change was manually validated, adapted to our frontend architecture, and tested locally before merging.
  • My prompts can be found here here

Individual Testing Efforts:

  • Set up the frontend unit testing infrastructure (Jest + jsdom) used by the team.
  • Contributed UAT coverage for assigned acceptance scenarios in [PR #392].

Additional Information:

  • Served as a presenter in the final demo.
  • Served as a frontend reviewer for teammates' pull requests across the semester.
  • Contributed to project documentation through the scenario template work and the test plan & coverage page.

Furkan Kaan Biçer (Backend)

Responsibilities (Final Milestone):

  • Backend development for story moderation, reporting, admin review, story removal, and user restriction flows.
  • Backend implementation of keyword tagging, AI-assisted tagging, tag search, semantic story search, and server-side filtering features.
  • Backend support for observability and release readiness through logging/monitoring integration and admin service separation.
  • Backend/API/unit/integration testing and UAT support for tagging and story discovery flows.

Main Contributions (Final Milestone):

  1. Moderation, Reporting & Admin Backend Completion: Implemented story report APIs, admin report review endpoints, story soft-delete/removal support, moderation logic, and user restriction behavior to support safer content management.
  2. Tagging & Search Backend Delivery: Built the keyword tagging backend, integrated AI-assisted tagging with fallback behavior, added tag persistence and tag response support, and extended story listing/search endpoints with tag-based and semantic search capabilities.
  3. Server-Side Filtering & Discovery Improvements: Added tag parameters to story search/nearby flows, implemented relevance ranking and hybrid search behavior, and updated API contracts, schemas, migrations, and tests for story discovery features.
  4. Logging, Monitoring & Service Stabilization: Integrated structured logging across backend layers, added monitoring documentation, separated admin service logic, and strengthened test coverage for final milestone release readiness.

Significant Issues (Top 3 per category):

Code-Related:

  • Issue/PR #297: Moderation Logic - Integrated moderation behavior into the reporting flow, including soft-delete handling and report-state updates.
  • Issue/PR #335: AI Tagging - Implemented AI-assisted story tagging, Gemini SDK integration, fallback logic, tag persistence, and related API/unit/integration tests.
  • Issue/PR #360: Semantic Search for Stories - Extended story search with semantic/hybrid search behavior, typo-tolerance support, updated API contracts, and test coverage.

Non-Code-Related:

  • Issue/PR #369: Log Monitoring - Prepared monitoring and logging documentation in docs/wiki/monitoring-and-logs.md and supported release observability.
  • Issue/PR #375: UAT Keyword Tagging - Contributed to final milestone QA by implementing Playwright UAT coverage for keyword tagging.
  • Issue/PR #382: TC_TAG_1 Keyword Tagging - Added mobile/Appium-oriented test support for the keyword tagging scenario.

Pull Requests:

  • PR #294: feat: report api - Implemented story report API endpoints, enums, migrations, and service logic.
  • PR #295: feat: review report api - Implemented admin report listing/filtering and report status update endpoints with comprehensive tests.
  • PR #296: feat: admin remove story api - Added admin-side story removal/soft-delete backend support with unit and integration tests.
  • PR #297: feat: moderation logic - Integrated moderation logic into the report system and added missing integration coverage.
  • PR #332: feat: keyword_tagging - Added keyword tag schema/model/service support, tag normalization, DB integration, response fields, and tests.
  • PR #335: feat: ai-tagging - Integrated AI-assisted tagging, fallback behavior, Gemini SDK support, background task handling, and test updates.
  • PR #357: feat: tag-search - Added tag search/filter support, relevance ranking, tag filter indexes, endpoint descriptions, and tests.
  • PR #360: feat: semantic-search-for-stories - Implemented semantic/hybrid story search behavior, typo mismatch handling, API contract updates, and test coverage.
  • PR #369: feat: log-monitoring - Integrated logging mechanisms across layers, revised config settings, added logging tests, and updated monitoring documentation.
  • PR #371: chore: separate admin service - Refactored admin logic into a dedicated service layer and updated related schemas/tests.
  • PR #375: test: uat-keyword-tagging - Added Playwright UAT coverage for TC_TAG_1 keyword tagging.
  • PR #380: feat: serverside-filtering - Added tag parameters to search/nearby APIs and updated service, unit, API, and integration tests.
  • PR #382: test: tc-tag-1-keyword-tagging - Added Appium/mobile E2E coverage for the keyword tagging scenario.
  • PR #388: feat: restrict-user - Implemented backend support for restricting users, including service integration and UAT/test fixes.

Conflict Resolution

  • The main coordination challenge in the final milestone was keeping backend search, tagging, moderation, and admin contracts aligned with frontend and QA expectations while multiple story-related flows were evolving in parallel. I resolved these issues by updating backend schemas and endpoints quickly, separating admin service logic where needed, adding missing migrations and indexes, and strengthening API/unit/integration/UAT coverage so regressions could be caught earlier.

AI Transparency & Documentation

  • During the final milestone, I used AI coding assistants, primarily OpenAI Codex, to accelerate backend implementation, debugging, test generation, and refactoring work. I used AI support for drafting service logic, exploring alternative API designs, identifying test gaps, and improving documentation wording.
  • I also used ChatGPT/Codex-style assistance for documentation-heavy tasks such as monitoring notes, milestone reporting, scenario wording, and contribution summaries. Even when AI helped produce implementation drafts or written content, I manually reviewed and validated the final changes before merging or submitting them. This included checking project architecture compatibility, reviewing logic correctness, updating tests, and ensuring the final behavior matched the intended backend contract.
  • In short, AI significantly accelerated my development and documentation workflow, but all final code, tests, documentation, and deliverables were manually reviewed and validated by me before being accepted.

Individual Testing Efforts:

Additional Information:

  • I contributed heavily to backend story infrastructure during the final milestone, especially around moderation, search, tagging, admin workflows, and release-readiness testing. I also prepared logging/monitoring documentation and supported final milestone QA by adding deterministic UAT/E2E coverage for the keyword tagging flow.

Beyza Nur Deniz (Backend)

Responsibilities (Final Milestone):

  • Backend development for core user interaction flows, including likes, comments, bookmarks, and notification-trigger behavior.
  • Backend implementation of integration-critical APIs for dashboard/profile and edit-profile flows.
  • Delivery of the story-audio transcription pipeline and backend support for transcription review before posting.
  • Backend-side testing and release-readiness support through API, unit, integration, and UAT work.

Main Contributions (Final Milestone):

  1. Story Interaction & Notification Backend Completion: Implemented the core backend APIs for likes, comments, and bookmarks, then extended these flows with notification triggers and notification-history fixes so interaction behavior remained consistent and reliable.
  2. Dashboard and Edit-Profile Backend Integration: Implemented authenticated dashboard APIs, optimized dashboard/engagement queries, and added edit-profile backend endpoints with user profile fields and migration support for end-to-end frontend integration.
  3. Transcription Workflow Backend Delivery: Built the audio transcription pipeline for uploaded story media, added the transcription preview endpoint used by the frontend review flow, and extended audio uploads to accept optional reviewed transcripts directly.
  4. Testing and Release Stabilization: Added backend API/unit/integration coverage for interaction, profile, dashboard, and transcription flows, and implemented the Playwright UAT for TC_MEDIA_2 to make the transcription review scenario deterministic and release-ready.

Significant Issues (Top 3 per category):

Code-Related:

  • Issue #207: Add Notification Triggers for Interactions - Added notification creation for likes, comments, and bookmarks, and later fixed notification persistence after comment deletion.
  • Issue #236: Backend: Dashboard APIs - Implemented the authenticated dashboard endpoints and optimized the related summary/statistics queries for frontend integration.
  • Issue #315: Backend: Story creation page audio transcription - Completed backend support for the transcription review flow through preview and upload-side transcript handling, on top of the audio transcription pipeline.

Non-Code-Related:

  • Issue #304: UAT: Implement TC_MEDIA_2 — Audio Transcription Review Before Posting (Playwright) - Contributed to final milestone QA and release readiness by implementing the acceptance test for the transcription review flow.
  • Issue #88: Create Lab 6 Report - Contributed to project documentation and milestone reporting by preparing lab report content.
  • Issue #76: Upload Weekly Meeting Notes to Wiki: Week 5 - Documented team decisions and follow-up items as note-taker.

Pull Requests:

  • PR #254: feat: add story like and unlike endpoints - Implemented the backend like/unlike API for story interactions.
  • PR #255: feat: implement comment API - Implemented the backend comment API and related validation/service logic.
  • PR #256: feat: implement bookmark API - Implemented the backend bookmark/save flow for stories.
  • PR #259: feat: add notification triggers for story interactions - Added notification creation for story interactions and preserved notification history after comment deletion.
  • PR #291: add story like summary endpoint - Extended interaction support with like-summary data for frontend consumption.
  • PR #299: Feat/dashboard - Implemented authenticated user dashboard APIs and optimized engagement/statistics queries.
  • PR #314: feat: add edit-profile backend endpoints and user profile fields - Completed backend edit-profile support with model, migration, service, and test updates.
  • PR #298: feat: add audio transcription pipeline for uploaded story media - Added transcript persistence and backend transcription flow for uploaded story audio.
  • PR #317: feat: add backend transcription preview endpoint for story audio - Added the preview endpoint used by the frontend transcription review flow.
  • PR #350: feat: accept optional transcripts on story audio uploads - Allowed reviewed transcript submission during audio upload and skipped unnecessary background transcription when transcript text was already provided.
  • PR #372: test: Add Playwright UAT for audio transcription review flow - Implemented deterministic Playwright coverage for TC_MEDIA_2.

Conflict Resolution

  • The main coordination challenge in the final milestone was keeping backend contracts aligned with frontend integration needs while multiple user-facing flows were being completed in parallel. This was especially visible in interaction APIs, notification behavior, dashboard/edit-profile integration, and transcription review. I resolved these issues by updating backend contracts quickly, addressing missing support such as optional transcript handling, and strengthening tests so integration problems could be caught earlier.

AI Transparency & Documentation

  • At the beginning of the semester, I mainly used Antigravity; later I switched to OpenAI Codex as my primary AI coding assistant.
  • I used these tools not only for debugging and review support, but also for generating implementation drafts, suggesting refactors, speeding up endpoint/service/test development, and exploring alternative solutions during backend development.
  • In addition to coding-oriented assistants, I also used ChatGPT for documentation-heavy tasks such as reporting, scenario writing, wording improvements, and structuring written deliverables.
  • Even when AI produced substantial implementation or writing assistance, I manually validated every change before merging or submitting it. This included checking logic correctness, adapting outputs to our project architecture, running or updating tests when needed, and making sure the final result matched the team’s intended behavior and quality expectations.
  • In short, AI significantly accelerated my development and documentation workflow, but all final code, documentation, and deliverables were manually reviewed and validated by me before being accepted.
  • The prompt list is available here.

Individual Testing Efforts:

Additional Information:

  • I served as the team communicator during the semester.
  • I was a presenter in the first demo.
  • For the second demo plan, I prepared the user-story-based presentation scenarios used to shape the demo flow.
  • I was the note-taker for Weekly Meeting 1 and Weekly Meeting 5.
  • I also contributed to project documentation by preparing several lab reports and other wiki/documentation artifacts during the semester.

İbrahim İlter (Frontend)

Responsibilities (Final Milestone):

  • AI-powered tagging system UI.
  • Tag-based search and filtering.
  • Content reporting interface.
  • Admin moderation panel.

Main Contributions (Final Milestone):

  • Developed the tagging UI system that displays AI-generated tags on story detail pages, map popups, and search result cards.
  • Added a comprehensive filter sidebar to the search page supporting year range, location, and tag filtering; integrated the map's "Near Me" radius panel into the Filters section.
  • Implemented the story reporting UI for authenticated users and the admin moderation panel for managing reported content.

Significant Issues (Top 3 per category):

Code-Related:

  1. PR #240 — Frontend: Keyword Tagging UI: Implemented display of AI-generated tags as chip components across story detail, edit, and creation pages using tags.js and renderTagChips().
  2. PR #243 — Frontend: Tag-Based Search & Filtering UI: Built tag chip filter, year range slider, and location filter on the search page with URL parameter synchronization and client-side filtering logic.
  3. PR #229 — Implement Admin Moderation Panel: Created an admin-only moderation dashboard with report queue display, story deletion, user restriction, and report dismissal capabilities.

Non-Code-Related:

  1. Issue #228 — Implement Reporting UI: Designed and implemented the reporting modal with three reason options and toast notifications for authenticated users on story detail pages and map popups.

Pull Requests:

  1. PR #266 — Implemented the full reporting UI and admin moderation panel covering report, delete, restrict, and dismiss actions.
  2. PR #349 — Introduced the AI-powered tagging system across the application with 50 Jest tests.
  3. PR #373 — Integrated the tagging system UI with a search filter sidebar and merged the map distance selector into the Filters panel.
  4. PR #395 — Consolidated three frontend fixes: location button fly-to, multi-location popup card redesign, and search API parameter correction.
  5. PR #396 — Fixed the invisible search bar on mobile by removing the hidden md:flex restriction from the site header and adjusting responsive layout.

Conflict Resolution: Resolved a merge conflict in map.html during PR #373 caused by diverging changes between branches. In PR #349, a 404 search error flagged by the reviewer was fixed with a follow-up commit before approval.

AI Transparency & Documentation:

  1. Claude used as the primary coding assistant.
  2. Prompts: Ibrahim Ilter Prompt Log

Individual Testing Efforts:

Additional Information:

  • I was a timer in the demo.
  • I reviewed several pull requests across the team.

Muhammed Efe Özavcı (Backend)

Responsibilities (Final Milestone):

  • Implementing three major backend features: anonymous story sharing, multi-location story support, and the gamification/badge system.
  • Building the geospatial query layer for the nearby stories API using the Haversine formula expressed in pure SQLAlchemy, without requiring a PostGIS extension.
  • Maintaining a clean, linear Alembic migration chain across all feature branches by resolving inter-branch migration conflicts and keeping revision IDs consistent.
  • Writing the full acceptance test suite for TC_STORY_5 (Anonymous Story Sharing): a Playwright UAT spec running in CI and a WebdriverIO/Appium mobile E2E spec.

Main Contributions (Final Milestone):

  1. Geospatial Nearby Stories: Implemented the Haversine radius query for nearby stories as a pure SQLAlchemy expression requiring no PostGIS extension, added the GET /stories/nearby endpoint, and created B-tree DB indexes on latitude, longitude, and place_name to keep queries fast at scale (PR #260, PR #261, PR #262).
  2. Anonymous Story Sharing Backend: Added the is_anonymous boolean column to the Story ORM model, wrote Alembic migration 0015, and updated story_service.py so all public API responses replace the author identity with null while preserving the real user_id in the database for moderation purposes (PR #311).
  3. Multi-Location Story Support: Created the StoryLocation ORM model and story_locations table (Alembic migration 0016) with a foreign key to stories, an ordering integer, and cascade="all, delete-orphan", and updated story schemas and service to accept and persist an ordered list of locations per story (PR #337).
  4. Gamification & Badge System: Designed and implemented the Badge and UserBadge ORM models with a composite primary key to prevent duplicate awards, seeded three milestone badges in migration 0019, and built a batch-query rules engine in badge_service.py that awards qualifying badges after each story creation and exposes them on GET /auth/me (PR #339).
  5. Playwright UAT — TC_STORY_5: Wrote the full acceptance test for anonymous story sharing: two users plus an unauthenticated visitor context, story ID captured from the POST /stories API response via waitForResponse before page redirect, asserting both reader and visitor see "Anonymous" in #story-author. Runs in CI as part of the UAT Tests GitHub Actions job (PR #365).
  6. Appium Mobile E2E — TC_STORY_5: Wrote the full WebdriverIO/Mocha spec for TC_STORY_5 using a window.fetch interceptor to capture the story ID before navigation, browser.execute() for JS-injected interactions, and this.skip() to self-skip gracefully when no WebView context is available (PR #347).

Significant Issues (Top 3 per category):

Code-Related:

  • Issue #232: Backend: Anonymous Story Sharing — designed and implemented the is_anonymous DB column, Alembic migration, service-layer anonymization logic, and moderation-safe storage of the real author identity.
  • Issue #231: Backend: Multi-Location Story Support — added the StoryLocation ORM model and story_locations table, wired a one-to-many cascading relationship on the Story model, and updated all related schemas and service methods.
  • Issue #237: Backend: Gamification & Badge System — designed two new ORM models, a rules engine service, badge seeding in the migration, and integrated badge awarding into the story creation flow with automatic exposure on /auth/me.

Non-Code-Related:

  • Issue #274: Write Acceptance Test Scenario: TC_STORY_5 — Anonymous Story Sharing — authored the complete acceptance test specification: defined preconditions, step-by-step test actions with correct selectors, test data, post-conditions, and linked requirements 1.1.8.1 and 1.2.8.1. This document served as the authoritative specification for both the Playwright UAT and Appium mobile E2E implementations.
  • Issue #53: Create a wiki page about stakeholder meeting — documented the stakeholder meeting outcomes on the project wiki, contributing to the team's requirements elicitation and communication records.
  • Issue #43: Finalize the Class Diagram and Sequential Diagram — helped finalize the core UML artifacts that guided the backend implementation throughout the project.

Pull Requests:

  • PR #260: feat: implement Haversine geospatial query for nearby stories — Haversine radius query in pure SQLAlchemy with PUBLISHED/PUBLIC story filtering and configurable radius.
  • PR #261: feat: add GET /stories/nearby endpoint — exposes the Haversine query with lat, lng, and optional radius_km query parameters.
  • PR #262: feat: add DB indexes for search and geospatial queries — B-tree indexes on stories.latitude, stories.longitude, and stories.place_name.
  • PR #311: feat: backend anonymous story sharing (#232) — is_anonymous DB column, Alembic migration 0015, and service-layer identity masking in all public API responses.
  • PR #337: feat: add multi-location story support — StoryLocation ORM model, Alembic migration 0016, one-to-many cascading relationship, and updated story schemas and service.
  • PR #339: feat: implement gamification badge system — Badge and UserBadge ORM models, Alembic migration 0019 with badge seeding, batch-query rules engine in badge_service.py, and badge exposure on GET /auth/me.
  • PR #365: test: implement TC_STORY_5 Playwright UAT for anonymous story sharing — full two-user + visitor scenario, runs in CI via the UAT Tests GitHub Actions job.
  • PR #347: feat: mobile Appium E2E spec for TC_STORY_5 - anonymous story sharing — WebdriverIO/Mocha spec with window.fetch interceptor for story ID capture and this.skip() guard for non-mobile environments.

Conflict Resolution

The main conflicts during the final milestone arose from multiple feature branches modifying the same backend files in parallel. I resolved these by coordinating merge order with the team and rebasing onto dev before opening PRs. The most significant conflict was the duplicate Alembic revision ID (0020) that broke CI — after the fix landed in dev, I rebased both affected branches and force-pushed to restore the pipeline.

AI Transparency & Documentation

I used Claude (via Claude Code) as my primary AI coding assistant during the Final Milestone for implementation drafts across backend feature endpoints and acceptance test flows, debugging, and reviewing my own diffs before opening PRs. Every output was manually reviewed, adapted to the project's existing architecture and conventions, and tested locally before being pushed. No AI-generated suggestion was merged without being fully understood.

My prompt log is available here.

Individual Testing Efforts:

  • Playwright UAT (Web):

    • Implemented the full acceptance test for TC_STORY_5 — Anonymous Story Sharing in frontend/tests/uat/story.spec.js (PR #365).
    • Test registers two users and an unauthenticated visitor context, captures the story ID from the POST /stories API response via waitForResponse before page redirect, and asserts both the logged-in reader and unauthenticated visitor see "Anonymous" in #story-author.
    • Runs automatically in CI as part of the UAT Tests GitHub Actions job.

  • Mobile E2E (Appium/WebdriverIO):

    • Implemented the full WebdriverIO/Mocha spec for TC_STORY_5 in frontend/tests/mobile-e2e/specs/tc-story-5.spec.js (PR #347).
    • Uses a window.fetch interceptor to capture the story ID before the WebView navigates away, browser.execute() for JS-injected interactions (matching the established auth.spec.js pattern), and this.skip() to self-skip gracefully in non-mobile environments.
    • Runs locally against the Android APK; excluded from CI per team convention.

  • Backend Unit Testing:

  • Backend API & Integration Testing:

Additional Information:

  • Resolved Alembic migration chain conflicts across all feature branches, including a rebase onto the patched dev after a duplicate revision ID broke alembic upgrade head in CI, restoring the pipeline for both PR #365 and PR #347.
  • Served as a PR reviewer for backend pull requests during the Final Milestone, providing feedback on migration ordering, schema consistency, and service layer correctness.
  • Assigned as the Ana Sunucu (main presenter) for the final demo per the Final Demo Plan.

Muhammed Mustafa Öztürkmen (Backend, DevOps)

Responsibilities (Final Milestone):

  • Backend feature delivery: Google OAuth integration, story view counts, timeline API, and search infrastructure (fuzzy / semantic search).
  • Transcription service reliability: Whisper OOM fix and full migration to the OpenAI Whisper API.
  • DevOps: CI/CD release and test workflow design, CI job-ordering fixes, and developer tooling (localrun.sh).
  • Team testing lead: built the shared automated testing infrastructure — CI test jobs, JUnit report generation, UAT/E2E/Appium skeletons — that the whole team used to implement and run their test scenarios.
  • Documentation: API docs, wiki architecture and deployment pages, .env.example updates.

Main Contributions (Final Milestone):

  1. Google OAuth Backend Integration: Implemented the full OAuth flow — login redirect, callback token exchange, CSRF state-cookie validation, and email-based account linking — with unit and API tests.

  2. Search Infrastructure and Core Backend Features: Added fuzzy/typo-tolerant place-name search via pg_trgm, story view-count tracking with atomic DB increment and user-stats aggregation, and the GET /stories/timeline endpoint with location filtering and historical-date ordering.

  3. Transcription Service Reliability: Fixed the Whisper OOM crash on Render with a per-request load/del + semaphore pattern, then migrated fully to the OpenAI Whisper API to eliminate the local model.

  4. DevOps, CI/CD, and Testing Infrastructure: Built the release.yml release workflow, fixed CI job ordering and added a parallel UAT job, established the Playwright UAT skeleton and TC_AUTH_2 + Appium mobile E2E tests, delivered a 9-scenario Playwright E2E suite with a tag-persistence bug fix, and updated technical documentation and wiki pages.

Significant Issues (Top 3 per category):

Code-Related:

  • Issue #238: Backend: Google OAuth Integration — implemented the full OAuth flow including CSRF state-cookie validation and email-based account linking (closed by PR #286).
  • Issue #345: Enhancement: fuzzy/typo-tolerant place name search using pg_trgm — added trigram similarity ranking so queries like "istanubl" match Istanbul (closed by PR #359).
  • Issue #300: Backend: Timeline View API — designed and implemented the GET /stories/timeline endpoint with location-based filtering, historical-date ordering, and pagination (closed by PR #354).

Non-Code-Related:

  • Issue #269: Prepare Lab 9 Acceptance Test Cases — defined and documented the acceptance test scenarios for the final milestone, establishing the test structure used across the team.
  • Issue #252: DevOps: Update Technical Documentation & Wiki — updated API docs (Swagger descriptions), .env.example, and added wiki pages for architecture and deployment (closed by PR #379).
  • Issue #270: Write Acceptance Test Scenario: TC_AUTH_2 — Google OAuth Login — authored the acceptance test scenario specification for the Google OAuth login flow.

Pull Requests:

  • PR #253: feature: accept audio/webm MIME type for live recorded audio — enabled browser-recorded audio uploads by supporting the audio/webm MIME type.
  • PR #257: test: add unit tests for video/webm recording upload — added unit tests covering the new video/webm MIME type path.
  • PR #264: test: add integration tests for recorded media story flow — end-to-end integration coverage for the recorded media upload and story flow.
  • PR #280: chore: enhance localrun.sh — port-conflict detection, .env bootstrap, Docker race-condition fix, and graceful shutdown.
  • PR #285: ci: fix job order and add parallel UAT job — moved API tests before integration tests in CI and added a parallel UAT job (closes #281).
  • PR #286: feat: add Google OAuth login and registration — full OAuth backend with CSRF state-cookie protection and account linking (closes #238).
  • PR #292: test: add Playwright UAT skeleton with TC_AUTH_1 — established the UAT test infrastructure used by the whole team, with TC_AUTH_1 passing in CI (closes #282).
  • PR #312: ci: add release workflow for final milestone packaging — release.yml composing CI → deploy → GitHub Release with JUnit-based test-result body (closes #283).
  • PR #351: fix: unload Whisper model after each transcription to free memory — per-request load/del and semaphore to prevent concurrent model instances and OOM restarts.
  • PR #353: feat: add story view count — atomic increment on detail fetch, exposed on all StoryResponse payloads and user stats (closes #346).
  • PR #354: feat: add GET /stories/timeline endpoint — chronological story feed with Haversine or ILIKE filter, date_start ASC NULLS LAST ordering, and limit/offset pagination (closes #300).
  • PR #359: feat: fuzzy/typo-tolerant place name search using pg_trgm — trigram similarity ranking for typo-tolerant search results (closes #345).
  • PR #362: test: implement TC_AUTH_1 & TC_AUTH_2 (Playwright UAT + Appium mobile E2E) — Google OAuth UAT and both auth scenarios as Appium mobile specs; established the page.evaluate() OAuth mock pattern used by the team (closes #302, #321).
  • PR #364: imp: replace faster-whisper with OpenAI Whisper API — removed local model entirely; async httpx call to OpenAI, graceful skip when key unset (closes #249).
  • PR #377: imp: UI/UX enhancements for map, story create, and story detail — visual bug fixes and usability improvements across map, story creation, and detail pages (closes #248).
  • PR #378: test: extend seeded_db with media file, DATE story, and admin story — richer fixture covering media files, exact-date stories, and admin-owned stories, with 3 new integration tests (closes #224).
  • PR #379: docs: update API docs and add wiki architecture and deployment pages — expanded Swagger descriptions, updated .env.example, and added architecture and deployment wiki pages (closes #252).
  • PR #389: test: Playwright E2E suite + fix tag persistence on story create/update — 9 Playwright E2E scenarios covering core flows (story CRUD, search, view count, multi-location, like, comment, tag search, timeline, edit), a dedicated playwright.e2e.config.js, full e2e CI job wiring, and a backend bug fix for silent tag drops on POST/PUT /stories.

Conflict Resolution

  • The main conflicts I encountered were Alembic migration ordering: multiple backend PRs landing in parallel each added a migration, which caused duplicate-head failures when two revisions pointed to the same parent (alembic upgrade head fails with "Multiple head revisions"). I resolved these by running alembic heads locally before pushing any new migration and adding empty merge migrations when needed. I also flagged the PR #337/PR #339 dual-head issue during code review so the author could fix it before merge. For the OAuth backend work, coordinating the CSRF state-cookie pattern with the frontend callback page required close communication to keep the token handoff consistent.

AI Transparency & Documentation

  • I used Claude (Anthropic) as my primary coding assistant throughout the final milestone, for implementation drafts, debugging, test generation, and reviewing my own diffs before opening PRs. I also used it for documentation tasks such as wiki page structuring, API description writing, and report drafting.
  • Every AI-generated output was manually reviewed, validated against the project architecture, and tested locally before being committed or merged.
  • My prompts can be found here.

Individual Testing Efforts:

  • Playwright UAT:

    • Established the Playwright UAT infrastructure (Jest-independent config, CI job, JUnit output) in frontend/tests/uat/ (PR #292), which the whole team used for their UAT scenarios.
    • Authored TC_AUTH_1 (register → login → map) and TC_AUTH_2 (Google OAuth login) in frontend/tests/uat/auth.spec.js (PR #362). Established the page.evaluate() OAuth redirect-mock pattern adopted by teammates.

  • Playwright E2E:

  • Appium Mobile E2E:

  • Backend Unit and API Testing:

    • Added unit and API tests for the Google OAuth URL builder and CSRF state validation (PR #286).
    • Added TestGetTimelineStoriesService (8 unit tests) and TestTimelineStoriesAPI (11 API tests) for the timeline endpoint (PR #354).
    • Updated TestGetStoryDetailByIdService and dashboard API tests to cover view-count increment and aggregation behavior (PR #353).
    • Updated test_transcription_service.py mock patch paths after the OpenAI Whisper API migration (PR #364).

  • Backend Integration Testing:

    • Extended the seeded_db fixture and added 3 integration tests (test_story_detail_includes_seeded_media_file, test_date_precision_story_retrievable, test_admin_story_appears_in_public_listing) in backend/tests/integration/ (PR #378).
    • Added integration tests for the recorded media story flow (PR #264).

Additional Information:

  • Served as app controller during the final demo — shared the live screen of both the web and mobile versions of the application while teammates presented.
  • Acted as code reviewer across the milestone, covering backend feature PRs (like/comment/bookmark APIs, dashboard, anonymous story sharing, audio transcription pipeline, multi-location story support, gamification badges, tag filtering & discovery, semantic search), frontend PRs (general UI/UX pass, Appium mobile E2E skeleton), and the final dev → main release merge. Provided multi-round feedback on several PRs, identifying blockers and requesting targeted fixes before approval.
  • Served as the primary server on-call throughout the milestone — monitored the Render deployment continuously and was first to identify and resolve production incidents as they surfaced, including Alembic multiple-head crashes blocking deploys and the Whisper model memory spikes causing repeated backend restarts.
  • Investigated and evaluated external services for the team: researched Gemini API parameters for AI auto-tagging (discovered and fixed the markdown-fence parsing bug in auto-tag output) and the OpenAI Whisper API as a Render-compatible transcription backend, providing the technical foundation for both integrations.
  • Contributed to project documentation through weekly meeting notes, lab reports, and customer meeting write-ups during the semester.

Enes Hamza Üstün (Frontend)

Responsibilities (Final Milestone):

  • Frontend integration of high-priority user flows (profile/edit-profile, interactions, transcription).
  • UAT/E2E stabilization for release readiness (Playwright/Appium + CI compatibility).
  • Final UI/UX pass on map/story/profile surfaces for demo and grading reliability.

Main Contributions (Final Milestone):

  1. Profile & Edit Profile Full Backend Integration: Removed remaining mock behavior, connected profile/edit-profile pages to live APIs, synchronized password/avatar/bio/location flows, and added/updated unit tests for profile update paths.
  2. Story Interaction Completion (Likes/Comments + View Counts): Finalized frontend-to-backend wiring for likes/comments and connected view-count behavior to backend-supported flows, including test updates.
  3. Transcription Workflow Delivery: Implemented transcription-related UI in story flows and connected transcription editing/review behavior to backend-compatible paths.
  4. Release Stabilization via UAT/CI and UI Pass: Wrote and refactored dashboard UAT tests (web + optional mobile), fixed base-URL/CI reliability issues, and polished final UX details (date picker behavior, map popup/sidebar/spiderfy, auth-state navigation visibility).

Significant Issues (Top 3 per category):

Code-Related:

  • Issue #226: Implement Comment UI - Implemented and integrated the comment UI flow on story detail pages, then aligned it with backend-connected behavior and related tests.
  • Issue #245: Frontend: User Dashboard Page - Contributed dashboard/profile integration work including view-related UI/data handling and validation.
  • Issue #244: Frontend: Audio Transcription Review UI - Implemented/refined frontend transcription review flow and connected it to backend-compatible behavior.

Non-Code-Related:

  • Issue #248: Frontend: UI/UX Final Pass - Contributed final milestone polish and consistency improvements across core user journeys.
  • Issue #276: Write Acceptance Test Scenario: TC_DASH_1 — User Dashboard View Count - Aligned implementation and verification flow with acceptance criteria for final QA readiness.
  • Issue #278: Create Customer Meeting notes 2 - Contributed to stakeholder communication and milestone alignment by documenting customer meeting outcomes and action items for the team.

Pull Requests:

  • PR #336: Feat/audio review UI - Connected story creation transcription review UI to the backend preview endpoint, improved retry/error handling, and stabilized transcript flow UX.
  • PR #353: feat: add story view count — increment on detail fetch, expose on API and user stats - Completed end-to-end view-count integration.
  • PR #263: Feat/comment UI - Implemented the comment interface on story detail pages and established the frontend structure later used for backend-connected interaction flows.
  • PR #319: Feat/connect edit profile to backend - Completed profile/edit-profile API wiring and related frontend validation/testing.
  • PR #258: Feature/like button UI - Implemented the initial like-button interaction flow on story detail pages and prepared the frontend structure for backend integration.
  • PR #293: fix: the frontend of the like and comment features are connected to backend - Completed end-to-end frontend-backend wiring for likes/comments and updated tests to ensure interaction reliability.
  • PR #374: Test/TC_DASH_1 - Contributed dashboard UAT validation work for the user view-count scenario to improve final milestone test coverage and confidence.

Conflict Resolution

  • Our main conflicts came from working asynchronously. Sometimes, I would finish a frontend feature before the backend team had created the endpoint for it. To keep working, I had to use mock data and bypass the missing endpoint errors. Once the backend team provided the endpoints, I connected them, but this often caused new bugs. To fix these issues quickly, we stayed in constant communication.

AI Transparency & Documentation

  • At the start of the term i mainly used Antigravity for coding and Gemini for brainstorming. At the 10th week changed to Cursor. It became my main tool for both design generations and coding the features. Other than debugging, i did not write much code. I could not find my chat histories in antigravity and gemini, however, i added my plans that are created with Cursor and chat histories in this link.

Individual Testing Efforts:

I contributed to testing mainly on the frontend and UAT side, focusing on making core user flows reliable for final milestone delivery.

  • UAT (Playwright/Web):

    • Implemented and refined TC_DASH_1 dashboard scenario in frontend/tests/uat/dashboard.spec.js.
    • Improved test robustness by adjusting base URL handling for local/CI environments and reducing flaky behavior.(Still it does not work on the github actions because this test required having two sessions and initial data which made the test so complex for local machine so it is tested on the dev deployment)
    • Aligned test behavior with final acceptance expectations for profile view-count/dashboard-related flows.

  • Mobile E2E Support (Appium):

  • Frontend Unit Testing:

  • Overall Testing Impact:

    • My testing work focused on end-to-end confidence for high-visibility user journeys: dashboard/profile behavior, story interaction (like/comment), and transcription review flow.

Additional Information: In the final milestone, I focused on integration completion and stability: closing frontend-backend gaps, improving UAT reliability under CI, and ensuring that core user journeys (profile management, story interaction, transcription, and dashboard checks) worked consistently for final evaluation.

Alper Vural (Frontend)

Responsibilities:

  • Frontend development for new post-MVP features (audio/video recording, badges & public profile, story timeline, Google OAuth UI)
  • End-to-end test infrastructure: Playwright UATs on web and Appium/WebdriverIO mobile E2E skeleton
  • Mobile (Capacitor/Android) packaging and mobile-specific UI fixes
  • Frontend release engineering for the Final Milestone (final UI/UX pass, dev → main release merge)

Main Contributions:

  • Implemented the in-browser audio/video recording interface on the story creation page, including camera capture controls and unit-tested recording helpers (PR #267).
  • Built the story timeline page (chronological nearby-stories view with radius and date filters) and added clustered story markers + timeline links on the map and story detail pages (PR #352).
  • Implemented the badges system on the frontend: badge assets on profile pages, post-publish badge unlock popup, and wired backend awarding (also corrected the badge rule type so awards return correctly) (PR #355).
  • Completed the Google OAuth frontend handoff: Google-branded sign-in buttons on index.html / register.html, OAuth callback page that stores the returned JWT and redirects to the map, plus unit tests for the button and callback (PR #341).
  • Set up the mobile end-to-end test stack (Appium + WebdriverIO) with config, helpers, smoke test, and Lab 9 placeholder specs, and excluded it from the Jest run (PR #329).
  • Authored the first badge user acceptance test (TC_BADGE_1) in Playwright covering award, profile display, and no-duplicate-award on a second story; also fixed a duplicate Alembic revision that was blocking backend startup (PR #366).
  • Migrated UAT and mobile E2E date inputs to the native yyyy-mm-dd format after the date field switched to type="date" (PR #385).
  • Performed the final dev → main release merge for the Final Milestone (PR #391).

Significant Issues (Top 3 per category):

Code-Related:

  • Issue #301: Frontend: Timeline View UI — chronological story list for a location (closed by PR #352).
  • Issue #246: Frontend: Badges on Profile Page (closed by PR #355).
  • Issue #265: Implement Recording Interface — audio/video capture on story creation (closed by PR #267).

Non-Code-Related:

  • Issue #318: Testing — Define Mobile E2E / Appium Plan and Template (closed by PR #329).
  • Issue #277: Write Acceptance Test Scenario TC_BADGE_1 — First Post Badge Awarded.
  • Issue #269: Prepare Lab 9 Acceptance Test Cases.

Pull Requests:

  • PR #267: Recording interface (audio/video capture controls, recording helpers, unit tests).
  • PR #329: Mobile Appium E2E skeleton (WebdriverIO config, helpers, smoke/Lab 9 placeholders, README).
  • PR #341: Google OAuth frontend handoff (Google-branded buttons, OAuth callback page, JWT storage, unit tests).
  • PR #352: Story timeline frontend with clustered map markers and timeline page (radius + date filters).
  • PR #355: Badges and public profile UI (profile badges, post-publish unlock popup, badge rule type fix).
  • PR #366: First badge Playwright UAT (TC_BADGE_1); also fixed a duplicate Alembic revision blocking backend startup. Conflict resolution: rebased a local-only branch onto dev and brought the migration fix forward so the UAT could actually run in CI.
  • PR #381: Mobile badge Appium test (closed in favor of the consolidated date-format fix below).
  • PR #385: Fix UAT and mobile E2E date input format after #date-single switched to native type="date" (closes #383).
  • PR #391: dev → main release merge for the Final Milestone.

AI Transparency & Documentation:

  1. Tool summary:
    1. OpenAI Codex (CLI) — used as the primary coding assistant for the recording interface, badge UI, story timeline, OAuth handoff, and Playwright/Appium test scaffolding.
  2. Prompts: Alper Vural Prompt Log

Individual Testing Efforts:

  1. Recording helpers unit tests (frontend/recording.test.js, commit 0617f0b): Jest tests for the recording helper module that backs the camera/mic capture controls.
  2. Profile page unit tests (frontend/profile.test.js, PR #355): Jest tests covering badge rendering on the profile page.
  3. Google OAuth frontend unit tests (frontend/oauth-button.test.js, frontend/oauth-callback.test.js, PR #341): unit tests for the Google sign-in button wiring and for the OAuth callback page (token storage, redirect, error handling — see commit c205dbb and 7e9c6b3).
  4. Mobile E2E skeleton (frontend/tests/mobile-e2e/, PR #329): Appium + WebdriverIO smoke spec and Lab 9 placeholder specs, with helpers and a documented local APK/emulator/Appium setup.
  5. TC_BADGE_1 Playwright UAT (frontend/tests/uat/badge.spec.js, PR #366): end-to-end acceptance test for first-post badge awarding, profile display, and no-duplicate-award.
  6. TC_BADGE_1 Appium mobile E2E (frontend/tests/mobile-e2e/specs/tc-badge-1.spec.js, PR #381 / PR #385): mobile counterpart of the badge UAT.
  7. E2E date-format fix (commits cff2cb0, a77be54, PR #385): updated UAT and mobile E2E suites to use yyyy-mm-dd after the date field became a native date picker, unblocking TC_BADGE_1 and TC_STORY_5.

Additional Information:

  • Frontend final UI/UX pass (Issue #248): map cluster click behavior fix, Capacitor asset bundling, and miscellaneous polish across map/story pages.
  • Reported and tracked the microphone-stays-active bug (Issue #338) discovered while integrating the recording interface.
  • Code review: reviewed 17 post-MVP pull requests across the team — covering frontend feature PRs (likes, comments, edit profile, saved/near-me stories, audio review UI, multi-location story, anonymous sharing, tagging UI, reporting UI, UI/UX enhancements, mobile fixes) and backend / testing PRs (Playwright UAT skeleton, /stories/timeline endpoint, query optimization, TC_DASH_1). Reviewed PRs: #258, #263, #266, #268, #292, #319, #333, #336, #349, #354, #361, #370, #373, #374, #377, #395, #396.
  • Documentation & demo (post-MVP):
    • Acted as note-taker for Weekly Meeting 11 (2026-05-02), the meeting that defined the Final Milestone testing strategy (Selenium/Appium templates) and delegated the timeline feature design to the frontend team — delivered as PR #352.
    • Contributed to Section 2 — Acceptance Testing Strategy of Lab 9 Report (30-04-2026), alongside writing the TC_BADGE_1 acceptance test scenario.
    • Assigned as a presenter for the final demo per the Final Demo Plan.
Team Members

Milestones

Lab Reports

Weekly Meetings

Other Meetings

Templates
Scenarios
Use Case Diagrams
Class Diagram
Sequence Diagrams

Requirements

Implementation

Clone this wiki locally