Skip to content

Report 5

aliakkaya1 edited this page Mar 15, 2026 · 10 revisions

Lab 5 Report

Stub App Completion

Each team member successfully completed their individual parts of the stub application. Every member created their own branch from feature/stub-app, implemented a button that redirects to a new page displaying a public API response, and merged their personal branch back into feature/stub-app. A Dockerfile was already included in the stub application base.

Planning Situation

We have begun planning our term project by defining Git conventions, choosing a team structure, and assigning roles. The MVP and Final Milestone plans are still in progress and will be finalized soon.

Conventions

Commit Messages

We follow Conventional Commits, inspired by the AngularJS Commit Guidelines.

Format: <type>(<scope>): <subject> (max 100 chars per line)

Types: feat, fix, docs, style, refactor, perf, test, chore

Rules:

  • Imperative, present tense ("add" not "added")
  • No capital first letter, no period at the end
  • Optional body for motivation/context, optional footer for issue references (Closes #12) or BREAKING CHANGE:

Branch Naming

We follow Conventional Branching. Format: <type>/<description> — lowercase, hyphens only, no special characters.

Prefixes: feature/, bugfix/, hotfix/, release/, chore/

Example: feature/add-login-page, bugfix/fix-header-bug

Pull Requests & Merge Policy

  • Minimum 1 reviewer approval required
  • No self-merge
  • PR description mandatory (what changed & why)
  • PR author resolves conflicts
  • Squash merge to keep history clean
  • Branch must be up to date with target before merging

Team Structure and Roles

We chose Option A: Specialized Sub-Teams.

Sub-Team Members
Backend Ali, Ulaş
Frontend Ekin, Bora
Mobile & DevOps Ömer, Baran, Arif

As per Option A, members assigned to DevOps are also part of either the Frontend or Backend sub-teams, ensuring cross-functional knowledge for infrastructure tasks.

Implementation Plan

Individual Contributions

Bora Aydemir

  • Created my personal branch (feature/stub-app-BoraAydemir-button) and updated config.js and handlers.js to add a personalized button to the homepage.
  • Designed a new UI page (boraaydemir.html) formatted as a football player card and integrated TheSportsDB API to dynamically fetch and display live athletic data.
  • Opened a Pull Request to merge my individual implementation into the team's shared branch. #72
  • Contributed to determining the team conventions (commit naming, branching, and merge policies). #64

Ekin Kılıç:

  • Created personal branch feature/stub-app-ekin-button from feature/stub-app
  • Implemented Button 3 ("Ekin's API") that redirects to a page calling the Random User API and displays user data (name, email, location, phone)
  • Created ekin.html with API integration and styled output
  • Modified handlers.js and config.js accordingly
  • Pushed changes and opened a pull request to merge into feature/stub-app
  • Wrote the Lab 5 report

Ömer Belemir Delier:

  • Created personal branch feature/stub-app-omerbelemir-button from feature/stub-app
  • Implemented a button that navigates to a new page displaying real-time data from a public API
  • Developed a simple Dockerfile to containerize the application and ensure consistent build and runtime environment
  • Created the results page with API integration and added a brief explanation of the returned API values for users
  • Followed team commit conventions (e.g., feat: / fix:) during development
  • Merged the personal branch back into feature/stub-app after verifying it met the team’s merge policies
  • Pulled and synchronized the feature/stub-app branch to ensure development started from the correct team baseline

Ulaş Sertan Kemeç

  • Created personal branch 'feature/stub-app-UlasSertan-button' from 'feature/stub-app'
  • Implemented Button 5
  • Modified handlers.js and config.js accordingly
  • Pushed changes and opened a pull request to merge into feature/stub-app

Arif Evren

  • Added a new page (arif-evren.html) linked to the "Arif Evren" button (Button 7) on the stub app.
  • The page fetches live data from the Open-Meteo API (free, no API key required),
    displaying current weather conditions in Istanbul, Turkey.
  • Implemented the onButton7Click handler in handlers.js to navigate to the new page.
  • Committed and pushed the changes to the remote branch feature/stub-app-ArifEvren-button.

Baran Önder

  • Created sub-issues for Lab 5 Report
  • Created separate issue for Implementation Plan (MVP + Final Milestone)
  • Added Pull Request template (.github/PULL_REQUEST_TEMPLATE.md) to standardize PR descriptions across the repository
  • Implemented "Baran - Joke" button in config.js and handlers.js
  • Created baran.html — fetches and displays a random programming joke from JokeAPI
  • Added Dockerfile using nginx:alpine to serve the static app
  • Opened PR from feature/stub-app-Baran-button into feature/stub-app with proper description following team conventions

Ali Akkaya

  • Created personal branch feature/stub-app-AliAkkaya-button from feature/stub-app
  • Implemented a button in config.js and handlers.js that redirects to a new page fetching data from a public API
  • Created ali-akkaya.html with API integration and styled the displayed response for readability
  • Pushed changes and opened a pull request to merge into feature/stub-app
  • Contributed to team discussions on Git conventions and branch naming policies

Project

Team Members

Lab Reports

Weekly Meetings

Scenarios and Mock ups

Use Case Diagrams

Class Diagram

Sequence Diagrams

Milestone Review

Clone this wiki locally