Meeting 14 of 352 - bounswe/bounswe2025group5 GitHub Wiki

Details

📅 Date: 28/04/2025
📍 Location: Zoom
🕐 Duration: 21.30 - 22.15 📝 Note Taker: Abdülkerim Kasar

👥 Attendees

Agenda

  1. Recap of Milestone #1
  2. Planning of Milestone #2.
  3. Discussions on Leaderboard Functionality.

Discussion Items

  • One member from each implementation team (Cengiz Bilal Sarı, Abdülkerim Kasar, Ahmet Çağdaş Girit) discussed what their teams succeeded in and what they were unable to complete by the Milestone 1 deadline.
  • They discussed what actions were taken after the deadline regarding these uncompleted items.
  • The same procedure was followed for the tasks to be done for Milestone 2.
  • The remaining implementations were carefully reviewed and the items that need to be completed for Milestone 2 were listed.

A draft of features to be implemented for Milestone 2 is as follows:

Backend:
- (Remaining from Milestone 1) Comment and like posts (Already done) - Save posts
- Endpoints for leaderboard and challenges
- Different endpoints for the Home page (most liked posts and total log information)
- Wikidata API semantic search implementation
- Deployment (if time permits) (Moderator and admin login status TBD)

Frontend:
- (Remaining from MS1) Waste goal and log implementations
- (Remaining from MS1) Profile page
- Comment/like posts
- Save posts
- Semantic search
- Leaderboard

Mobile:
- (Remaining from MS1) Waste goal and log implementations
- Comment/like posts
- Save posts
- Home page
- Semantic search
- Leaderboard

  • Possible logical issues related to adding leaderboard, waste goal, and waste log data to the system were discussed.
  • It was concluded that users would enter their wastes (itself, not reduced waste) in the waste log section and that for the leaderboard everyone would be given a base score, which would be reduced as waste is added.
  • To be sure, it was decided that the Communicator (Abdülkerim Kasar) would send an email to the client.
  • Moderator, challenge acceptance, leaderboard's type and location topics were set aside for later discussion.
  • It was reminded that since each team member needs to write an API function, the backend team should leave space for this.
  • It was decided to review the Requirements document after Milestone 2 is completed to ensure nothing is overlooked.

Action Items

# Details Assignee(s) Deadline
1 Finalize and add Milestone #2 report Abdülkerim Kasar 29.04.2025
2 Every team needs to divide tasks and create corresponding issues for the upcoming milestone Every team member 30.04.2025