Meeting 8 of 451 - bounswe/bounswe2025group5 GitHub Wiki
Details
📅 Date: 16.10.2025
📍 Location: Zoom
🕐 Duration: 20.00 - 21.00
📝 Note Taker: Serdar Bahar
👥 Attendees
- Serdar Bahar
- Cengiz Bilal Sarı
- Yusuf Onur Öksüz
- Osman Yusuf Tosun
- Yüksel Eren Şen
- Abdülkerim Kasar
- Arda Yalçındağ
- Ali Bartu Konca
- Emre Kılıç
- Abdurrahman Arslan
Agenda
- UML diagram deliverables and issue closure
- Waste goal and waste log implementation updates
- Challenge module and endpoint review
- Deployment and domain configuration planning
- Mobile–Frontend synchronization
- Database population
Discussion Items
-
UML Diagram Deliverables:
- The delete account sequence diagram will be added. (Assignee: Yusuf)
- All UML diagrams will be finalized and related GitHub issue will be closed. (Assignees: Yusuf, Osman, Eren)
-
Waste Goal & Waste Log:
- Backend implementation for waste goal and waste log is completed.
- Frontend and mobile teams should begin implementation.
- Cengiz explained the current backend structure:
- Waste goal is now independent from challenge module.
- Waste goals will be created only with waste type and duration.
- Need clarification on whether the max goal (100%) will be enforced. (Assignee: Cengiz)
-
Challenge Module:
- Some of the Challenge statuses defined as:
"ended"
→ when time expires."completed"
→ when the goal is reached. (Assignee: Cengiz)
- A unit field will be added. (Assignee: Cengiz)
- Discussed backend challenge endpoints:
createChallenge
attendChallenge
leaveChallenge
getAllChallenges
getAllUserChallenges
getLeaderboard
(with name–log quantity pairs).
- Some of the Challenge statuses defined as:
-
Deployment & Domain Setup: (Assignees: Eren, Cengiz Bilal)
- Planned frontend–backend deployment on Saturday evening.
- HTTPS setup is required, and an additional domain should be obtained.
- Possible tools: ngrok or nginx.
- Logs will be stored as files on DigitalOcean.
-
Mobile–Frontend Sync Meeting: (Assignees: Mobile and Frontend Team)
- Scheduled for 17 Oct, Friday 22:00.
- Purpose: ensure consistent UI flow and API usage between both platforms.
-
Database Population:
- The team will prepare and populate initial database data for testing and demos.
Action Items
# | ## | Details | Assignee(s) | Deadline |
---|---|---|---|---|
1 | 1 | Add delete account sequence diagram | Yusuf | ASAP |
2 | Finalize all UML diagrams and close related GitHub issue | Yusuf, Osman, Eren | ASAP | |
2 | 1 | Begin frontend and mobile implementation for waste goal and waste log | Frontend & Mobile Teams | ASAP |
2 | Clarify if max goal (100%) enforcement will be applied | Cengiz Bilal | ||
3 | 1 | Define challenge status logic (“ended”, “completed”) | Cengiz Bilal | |
2 | Add unit field to challenge model | Cengiz Bilal | ||
3 | Implement challenge endpoints (create , attend , leave , getAll , getUser , getLeaderboard ) |
Backend Team | ||
4 | 1 | Set up frontend–backend deployment | Eren, Cengiz Bilal | |
2 | Obtain domain and finalize HTTPS configuration | Eren, Cengiz Bilal | ||
3 | Configure log storage on DigitalOcean | Backend Team | ||
5 | 1 | Conduct mobile–frontend synchronization meeting | Frontend & Mobile Teams | @17.10.2025 (22:00) |
6 | 1 | Populate initial database data for demo and testing | Backend Team |