-
Notifications
You must be signed in to change notification settings - Fork 2
Backend Team Meeting (Offline) #4
🗓️ Date: 13/11/2023
🕖 Time: Offline
📍 Location: Offline
📝 Note Taker: All
Regarding our physical conditions and current workload of the members, we decided to have an offline meeting. For the first tour of the meeting members informed the group about their weekly efforts and their perspective on the coming week. On the second tour questions and notes were exchanged (Latter, in a rather informal way. Using our communication tools).
- Begüm Arslan
- Mehmet Kuzulugil
- Aziza Mankenova
- Ramazan Burak Sarıtaş
- Buse Tolunay
- Members should inform the team about their efforts for the past week.
- Members should inform the team about their continuing work.
Weekly Update:
Accomplishments:
Worked on the design of user role implementation. Created a pull request with two new endpoints. Worked on the resource desgign for food and clothes.
Ongoing Work:
Awaiting implementation of image and PDF uploading for user role features. Planning to discuss design choices with the mobile and frontend teams. Continuing work on designing activities.
Challenges:
Waiting for the completion of image and PDF uploading implementation. Seeking feedback on design choices from the team.
Weekly Update:
This week, my focus was primarily on preparing for our upcoming team discussion about final design and implementation of resource & need, and also future implementations of Action and Events. Here's a breakdown of my activities:
- Thorough review of the current implementation and design/requirement documents of Resource and Need.
- Review of requirements and diagrams of Action and Event.
Challenges:
- Although we aimed to schedule a team discussion for a deeper dive into these elements, finding a suitable time proved challenging due to conflicting schedules because of the midterm week.
- Ensuring a comprehensive understanding of the diagrams and requirements for the planned implementations, since some parts are a little bit ambigous in terms of how it will be designed in the backend.
After a first check to the backend coding of my part for the week I decided to review the related requirements and diagrams of Events issue. Decided to discuss some details with the group (BE, FE and MO subgroups).
This week’s planned and non-planned activities for me were:
- Review the design, mainly for Events.
- Prepare some notes for discussion
- Review the Test and documentation elements of the recent work of Milestone 1.
- Research for storing profile pictures (and possible image storage): Merve had some elements (codes etc) on this issue. So we will decide how to complete the job. (Whether Merve will take on herself)
At first I have decided to review the related requirements and diagrams of Feedback System. I have decided to discuss some implementation details with the group (BE, FE and MO subgroups).
This week’s planned and non-planned activities for me were:
- Review the design, mainly for Feedback System.
- Prepare some notes for discussion of design with frontend and backend
- Review the Test and documentation elements of the recent work of Milestone 1. -Review of requirements and diagrams of Action and Event
After a first check to the backend coding of my part for the week I decided to review the related requirements and flow of the register and verification.
Also we decided to discuss some details about events and action flow with the group (BE, FE and MO subgroups).
This week’s planned and non-planned activities for me were:
- Review the authentication and register flow.
- Learn and study about email verification with fastapi -Awaiting implementation if email verification
Challenges:
- Since I didn't have any prior experience with email verification libraries it took me more time to understand and clearify the subtasks.
📌 Communication Plan
📌 Docker and local deployment tutorial
📌 RAM
📌 Test Traceability Matrix