This past week it was my turn to be sheriff for the Telescope project. There were a lot of responsibilities and a lot of tasks to complete.
A big part of the role is to lead the weekly meetings, go over outstanding PRs and assign tasks for the following release. It was my turn to be at the helm of the ship and to always be available on Slack if any problem occurred. Looking at all the incoming PRs forced me to have a more holistic view of Telescope and learn more about all the great things other students are working on.
My outstanding PR about Turborepo linting was merged and I will have another blog post to talk about it in more details.
Breaking Telescope
Everything went pretty smoothly until it was time for the release. While on a call with Tue and David, releasing version 2.7 of Telescope first broke production and then staging.
The call quickly turned into a one hour debugging session and I experienced first hand how to debug Docker containers from David (Which is something still new for me).
The issue was caused by a recent PR that changed SECRET to JWT_SECRET (To use with the latest version of Satellite) without adding the required variables in env.staging
and env.production
.
Project management
Over the week I reviewed many more PRs than in the past and merged a lot of them into master myself. I also added milestone labels and tags to keep things organized.
This experience made me realize how much non coding related work there is to manage an open source project. I now understand why teams in big projects have people specialized in doing this all day and keep team members accountable and on track with their work.
Top comments (0)