BACKEND Meeting Notes #2 20 10 2022 - bounswe/bounswe2022group7 GitHub Wiki

Meeting Information

Date: 20/10/2022
Time: 22:00
Online/Offline: Online
Location: Discord
Duration: 1 hour
Note Taker: Basak Onder

Attendees

  • Cahid Arda Öz
  • Demet Yayla
  • Ali Can Milani
  • Musa Şimşek
  • Erim Erkin Doğan
  • Güney İzol
  • Aziza Mankenova
  • Atilla Türkmen
  • Can Atakan Uğur
  • Başak Önder
  • Sabri Mete Akyüz
  • Muhammet Ekrem Gezgen

Agenda

  • Discussing the remaining tasks from the previous week.
  • Discussing authantication issue and how to deal with it.
  • Deciding the necessary class to implement this week.

Discussions

  • Agreed on what to do for previous tasks and close them.
  • Decided to research and use built-in functions provided by Spring Boot.
  • Decided to implement user classes.
  • Decided to implement endpoints to return events and art items.
  • Decided to create dev/backend branch to merge backend developing branches after review.

Action Items

Item Responsible Person Due Date
Docker initialization part is to be done Basak Onder 21/10/2022 23.59
Target file issue is to be closed with a necessary explanation Basak Onder 21/10/2022 23.59
Endpoint that returns all the events is to be implemented. Demet Yayla 25/10/2022 23.59
Endpoint that returns all the art items is to be implemented. Demet Yayla 25/10/2022 23.59
Research about authentication built-in function is to be done. Sabri Mete Akyüz 23/10/2022 23.59
Authentication part is to be implemented. Sabri Mete Akyüz 25/10/2022 23.59
Visitor class is to be written. Basak Onder 25/10/2022 23.59
Guest class is to be written. Basak Onder 25/10/2022 23.59
RegisteredUser is to be written Muhammet Ekrem Gezgen 25/10/2022 23.59
EventInfo class is to be written. Muhammet Ekrem Gezgen 25/10/2022 23.59
Comment class is to be written. Muhammet Ekrem Gezgen 25/10/2022 23.59
CommentReport is to be written Muhammet Ekrem Gezgen 25/10/2022 23.59

Conclusions

  • Corresponding classes and endpoints to implement are decided and divided between the team.
  • Github flow and branch names are decided