MVP - Talawa API

[palisadoes]

This is a parent issue for tracking purposes

We need to have an Talawa MVP by the end of the year. The MVP will be the master branch. To do this we will need to remove features that either don’t work or have insufficient functionality.

The features to remove include:

1. Links to chat (Handled by PR)
   1. commented firebase notification code #1503
2. Notifications (Handled by PR)
   1. commented firebase notification code #1503
3. Dynamic linking (Handled by issue)
   1. Remove Dynamic Linking (MVP Prerequisite) #1510

Other

1. You need to work on removing these functionalities from this repo and work with the contributors below to make sure the correct functionality occurs in the other repos.
2. Documentation related to configuring these features needs to be removed as they will be no longer valid.
3. Test code coverage needs to be maintained. Coverage for the PR patches needs to be 100%

The plan is to:

• remove these features from the develop branch by commenting out the code.
• merge the develop branch not containing these features into our master branch.
• make the master branch the default

Please work with @Ayush0Chaudhary (Talawa impacts), @kb-0311 & @xoldyckk (Talawa-API impacts) @beingnoble03 (Talawa-Admin impacts). Ask to be assigned this task by them.
Issues related to this one include:

• MVP - Talawa Admin talawa-admin#1069
• MVP - Talawa API #1427
• MVP - Talawa talawa#2108

[kirtanchandak]

@Ayush0Chaudhary I can take this task

[palisadoes]

1. It may be sufficient to remove access to the features in the Talawa-Mobile MVP and Talawa-Admin MVP PRs alone to achieve this goal.
2. Please work with @kb-0311 & @xoldyckk on this. Though the features mentioned don't work, we may want to leave the API code unchanged so that further work can be done on the features to make them really work.

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[palisadoes]

Unassigning due to inactivity and no submitted PR

[zakhaev26]

Can i please be assigned this issue @kb-0311 @Ayush0Chaudhary @xoldyckk @beingnoble03 ? I am currently learning the codebase and would like to contribute in it!

[punitkr03]

Hey @Ayush0Chaudhary @kb-0311 @xoldyckk @beingnoble03, I can work with @zakhaev26 (classmates) and can contribute to this issue. Can you please assign this issue to both of us?

[noman2002]

@punitkr03 One person per issue.

[palisadoes]

@zakhaev26 The features are to be disabled in Talawa and Talawa-Admin.

1. We are planning on using locally generated notifications, so this feature should be disabled in the API if it supports it in any way.
2. Similarly, we decided to disable deep linking, so this feature should be disabled in the API if it supports it in any way.
3. Though we are removing chat functionality from Talawa and Talawa-Admin, it will most likely be restored during GSoC 2024 but in a much less buggy way. We'll need to keep this functionality in the API. DO NOT REMOVE CHAT FUNCTIONALITY

Please confirm that you understand this.

[zakhaev26]

Sure,Currently having exams;will be working on it as soon as possible.

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[palisadoes]

Unassigning due to no activity and no PRs

[palisadoes]

Please work with the following persons to get this implemented

1. @Ayush0Chaudhary
2. @EshaanAgg
3. @kb-0311

[ayan-joshi]

Can I work on this issue , can u assign it to me @palisadoes ?

[palisadoes]

Assigning to @EshaanAgg as he's overseeing the API MVP effort. This is a parent issue.

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.