Frontend Meeting ‐ 11 10 2025
📅 Date: 2025-10-11 📍 Location: Remote on Google Meets ⏰ Time: 20:00 ⏳ Duration: 60 Minutes
| Member | Participated |
|---|---|
| Berk GÖKTAŞ | ✅ |
| Hasancan KELEŞ | ✅ |
| Arda SAYGAN | ✅ |
| Yusuf Anıl YAZICI | ✅ |
- Review of SRS and initial milestone readiness
- Revising meal planner requirements
- Backend and frontend viability assessment
- Backend expectations and object structure discussion
- Review of user and report object details
- Clarifying user visibility and access rules
- Review of moderator and admin roles in SRS
- Task assignments for next milestone
- Repository update plan
-
Backend Object Expectations: The team discussed the objects expected from the backend and how they should be structured:
-
User Object should include:
- Private food items
- Profile-related information (photo, status flags like isReported, isBanned, isWarned)
- Reported posts
- Role flags (isModerator, isUser, etc.)
- Certificate information (certi)
-
Report Object: Should include the report reason, the profile being reported, and the post related to the report.
-
ReportList Object: Will contain multiple Report objects.
-
-
Banning Behavior: The team needs to specify what happens when a user is banned — whether the ban will restrict specific actions or completely block access. This will be clearly defined in the next SRS update.
-
Profile Visibility Rules: Users will be able to view other users’ profiles, but certain information will remain private.
- Not visible: liked posts
- Visible: shared recipes These visibility rules will be added to the SRS for clarification.
-
Certificate Deletion: User should also be able to remove the certificates they once uploaded. This feature is missing in SRS right now and it shall be updated accordingly.
-
Moderator and Administrator Roles:
- The Content Moderator role will be merged with the Community Moderator, as their purposes overlap.
- General and System Administrators may remain in the SRS for reference, but will not be implemented in early milestones.
- Moderators will also function as regular users, but their profiles will display additional moderation-related information.
-
Repository Management: The team agreed to copy the archived codes into the main repository to ensure consistency and access for future development.
| Action | Assignee | Linked Issues | Deadline |
|---|---|---|---|
| Define banning behavior (restrict vs full ban) | Team | — | 2025-10-14 |
| Specify visible user profile details in SRS | Team | — | 2025-10-14 |
| Merge Content and Community Moderator roles in SRS | Hasancan | — | 2025-10-15 |
| Decide on handling of General/System Administrator roles | Yusuf, Nuri | - | 2025-10-15 |
| Copy archived codes to main repository | Anıl | #440 | 2025-10-12 |
| Implement assigned features: | |||
| → Meal Planner | Arda | check Impl. 1.5 issues |
<-- |
| → Profile Management | Anıl | check Impl. 1.2 issues |
<-- |
| → Forum | Berk | check Impl 1.4 issues |
<-- |
| → Moderation | Hasancan | check Impl. 1.8 issues |
<-- |
