Meeting Notes 9 - bounswe/bounswe2025group8 GitHub Wiki

Meeting #9

Meeting Information

  • Date: 19/04/2025 20.00 - 21.00
  • Platform: Google Meet
  • Not Taker: Mustafa Batuhan BÜBER

Attendees

11/11 team members attended.

  • Abdullah Rüzgar
  • Ali Sönmez
  • Ahmet Eren Aslan
  • Alperen Garip
  • Batuhan Büber
  • Ebru Özçakı
  • Eray Yüklü
  • Erdem Koçak
  • Musa Kaan Güney
  • Üveys Aydemir
  • Yusuf Kaan Akçay

Discussion

  • Backend: majority leans toward Django over Java Spring, although its legacy status was noted as a risk.
  • Database: agreed to use PostgreSQL.
  • The backend team will take the lead on the initial implementation phase.
  • Feedback indicates an error in the current Use‑Case diagram; a fix will follow completion of all Sequence Diagrams.
  • Features with high-priorities:
    • Login / Register
    • Volunteer Task flow
    • Post Task flow
    • Profile Page
    • Unified request feed (for authenticated users)
    • Guest‑visible feed
  • A shared Docker setup is required so everyone can run the project in the same environment.
  • Slack channels for the three team were created.

Action Items

# Task Assignee(s) Due
1 Open every required GitHub issue related to this meeting Batuhan 20 Apr 2025
2 Create a GitHub milestone for the 25 Apr feedback round Ali 20 Apr 2025
3 Complete all Sequence Diagrams Everyone 20 Apr 2025
4 Review and close all open Sequence Diagram issues Ali 21 Apr 2025
5 Review and close Ali's Sequence Diagram issue Ebru 21 Apr 2025
6 Fix diagrams according to the feedback Eray, Ebru 21 Apr 2025
7 Collected and stored the scenarios and Sequence Diagrams Musa 21 Apr 2025
8 Each team to agree on its tech stack Everyone 23 Apr 2025
9 Complete the UI/UX Design Batuhan, Ahmet Eren 23 Apr 2025
10 Research and select a Docker image / compose setup for the project Eray, Abdullah 23 Apr 2025
11 Configure the GitHub Projects page Ebru Ongoing

Additional Notes

  • Three dedicated Slack channels (Backend, Frontend and Mobile) are already in place; please post inter‑team questions in the relevant channel to keep discussions organised.