-
Notifications
You must be signed in to change notification settings - Fork 3
Mobile Meeting 5
Halil Burak Pala edited this page Dec 3, 2022
·
2 revisions
Date | 01/12/2022 21:00 - 22:00 |
Platform | Discord |
Note Taker | Halil Burak Pala |
- Baver Bengin Beştaş
- Engin Oğuzhan Şenol
- Halil Burak Pala
- Kardelen Demiral
- Fifth meeting of the Mobile Team in which we discuss tasks to be done before Milestone 2.
- Reviewing Meeting 21.1
- Determining the tasks that are needed before the Milestone 2
- Work distribution
- Some bugs in the post reading page have been pointed out: Overflows in smaller screens
- Some necessary design changes in the post reading page have been determined:
- Report button should be removed from post and comment widgets.
- A button for reaching deleting and editing features of the post/comment/article is needed.
- Constructor of these pages need active user info.
- Whether the session is active should be checked to allow a user to comment and up/downvote.
- Drawer should be updated to show username of a user or full name of a doctor. Notifications and settings buttons should be removed.
- Necessary form fields should be added to the edit profile page.
- We need a page for comment creation.
- View post, view article, create post, create article pages should be connected to the home page.
- We determined some important API functions that we will need:
- We need to get all posts and all articles when a user enters the home page. There should be an API function for this purpose. Pagination should be handled also.
- There should be an API function to get a single post, its comments in the post reading page. Also there should be an API function to get a single article.
- Functions for post and article creation have already been handled by Kardelen.
- There should be an API functions for post/article upvote/downvote.
- There should be an API function to get all upvotes of a user which can be reached through profile page.
- There should be an API function to get all posts of a user which can be reached through profile page.
- There should be an API function to get all comments of a user which can be reached through profile page (If such a function will be implemented by backend team).
- There should be an API function to update a user's info which will be used in edit profile page.
- There should be API functions for deleting a post/comment/article.
- IMPORTANT: Frontend issues about the above functions should also be handled (e.g. deleting a comment from the mobile page immediately after it is deleted via related API function).
# | Task | Assignee | Task Deadline | Reviewer | Review Deadline |
---|---|---|---|---|---|
1 | Overflow bug in the post reading page should be fixed. | Bengin | 04.12.2022 21:00 | Oğuzhan | 05.12.2022 12:00 |
2 | Report button should be removed from the post reading page. Dropdowns for deleting and editing a post/article/comment should be added. Session activity and the logged-in user controls should be done in corresponding pages. | Bengin | 18.11.2022 23:59 | Halil | 19.11.2022 21:00 |
3 | Drawer should be updated to show username of a member user or full name of a doctor user. Notifications and settings buttons should be removed. | Halil | 04.12.2022 21:00 | Oğuzhan | 05.12.2022 12:00 |
4 | Necessary form fields should be added to the edit profile page. | Oğuzhan | 04.12.2022 21:00 | Bengin | 05.12.2022 12:00 |
5 | Comment creation page should be created. | Kardelen | 04.12.2022 21:00 | Halil | 05.12.2022 12:00 |
6 | API functions for getting all posts and articles in the home page should be created and connected to the home page. Pagination should be handled also. | Halil | 04.12.2022 21:00 | Kardelen | 05.12.2022 12:00 |
7 | API functions for getting a single post and a function for getting a single article should be created. They should be connected to the home page also. | Halil | 04.12.2022 21:00 | Oğuzhan | 05.12.2022 12:00 |
8 | API functions for upvote/downvote functionalities should be created. Necessary page connections to this function should be done. | Kardelen | 04.12.2022 21:00 | Bengin | 05.12.2022 12:00 |
9 | API function for comment creation should be created. Necessary page connections to this function should be done. | Kardelen | 04.12.2022 21:00 | Halil | 05.12.2022 12:00 |
10 | API functions for getting a user's upvotes, posts and comments should be created. Necessary page connections to these functions should be done. | Oğuzhan | 04.12.2022 21:00 | Kardelen | 05.12.2022 12:00 |
11 | API functions for post/comment/article deletions should be created. Necessary page connections to these functions should be done. | Kardelen | 04.12.2022 21:00 | Bengin | 05.12.2022 12:00 |
12 | A doctor profile page that can be reached by all users should be created. | Oğuzhan | 04.12.2022 21:00 | Kardelen | 05.12.2022 12:00 |
- Screens and functions about the search functionality is not mentioned in this meeting. It will be considered in the following meetings.
- A page for doctor profiles that can be reached through their posts/articles/comments will also be considered later. After such a screen created, necessary API functions and connections should be implemented.
- Some action items has many subtasks, so there can be multiple issues related to a single action item in this meeting note.
🏠 Homepage
- Alper Canberk Balcı
- Baver Bengin Beştaş
- Burak Mert
- Halil Burak Pala
- Kardelen Demiral
- Sinan Kerem Gündüz
- Yavuz Samet Topçuoğlu
- Mehmet Emre Akbulut
- Oğuzhan Demirel
- Engin Oğuzhan Şenol
- Irfan Bozkurt
- Ozan Kılıç
Meeting Notes From CMPE352
Meeting Notes From CMPE451
- Meeting 13.1
- Meeting 14.1
- Meeting 15.1
- Meeting 16.1
- Meeting 18.1
- Meeting 19.1
- Meeting 20.1
- Meeting 21.1
- Meeting 23.1
- Meeting 24.1
Backend Team Meetings
Frontend Team Meetings
Mobile Team Meetings
- Customer Meeting 1
- Customer Meeting 2
- Customer Meeting 3
- Customer Meeting 4
- Customer Meeting 5
- Milestone 1 Presentation Notes
- Milestone 2 Presentation Notes
- Milestone 3 Presentation Notes
Scenarios
- Scenario 1 for CMPE451:Milestone 1
- Scenario 2 for CMPE451:Milestone 1
- Scenario 1 for CMPE451:Milestone 2
- Scenario 2 for CMPE451:Milestone 2
- Scenario 3 for CMPE451:Milestone 2
- Scenario 1 for CMPE451:Final Milestone
- Scenario 2 for CMPE451:Final Milestone
- Scenario 1 for CMPE352
- Scenario 2 for CMPE352
- Scenario 3 for CMPE352