Triage Meeting March 16th 2021

TRIAGE MEETING (March 3rd 2021) LEADER: Chris Pinkney WRITER: Mo

Cleaning up 1.8:

Issue #1412:

• Royce's Solution was to keep the UI the same, but reduce the size of the link itself.
• Pushed back to 1.9
• Try to get our CSS experts on this

Issue #1931:

• Dividing the Issue into Multiple Issues, for Microservices.
• Move some of the jobs onto Satellite

Issue #1929:

• Porting this over to Satellite, planned meeting today at 3 pm
• Working on this issue, in tandem with #1931

Issue #1932:

• Chris continuing to do research on Firebase

Issue #1611:

• Can't push back to 2.0, need to understand what out scope is
• Talk to Dave on breaking up our scope for the GitHub integration
• Planned for 3pm, today

PR #1954:

• Landed AuthService, looking for more reviews
• Complicated, due to not having a single backend/frontend
• Needs review, so that we don't break anything when merging to master

PR #1909:

• Implemented Requested Changes
• Bug with Search Bug in Production, duplicates "Help" on the Search Bar
• Pulling up the Search Bar on Staging [changes weren't deployed?]
• Rebase to master, then ask for reviews again

PR #1953:

• Incorporating POSTS into the Frontend portion of Telescope
• Tests Fails everytime, figuring out why they fail
• PR is done, after the tests are fixed, merging should be possible soon.

PR #1802:

• PR has been worked on recently, dave finished review
• PR should be good for 1.9
• Once the PR is cleaned up, it'll be ready for review

PR #1828:

• Need to finish User microservice before working on this PR
• Put into 1.9 for now, clarify with c3ho if they want to continue with this
• Might need some help, so we need people to take over the Issue/PR

Issue #203:

• Pushed into 1.9, asking if someone wants to work on this?
• Removed from 1.9, left with no milestone since there was no work

Issue #290:

• Chris wants to take a look
• Unsure if this will come in 1.9 due to UI 2.0 work
• Assigned to Anton, mentioned Josue on the collaboration

Issue #567:

• Contemplating if this is required?
• Quite a big bug, might assign parts to other people
• Close for now

Issue #570:

• Should work on this due to Depreciated Promise Rejections
• Tests might not work properly, an audit maybe required

Issue #653:

• c3ho has been working on this
• Adding to 1.9 to look? We've made an audit to logger, might want to take a look again
• Wait until PR #1828 Lands before revisiting issue

Security Overview for GitHub:

• Looking at Security Policies for CI/CD Bots
• Implementation? Need to learn/play around with it more
• Anton will look into it.

Issue 667:

• Implement CORS in Satellite
• Possibly breakup cors() into multiple modules
• Possibly Restrict Routes to certain domain names
• Possibly pass extra header when required & allow cookie sessions

Issue #801: Chris will take on the issue, will collab with Tony

Issue #780:

• Might have to shelf, cause Ilya is coming back in 2 weeks
• Printing possibly in Canada?

Issue #828:

• Closed in favour of 1938, since it's an updated version

Issue #858:

• We don't use /stats/ in the backend, but we have a Stats microservice issue
• We close in favour of the Stats microservice (#1829)

Issue #910

• Removed, we don't need it anymore due to UI 2.0

Issue #1004:

• Running behind 2 proxies instead of 1
• Port this over to Satellite instead, leave a note for Telescope

Issue #1039:

• Discussed the bug in question, closed due to the bug being fixed in UI 2.0

Issue #1037:

• Ban users who constantly add feeds they don't own
• Even with implementing Firebase, this is still an issue
• Ask the user not to add feeds that they don't own

Issue #1938:

• Add Health Check into Redis
• Wait for Mo to finish PR, today.
• Simple fix, added to 1.9

Issue #1058:

• Talk between Chris and Dave to see how to implement this Issue
• Approach right after we implement the User service