Weekly Meeting 8 (15.04.2026) - bounswe/bounswe2026group11 GitHub Wiki
📝 Weekly Meeting
- 📅 Date: 15-04-2026
- ⏰ Time: 19:00- 19:50
👥 Participants
| Member | Participated |
|---|---|
| Mehmet Kaan Ünsel | ✅ |
| Mehmet Akif Yıldırım | ✅ |
| Oğuz Özer | ✅ |
| Utku Yiğit Demir | ❌ |
| Cansu Er | ✅ |
| Buğra Keser | ✅ |
| Emine Türk | ✅ |
| Sevde Pekköse | ✅ |
🎯 Agenda
- Final milestone feature planning
- MVP/demo feedback evaluation
- Issue distribution and roadmap update
💬 Discussion Summary
-
The team discussed the remaining work for the final milestone and reviewed the major features that should be prioritized.
-
An optional meeting point text field may be added to events for practical instructions such as where to gather.
-
For join requests, an additional idea was discussed: allowing users to attach an image or PDF as evidence for a constraint.
-
The team also discussed adding a discussion section under events:
- pre-event Q&A
- post-event comments
- possible integration with the existing review/rating structure and event photo sharing
-
Another discussed improvement was allowing users to view other users’ profile details, potentially making profiles richer with information such as equipment, images, and similar personal content.
-
For discovery results, events that do not match the user’s gender and age restrictions should be filtered out.
-
Advanced filtering should be improved further, including more detailed filtering use cases.
-
On the create event page, the privacy levels should include short explanatory text.
-
Profile improvements such as change password functionality were also included in the discussion.
-
A possible badge / achievements system was mentioned as an additional enhancement.
-
It was noted that events should be able to remain in draft state, so that users can continue later.
-
The team also discussed allowing users to search with multiple categories.
-
For protected events, the displayed location should be approximate rather than exact.
-
The meaning of clear history was revisited, with the idea leaning more toward hiding history rather than permanent removal.
-
A frontend-specific issue was noted: when returning from the event detail page, the selected location does not persist.
-
The team used this discussion to better understand what must be prioritized before the final milestone and how remaining tasks should be split into issues.
🚀 Action Steps
- All team: Open and document the agreed issues.