Lab 8 Report

Lab 8 Report

Use of Standards

Here is the link for Use of Standards page.

Project Retrospective

Here is the link for Project Retrospective page.

Individual Contributions

• Ali Akkaya: -Coordinated Lab 8 deliverables and ensured alignment across team members -Contributed to refining the revised project plan based on MVP feedback and feasibility -Supported issue creation by defining clear and consistent technical requirements -Helped prioritize features and clarify scope for the final milestone -Reviewed repository structure and maintained consistency between development and roadmap
• Ulaş Sertan Kemeç:
  • Actively participated in post-demo discussions with the teaching assistants and synthesized insights from our recent customer meeting. Contributed to evaluating MVP demo feedback to determine which features and requirements to prioritize for the final milestone.
  • Collaborated on shaping the "Revised Plan" toward the final milestone. Contributed to breaking down high-level feature areas into small, independently pickable issues to enable parallel work across the team.
  • Opened the following issues for the next milestone: Issue #171 Moderation queue API [BACKEND], Issue #174 Push notification system [BACKEND], Issue #179 Auto-decay: transition stale reports to PASSIVE [BACKEND], Issue #168a Community resolution confirmation endpoint [BACKEND], Issue #165 Report lifecycle automation [BACKEND].

Ekin Kılıç:

• Opened the following issues for the next milestone: Account suspend / ban endpoints [BACKEND], Admin moderation UI [FRONTEND], Push notification system [BACKEND], Password reset flow [BACKEND], E2E smoke test suite [QA].
• Created the Project Retrospective wiki page and wrote its content.
• Actively participated in post-demo discussions with the teaching assistants and synthesized insights from our recent customer meeting. Played a key role in evaluating the feedback for the MVP demo to determine which features and requirements to include or exclude moving forward.

Bora Aydemir:

• Actively participated in post-demo discussions with the teaching assistants and synthesized insights from our recent customer meeting. Played a key role in evaluating the feedback for the MVP demo to determine which features and requirements to include or exclude moving forward.
• Collaborated on shaping the "Revised Plan" toward the final milestone. Translated high-level strategic decisions and customer expectations into actionable tasks by directly opening Issue #170, Issue #180, Issue #182, Issue #185, and Issue #186 to guide the team's upcoming sprint.
• Conducted peer reviews of the team's generated content for this lab, ensuring that the "Project Retrospective" and "Use of Standards" deliverables accurately reflected our team's actual progress, architectural decisions, and future roadmap.

• Baran Önder: 
  • Participated in the project retrospective and Final Milestone planning discussions.
  • Created GitHub issues for the Lab 8 report deliverables.
  • Opened new task issues for the remaining work toward the Final Milestone.
  • Updated the project roadmap to reflect the newly created issues and revised plan.
• Arif Evren:

• Opened issue #177 to define the backend endpoint for authority users to resolve obstacle reports (PATCH /api/authority/reports/{id}/resolve). The issue specifies that only users with the INFRASTRUCTURE_AUTHORITY role can call this endpoint, and a successful request must include a post-repair photo URL, transition the report status to RESOLVED_AWAITING_VALIDATION, and record the transition in the status history with optional repair notes. A 403 must be returned for non-authority roles and a 400 if the repair photo is missing.

• Opened issue #181 to define the Authority Dashboard UI for the frontend. The screen is route-protected and redirects non-authority users. It includes a filterable report list (by status: Open / Awaiting / Resolved), a detail panel showing the report's photo and history, and a "Mark as Resolved" form with repair photo upload and notes. On successful submission the list updates without a full reload.

• Opened issue #183 to define automated report lifecycle decay on the backend. Reports with UNVERIFIED status and no interactions after a configurable number of days (set via environment variables) are transitioned to PASSIVE by a management command or Celery beat task. Each transition must be recorded in the status history with the reason "Auto-decayed", and PASSIVE reports must be excluded from route calculations.

• Opened issue #184 to define the Upvote/Flag UI on the obstacle detail screen. Upvote and flag buttons display current counts and reflect the user's already-voted state. Tapping upvote calls the API and updates the count optimistically. Buttons are disabled with a tooltip on the user's own reports. Guest users can see counts but cannot interact — tapping shows a "log in to vote" prompt.

• Wrote the Use of Standards wiki page (Lab 8 Part I), documenting the project's use of GeoJSON (RFC 7946) for geographic coordinate representation, Schema.org for semantic domain modeling, W3C WCAG 2.1 as the guiding accessibility standard for routing and UI decisions, JWT (RFC 7519) for stateless authentication, and ISO 8601 for date/time serialization across the API. Also participated in the Part III discussion on how these standards apply to our accessibility-focused routing and reporting system.