CMPE451 Meeting Notes #4 - bounswe/bounswe2022group7 GitHub Wiki
Meeting Information
Date: 29/10/2022
Time: 19:00
Online/Offline: Online
Location: Discord
Duration: 1 hour 40 minutes
Note Taker: Cahid Arda Öz
Attendees
- Cahid Arda Öz
- Demet Yayla
- Ali Can Milani
- Musa Şimşek
- Enes Aydoğduoğlu
- Erim Erkin Doğan
- Güney İzol
- Atilla Türkmen
- Can Atakan Uğur
- Başak Önder
- Sabri Mete Akyüz
- Muhammet Ekrem Gezgen
Agenda
- Update from teams
- Usage of branches
- Documents we need to prepare for the milestone
- Presentation
- Name of the App
Discussions
Updates From Teams
| Team | Status |
|---|---|
| Mobile | They are ready to connect to the API endpoints. They are waiting for backend to merge changes. Their implementation is therefore not tested. |
| Backend | Not much is left before merging the changes to the develop branch. There is an issue with SQL in docker. It works in local but CI fails. Endpoints are mostly done. |
| Frontend | Done research on annotations. Other than that not much development. |
Endpoints
- Documentation: We are currently saving endpoints on a page on wiki. This is not the best option. We can add swagger documentation after the milestone to improve documentation. Using a Postman repository is an option but it requires payment.
- We talked about which fields of the endpoint resposes will be used in the mobile and frontend. We decided that we will show every information available.
Frontend
- We need to add sign-up verification and some fields to match the mobile implementation.
- We can add testing with robot framework to run the scenario we will present in the presentation. This is a low priority task.
Documents for Milestone
- We saw that the format of the documents will be Markdown.
- We will collect the files in a folder in the deliverables folder.
- Project plan needs to be updated to match our progress. The team members should also be updated. Erkin will be assigned to DevOps until the milestone, then to backend team after the milestone. The project plan is a low priority task and we will handle it if we have time on monday.
- We will handle the group review report together on thursday.
- Everyone will fix their own sequence diagrams.
Branches
We will no longer have three branches for all three teams. There will be a develop branch and feature branches. This change was requested because there are too many steps in the original plan. We will continue naming the feature branches like before.
Name of the App
App will be named ideart
Action Items
| Item | Responsible Person | Due Date | Relevant Issue |
|---|---|---|---|
| Prepare Deliverable Documents to the repository. Create a branch and add files there. Then create a PR into the develop branch. Atakan will add use case and class diagrams. Arda will add the rest. | Can Atakan Uğur and Cahid Arda Öz | 31.10.2022, 23:59 | - |
| Handle Sequence Diagrams | Everyone | 31.10.2022, 23:59 | - |
| Merge team branches into develop branch | Everyone | 29.10.2022, 23:59 | - |
| Integrate backend endpoints to the app | Frontend and Mobile Team | 31.10.2022, 23:59 | - |