Meeting Notes #21 08.11.2022

Date: 08.11.2022
Location: Classroom B2
Time: 15:00 - 17:00
Note Taker: Salim Kemal Tirit & Kadir Ersoy

Participants:

• Burak Yılmaz
• Mehmet Gökberk Arslan
• Bilal Aytekin
• Nurlan Dadashov
• Hatice Şule Erkul
• Kadir Ersoy
• Salim Kemal Tirit
• Mertcan Özkan
• Furkan Akkurt

Agenda:

• Critique about Milestone 1
• Discussing what is going to be implemented for Milestone 2
• What are the things that we need from other teams?

Discussion Notes

• We started with a critique of Milestone 1:

  • We needed to have a backup plan.
  • We had a nice presentation overall.

• Open issues related to previous work or the ones that have passed the deadline should be completed and closed as soon as possible.

• After the lesson, we decided to create a meeting notes page and the issue for the meeting notes before the meeting.

• We need to state the agenda

  • List topics necessary to discuss under the issue, before the meeting
  • Simple sentences, can have links to related other issues
  • Go over it at the meeting and assign people

• We discussed what we need to do until Milestone 2:

  • There are problems with the enrollment and enrolled courses in the backend that need to be fixed.
    • Enrollment must be unique (user, course pair)
    • Must have a regex option for searching.
  • Uniqueness should be implemented in all backend models.
  • We should open a new issue like #270 to collect all endpoints that are necessary for the second milestone.
  • We need endpoints to create, update, and edit for topics, comments, or content.
  • Create comment endpoint needs discussion id.
  • There should be discussions under the resources
  • Contents need to have a title and resources inside. It can have more than one resource.
  • We need to get a text-based resource system ready for this week. Images, PDFs, and Videos will be texts as well, providing their links.
  • We discussed the annotation feature:
    • We need to read the w3c annotation standard carefully again.
    • We talked about the implementation of the annotation feature.
    • There may be some special characters before and after the annotated part.
    • There may be some indication after the special character to connect it to the annotations in the database.
    • We talked about what will happen if the user changes the annotated part. This might result in two ways: it can get deleted or it can stay we decided to think about this and decide when we need it.
  • The backend team should write unit tests.
  • There should be a rating system for the resources and/or topics.
  • There should be a mechanism that will calculate the knowledge of the user. This will be specified in the future.
  • We need to open weekly efforts pages for the previous and this week.
  • We need to make research on the geolocation feature and we need to share our findings with each other in the weekly meeting on Sunday.
  • Mobile team should work on the markdown feature that is implemented on the website.
  • Mobile team should decide and find a way to implement the note-taking feature.
  • Add a checkbox for KVKK for both the frontend application and the mobile application and the backend needs to check if it is filled.
  • There needs to be a script to populate the database.
  • A development environment should be created.
  • The static pages in the frontend application and the mobile application should be connected to the backend. And their endpoints should be ready and working.
    • Profile page, interests, tags
    • Topics
    • Resources
  • There should be an endpoint to search with tags.
  • The homepage should have an endpoint to get the related courses.

• With our TA:

  • What happens if someone puts unrelated content?
    • Should be decided clearly. Do the users just downvote or is there an option to report to the admins?
  • There should be sorting mechanisms everywhere.
  • Like or dislike feature for content (upvote downvote)
  • What does the user sees if there are many contents? Which one do we show first?
  • The learning space should be improved by anyone. There is no need to be advanced in anything.
  • There should be a list of people who contribute to the learning space.
  • The resources should have a discussion section. This will be also used as feedback in words.
  • We can restrict some things like annotation can be only for the texts.
  • We need to make our next meeting with the deployed application open.

Action Items

Action	Assignee	Deadline	Issue
Open issues related to previous work should be closed.	Everyone
Creating meeting notes page and agenda for the next meeting		13.11.2022@20:00
Collecting necessary endpoints for the next milestone
Read w3c annotation standard and creating a		13.11.2022@20:00
Writing unit tests	Backend Team
Implementing a rating system for the resources and/or topics
Creating weekly efforts for this week and the previous week	Salim Kemal Tirit	09.11.2022@23:59	#348, #350
Doing research on the Geolocation feature		13.11.2022@20:00
Implementing markdown feature for mobile application	Mobile Team
Planning of implementing note-taking feature	Mobile Team
Adding KVKK for the UI	Front End Team, Mobile Team
Implementing KVKK checking	Backend Team
Implementing a script to populate the database	Backend Team
Creating a development environment	Backend Team
Connecting static pages to backend	Frontend Team, Mobile Team