Lab 5 Report - bounswe/bounswe2026group9 GitHub Wiki

Are the button, Dockerfile, and merge to feature/stub-app completed?

Member	Participated
Can Emir BORA	x
Mustafa KOYUNCU	x
Muhittin KÖYBAŞI	x
Faik İhsan SÜDÜPAK	x
İbrahim Fırat YOĞURTÇU	x
Battal HAZAR	x

We are completely done with our planning and diagrams. We are ready for implementation, and we have decided on our roles during the project.

Link to Team Policies

• Commit model:
  • Use the following commit message syntax: <type>: <short-description>
  • Allowed commit types are: feat, fix, docs, refactor, test, and chore
  • Keep commit messages short, clear, and descriptive
  • Use one commit for one logical change only
  • Do not use vague commit messages such as update, changes, or final version
• Branching model:
  • Create a branch from main for each task: feat/<short-description>, fix/<short-description>, docs/<short-description>, refactor/<short-description>, or test/<short-description>
  • Never push directly to main. All changes go through pull requests.
  • Use one branch for one issue or task only.
  • Keep <short-description> short, clear, lowercase, and hyphen-separated.
  • Do not mix unrelated changes in the same branch.
  • Keep branches up to date with main before opening or merging a pull request.
  • Delete branches after they are merged.
• Pull Requests:
  • Reference the issue: include closes #<issue_number> in the PR description.
  • Assign at least one reviewer who is not the PR author.
  • PRs require at least one approval before merging. No exceptions.
  • The reviewer (not the author) performs the merge after approval.
  • Delete the branch after a successful merge.
  • Use a clear and descriptive pull request title.
  • Keep each pull request focused on a single logical change.
  • Do not merge pull requests with unresolved conflicts.
  • Update related documentation if the change affects requirements, diagrams, setup instructions, or user-facing behavior.
  • Ensure the branch is up to date with main before merging.

We chose Option A as :

• Muhittin - web, devops
• İhsan - backend, devops, mobile
• İbrahim - web
• Mustafa - mobile
• Battal - mobile
• Can - backend, mobile, devops

Implementation Plan (MVP + Final Milestone): https://github.com/bounswe/bounswe2026group9/wiki/Implementation-Plan

• Created button 5 for stub-app and created the dockerfile: #78
• Discussed with the team on planning and roles.

• Created button 1 for stub-app and created the dockerfile: #72
• Discussed with the team on planning and roles.
• Added stub app completion, planning situation, and team structures-roles part to the lab report.

• Created button 4 for stub-app: #73
• Discussed with the team on planning and roles.

• Implemented Button 2 for the stub app by adding a new page that fetches and displays data from a public API: #70
• Updated config.js and handlers.js to integrate the new button into the app and connect it to its page.
• Revised the team policies section by contributing to the commit, branching, and pull request rules.
• Participated in team discussions on planning, task distribution, and report preparation.

• Created the stub-app branch and cloned the Base Repo's files into our repo. #68
• Create button 6 for stub-app: #69
• Discussed with the team on planning and roles.

• Implemented Button 3 for the stub app by adding a new page that fetches and displays data from a public API: #81
• Updated corresponding config.js and handlers.js to integrate the new button into the app and connect it to its page.
• Discussed with the team on planning and roles.