BackEnd Meeting 2 - bounswe/bounswe2025group2 GitHub Wiki
Backend Meeting Notes
Date: 2025-04-19 Time: 21:30 - 22:00
Agenda
-
Distrubiting our work which is:
- Creating backend for settings
- Creating backend for profile
- Creating backend for goal mechanism
-
Some distinctions needs to be made such as:
- The difference between a coach and a mentor
- The difference between a challenge and a goal
-
The properties of badge system and some profile settings
Attendees
- Yusuf Akdoğan (Note taker)
- Alperen Akyol
- Berkay Buğra Gök
- Doran Pamukçu
Discussion Points
-
The work is distributed among team members and is clarified in action items.
-
The difference between coach and mentor is assumed to be following:
- A coach is only a verified user and its existence is not linked to another subject. Coaches can create challenges but they can not have mentees and can not set goals.
- A mentor can have a mentor-mentee relationship with a user. He can set goals for that user and track them. Mentors are not verified and can not create challenges.
-
The difference between challenge and goal is assumed to be following:
- A goal is self-set or set by a mentor. It has a receiver and can be tracked.
- A challenge does not have a receiver. They can be set by coaches and users can reach them via a catalogue-like system. After completion they might have receive a badge depending on challenge setter.
-
Profile customization and sending (or not sending) e-mails for notifications are decided as possible settings.
-
Some API examples are discussed and discussions will be added to the relevant discussion page.
-
Possible implementation details are discussed such as using AWS S3 for profile photo.
-
For badges it is decided that majority of work will be done by front-end. The number of datafields will be limited (like type or optionally a message clarifying from where the badge come from). However actual clarification will be done in the future since we have not decide on whether a coach can customize image for the prize badge for a challenge or not. For that three options are discussed:
- A coach can fully customize for the image for a badge. (we will need to provide means for that and we need to store the image in our database)
- We will have some number of custom images and coaches will choose one of them. (We will not need to store the images since predefined image can be handled in front-end. We will only need to store an id for the correct image)
- All badges will look same. (Easiest option no additional data fields)
However it is decided that the actual implementation will be decided alongside with challenges since back-end does not need to handle badges completely until then.