-
Notifications
You must be signed in to change notification settings - Fork 2
Meeting #9
🗓️ Date: 15/04/2023
🕖 Time: 17.30 - 18.10
📍 Location: Zoom
📝 Note Takers: Egecan Serbester
- Aras Güngöre
- Begüm Arslan
- Cahid Enes Keleş
- Egecan Serbester
- Halil İbrahim Gürbüz
- Hasan Bingölbali
- Mehmet Emin İpekdal
- Mehmet Kuzulugil
- Merve Gürbüz
- Ömer Şahin Albayram
- Ramazan Burak Sarıtaş
- Reading the Milestone 2
- Open discussion for tools we will use
- Weekly RAM
-
After we read the milestone 2 documentation and clarify what the project owner wants from us some of us discussed which tools we will use and some of us have no idea about them. Thus we decided that:
- 1.1 API
- 1.1.1 Each group member should learn what API means and why we need them.
- 1.1.2 Each group member should also learn which API types will be better for us. Including their advantage and disadvantages.
- 1.2. Web Framework
- 1.2.1 Each group member should learn web frameworks do, and which one is more practical, easier to learn and implement.
- 1.2.2 Some of us may use to working with some web frameworks. They may want to develop practice apps with frameworks that they know. These people can search and offer which framework is better for what purposes.
- 1.3 Web Service
- 1.3.1 Each group member should learn what AWS (Amazon Web Services) is used for. Could it be a better option than AWS (i.e Azure?)
- 1.4 Git Actions
- 1.4.1 Each group member should learn some git actions that we will use in this project. (Merge Request, push, commit etc.)
- 1.1 API
-
We will open discussions about each topic to discuss it more structurally. We can use these discussions to share useful links.
-
Under the 9th criterion on Milestone 2 "All team project development practices discussed thus far must be used to specify, plan, and track the practice application." That means we will also develop UMLs for that. Everyone will be responsible for their part. Please consider that.
-
We decide to create a practice-app project to push everything that relates to Milestone 2 on it.
-
We decide to keep RAM (Responsibility Assignment Matrix) for each week. In this way not only its data will be more accurate but also it will promote us to contribute more to this project.
-
Each group member should also keep a weekly effort template to follow their weekly contributions more easily.
-
Some of us have developed or edited something on the project without opening an issue because of their goodwill. From now on, each team member should go on with issues to follow and show their contributions easily both for RAM and DPR on milestone reports.
-
We decided note takers of meetings should also open issues about decisions on these meetings. They can open issues when editing the meeting notes.
9. We decided to meet on Tuesday evening to talk about what we have learned and decide which tools we will use on Milestone 2 and who develops which API (they should be useful for our project you can pick them from use-cases or requirements).
Action | Issue | Assignee(s) | Deadline |
---|---|---|---|
LEARNING TOOLS WE WILL USE | @EVERYONE | 18/04 @ 17.00 | |
DECIDE WHICH FUNCTION YOU WILL DEVELOP WITH APIs | #1 | @EVERYONE | 18/04 @ 17.00 |
Open Discussion About Frameworks | #2 | Şahin | 18/04 @ 17.00 |
Open Discussion About Tools | #3 | Egecan | 18/04 @ 17.00 |
Open Project | #4 | Begüm | 18/04 @ 17.00 |
📌 Communication Plan
📌 Docker and local deployment tutorial
📌 RAM
📌 Test Traceability Matrix