First time being a Sheriff
Published: 2022-04-12 08:43:19

# What is a Sheriff in Telescope:
Sheriffs will be the one who help and manage the current project. They make sure to keep the team on track and shepherd their code through the review process so that the release of that week can be landed optimally without breaking any tests, CI. Each week, there will be 2 main Sheriffs and if one of the 2 Sheriffs cannot take the duty, a backup Sheriff will take the job. 

# Overview
This week, I had a chance to be a Sheriff with Tue. This week was a little bit different, we wanted to focus more on completing the current features and fixing current bug for the release 3.0 alpha. This means that we needed to "say no" to some new features or current features that are not important. Instead, we would focus wholly on important features. Here is the list of features from the email of our professor David Humphrey:
- Finish the Parser service (done) and remove the Legacy Backend (not done)
- Finish our monorepo tooling (eslint, tests, pnpm, etc), and fix edge cases we're hitting now (getting closer, but not all done)
- Finish Dockerfile/Image optimizations and use our new Docker Registry for all of our images and deployments (getting close to being done)
- Ship and finish the first version of the Docusaurus docs, including docs on anything that the next set of students will need (not done, but almost)
- Get an Alpha (i.e., usable to read posts) version of the React Native App shipped (not done)
- Fully integrate Supabase into our front-end and back-end in production, and stop using the Wiki Feed List (not done, and this one is critical for 3.0)
- Use our front-end Sign-up flow for adding new users/feeds (not done)
- Finish Search/ES improvements (progress, but not done)
- Finish YouTube/Twitch feed integration (getting close, not done)
- Finish dependency service so that it's usable by the next set of students in the fall for finding bugs to work on (progress, but not done)

# Planning and meeting
To make things more easily, me and Tue created a [new page](https://github.com/Seneca-CDOT/telescope/wiki/Triage-Meeting-March-29,-2022-Preparing-for-Release-3.0-alpha) in GitHub to group the issues into different areas. On Tuesday, I lead the meeting and at that time, I went through every current issues that were listed in our prepared sheet on GitHub. Everyone joined and helped me a lot on explaining the issues and giving me an update of the progress. And on Thursday, Tue helped everyone on reviewing the current PRs, we assigned more people to the PRs that needed to be finished the most and unassigned those who lost the interest to the PRs they had been working on. Everything went really smoothly because everyone did a good job. 
# Progress
Tue and I helped people on reviewing their PRs as well as asking the people in the current issues about their progress. The issue I cared the most was about React Native. I asked everyone to review my [PR](https://github.com/Seneca-CDOT/telescope/pull/3320) about the mobile app footer so that it can be merged immediately, and helped James to complete his [PR](https://github.com/Seneca-CDOT/telescope/pull/3346) about using Supabase to share file between both front-end web app and front-end mobile app. In the mean time, I was working on the [loading posts](https://github.com/Seneca-CDOT/telescope/issues/2857) for mobile app but since this week was overwhelming for me so I could only touch that issue just a little bit.