-
Notifications
You must be signed in to change notification settings - Fork 1
Meeting Minutes ‐ Backend
Attendees: Dan, Patrick, Ziad, Walid, Wadeh, Joud
Dan:
- Risk management table done in drive
Patrick:
- Work on DB model.
- Working on use cases to put in wiki.
Wadeh:
- Deployment diagram
Walid:
- Deployment diagram
- Setup server for deployment
- Start 1 service
Ziad:
- Architecture diagram
Talking points: Selected the time for backend scrum meeting: Tuesday 8:30 PM Decided to create tasks ON THE BOARD ONLY for diagrams Use naming convention: [Task] XXXX Diagram Add any sprint 1 work as well Sidenote for research [Spike] “research topic” Contains brief description of what the diagram talks about
Action Items: Joud update the frontend team on creating tasks on github for diagrams Joud update the frontend team Dan ask Khalil on Gantt chart
Attendees: Dan, Patrick, Ziad, Walid, Wadeh, Joud
Note: Scrum for iteration 3, as well as doing task poker for iterations 4 and 5. In addition, assigning user stories and discussing upcoming sprint matters among the backend team. We keep in mind the priorities, and dependencies between tasks and iterations. Going through iteration 4 user stories and assigning user points using task poker.
Dan:
- Risk assessment document has been completed but needs formatting before being placed in the wiki.
Patrick: -Good progress on the use case diagram, some things to be added/adjusted and will also be put in the wiki soon.
Wadeh:
- Made github hooks for consistent commits and link to the issue as well as work on the deployment diagram and frontend pipeline for Jest tests.
Walid:
- Worked on deployment diagram and set up CI pipeline for testing, PR was created and was merged. Set up deployment server. Domain name acquired - Sportahub.app
Ziad:
- Learning from the videos to develop microservices using Spring boot.
Action Items:
- If anything is added to the wiki page, link it to an issue and vice-versa
- Specify the description of the user profile getters with Khalil (walid)
- Separate the user profile getters into 2 endpoints (full and filtered)
- Everyone should finish up their wiki pages
To pass to Frontend: Planning poker system: Points are how many hours it would take you to do the task Not difficulty (that would be risk) Majority vote after discussion Nico, Walid wants to meet for endpoints
Attendees: Dan, Patrick, Ziad, Walid, Wadeh, Joud
Dan:
- Waiting on other tasks to be done to start.
- Requires libraries from frontend (Joud) to include in the wiki
Patrick:
- Update user profile research
- User case diagram finished and will update to wiki
- Started research for the “measurement” wiki page
Wadeh:
- Diversity Wiki Page
- First drafts drafts for the backend pipeline
- Commit hooks ready for the backend/frontend
Walid:
- User microservice
- 100% test coverage
- Gateway service developed locally
Ziad:
- Finished the naming convention wiki
- Worked on get user endpoints (with full unit tests + started integration tests)
Todo:
- Walid has to setup KeyCloak
- Wadeh has to test backend pipelines and hooks
- Backend team needs to decide on the directory structure for pipeline & hooks to work.
- 1.12 should it be broken down into more detailed stories?
- 1.16 break down the tasks into more detailed tasks
- 1.18 notification to the user of new badges and storage of past badges
First Scrum after Iteration 1
Should tasks have story points? No, to not encourage Tasks usage as an equivalent to a user story.
Wadeh vote on the tasks performed for the ci/cd implementation
Did planning poker for sprint 5: #103, #155, #152, #153, #102
Notes during Planning poker
1.18: keep track of who endorsed who to not allow duplicates/badge/user
2.2: High priority - High risk, create a service (copy paste). New model, new endpoint.
1.22: Frontend Member to create the email template (create an issue for it) - Keycloak will handle the email verification internally.\
Notes on Testing:
Focus on Unit testing, 80% branch coverage
Define a structure for integration test:\
- one test file for every endpoint
- file name must have integration test in the name getUserIntegrationTest.java
- Test containers for integration tests.
Attendees: Dan, Patrick, Walid, Wadeh, Ziad, Joud
Dan:
- Started creating the event-service microservice
- Writing more tests for login to reach 80% coverage Patrick:
- Sending the verification email is done
- Need to write tests for verification email
- Working on improving the coverage on editing profile Wadeh:
- Doing research related to kafka before implementation Walid:
- Set up the email verification
- Changed the default message for the email
- Have to Update the registration endpoint to send the email verification
- Will Work on a ticket to update the user model based on a frontend request Ziad:
- Created the badge model and retrieval and assigning to users
- Started working on unit tests and will start integration to reach 80%
- Still have to work on the integration tests from last sprint coverage
Todo:
- Finalize the integration tests from last sprint
- Make tests for the tasks of this sprint
- Wadeh and Dan can focus on the more heavy implementation of the microservices rather than tests.
- The rest of the backend team should aim to >80 to balance the total unit and integration coverage
- Update the pipeline to enforce the 80% coverage without affecting development (wadeh and walid)
Full stack:
- Code freeze on Friday night
- Full attendance (first meeting with Jean-Nicolas
- Did planning poker for sprint 6
- Todo:
- Dan can drop the authentication part of his event service implementation to be moved to 11.1
- Patrick and Jean-Nicolas (after finishing his first task (low risk low priority as per professor): Not move forward with 11.1 without updating the team on the reasons why a specific choice was picked to keep the team in check.
© 2024 Sporta Team. All rights reserved.