Meeting #2 (10.03.2022)

Meeting #2

Details

📅 Date: 10/03/2022

📍 Location: Discord

🕐 Duration: 20:00 - 22:00

📝 Note Taker: Bahrican Yesil

👥 Attendees: (10/10)

• Ahmet Yiğit Özdoğan
• Altay Acar
• Bahrican Yeşil
• Ecenur Sezer
• Egemen Atik
• Ezgi Aysel Batı
• Hasan Can Erol
• Mehmet Batuhan Çelik
• Muhammed Enes Sürmeli
• Onur Kömürcü

Agenda

1. Passing over the project pdf, talking about it in general
2. Review of the previous week feedbacks about the issues/wiki pages
3. Specifying the main titles for the requirements
4. Determining the research topics for this week
5. Assigning the tasks and determining the assignees for the week

Discussion

1. We went over the project description pdf and extracted the base features of the app item by item from it. You can view them here.

2. We talked about some notions/technologies/methods that are mentioned in the project pdf. After that, we determined some research topics for this week:

• W3 Web Annotation Model Research
• Semantic Search
• Similar Products - Competitor Analysis (Initial phase)

In order to learn better, it was decided that everyone will contribute to the research tasks. People assigned to research tasks will gather the research together and document it on the wiki page.

3. Iterated over the assignment to create a task list, and assigned people on a volunteering basis.

4. For common tasks that affect others' work or requires a review of another person (such as the research, requirements), the deadline was decided to be 13.03.2022 - Sunday - 20:00

5. For the reviewers and documenters, the deadline was decided to be 14.03.2022 - Monday - 23:59

6. It was decided that we should create separate titles and subtitles for the requirements and then assign different people to determine these specified requirements. We have separated requirements as:

• Functional Requirements
  • User Requirements
  • System Requirements
• Non-Functional Requirements

7. To have an objective review process, we also decided to select the reviewer among the people who are not assigned to an issue. This both will help us to complete each other and track what's going around in the other issues.

8. We've decided to have some issue templates to both have unity among the team and speed up the issue creation process. We also shared our decision with Suzan Hoca on Slack. As a result, we will create some templates in the upcoming days and will inform our TA to create them on GitHub on our behalf of us.

9. We have put some rules about the issue management process, we will also implement these rules in the templates.

• Every issue should have a deadline written in the description of it.
• Every issue should have a detailed description.
• Progress, updates, etc. should be added to the issues as comments.
• Every issue should be labelled (its priority, status, and so on).
• Those issues which have a reviewer should contain the reviewer info and a deadline for him/her in the description.
• The person who will close an issue should put a final comment before closing it.
• All progress indicator labels (such as status-inprogress) should be removed (or be replaced with completed indicator labels) before closing an issue.
• Dependent issues should be linked by writing #{issue_number}. With the help of this notation, issues will have reference info under themselves to the other related ones.

Action Items

Action items are listed in the order they were discussed during the meeting.

#	Details	Assignee(s)	Due Date	Issue
1	Document the meeting notes on the wiki	Bahrican Yesil	14.03.2022 Monday @ 23:59	#15
2	Create an issue to collect the user requirements info and track its sub-issues	Bahrican Yesil	11.03.2022 Friday @ 15:00	#16
3	Create an issue to collect the system requirements info and track its sub-issues	Ezgi Batı	11.03.2022 Friday @ 15:00	#22
4	Create an issue to collect the non-functional requirements info and track its sub-issues	Onur Kömürcü	11.03.2022 Friday @ 15:00	#21
5	Review the user requirements	Ezgi Batı	14.03.2022 - Monday @ 23.59	#16
6	Review the system requirements	Bahrican Yesil	14.03.2022 - Monday @ 23.59	#22
7	Review the non-functional requirements	Ecenur Sezer	14.03.2022 - Monday @ 23.59	#21
8	Determine the user requirements	Ahmet Yiğit Özdoğan, Altay Acar, Bahrican Yesil, Batuhan Çelik	13.03.2022 Sunday @ 20:00	#16
9	Determine the system requirements	Ecenur Sezer, Ezgi Batı, Muhammed Enes Sürmeli	13.03.2022 Sunday @ 20:00	#22
10	Determine the non-functional requirements	Onur Kömürcü, Egemen Atik, Hasan Can Erol	13.03.2022 Sunday @ 20:00	#21
11	Research about W3 Web Annotation Model	Everybody	13.03.2022 Sunday @ 20:00	#20
12	Research about semantic search	Everybody	13.03.2022 Sunday @ 20:00	#26
13	Research about competitors/similar products	Everybody	13.03.2022 Sunday @ 20:00	#27
14	Collect and document the research of W3 Web Annotation Model on a wiki page	Altay Acar	14.03.2022 Monday @ 23:59	#20
15	Collect and document the research of semantic search on a wiki page	Ezgi Batı	14.03.2022 Monday @ 23:59	#26
16	Collect and document the competitor analyses on a wiki page	Muhammed Enes Sürmeli	14.03.2022 Monday @ 23:59	#27
17	Update the home wiki page and sidebar acc. to the feedbacks and new items (such as requirements)	Bahrican Yesil	13.03.2022 Sunday @ 20:00	#14, #18
18	Add glossary to the requirements page	Egemen Atik, Ahmet Yiğit Özdoğan	13.03.2022 Sunday @ 20:00	#24
19	Review the glossary page	Ecenur Sezer	14.03.2022 Monday @ 23:59	#24
20	Create an issue to check and track glossary page tasks	Egemen Atik	11.03.2022 Friday @ 15:00	#24