Weekly Meeting 7 - bounswe/bounswe2026group4 GitHub Wiki

Weekly Meeting — Week 7

Details

📅 Date: 25 / 03 / 2026

📍 Location: Google Meets

🕒 Duration: 20.00 - 20.30

📝 Note Taker: Oğuz Semih Arık

👥 Attendees

  • OĞUZ SEMİH ARIK
  • ÖMER FARUK ÇELİK
  • SEZİN DOĞAN
  • MERT EREN KAPLAN
  • AYSU KESKİN
  • KEMAL MAHMUTOĞULLARI
  • OSMAN YUSUF TOSUN
  • AHMET ÇAĞDAŞ GİRİTLİ

Agenda

  1. Discuss whether Enginex should be used
  2. Discuss database hosting options (Google Cloud)
  3. Review team role changes
  4. Decide on mobile development technology
  5. Plan team structure and internal team meetings
  6. Define issue and pull request workflow rules

Discussion Items

  • Discussed whether Enginex should be used in the project. No final decision was made and it may be revisited later if needed.

  • Discussed the current database setup and the need for a hosted solution to keep the database running continuously. It was noted that a cloud service may be required for persistence and availability.

  • Evaluated Google Cloud as a potential option for database hosting. The team discussed its free trial offering (approximately 90 days) and considered using it temporarily for the project. No final decision has been made yet.

  • It was noted that Oğuz Semih Arık will temporarily switch from backend to mobile development to support the mobile side of the project.

  • The team agreed to use React Native for mobile application development.

  • Decided that frontend, backend, and mobile teams will each hold separate internal meetings to determine their own task distribution and workflows.

  • Established that all newly created issues must include start date and end date information to improve task tracking and planning.

  • Agreed that pull requests must not be merged without receiving at least one review, enforcing a stricter code review process.

Action Items

# Details Assignee(s) Deadline
1 Evaluate and finalize decision on Enginex usage Team TBA
2 Further assess Google Cloud for database hosting and free trial usage Team TBA
3 Organize separate meetings for frontend, backend, and mobile teams to define internal task distribution Team TBA
4 Ensure all new issues include start and end dates All Team Members Ongoing
5 Enforce PR review requirement before merging All Team Members Ongoing