Enforcing the Telescope Law

-

Howdy,

You are speaking to this week's Telescope Sheriff's. That means I (along with my fellow OSD peer Kevan) carry the responsibility of leading the maintenance of the Open Source Telescope repository. That includes, reviewing PRs, filing issues, following up on backlogs, and more.

Tomorrow we'll be having our OSD700 class where it really just is one big meeting or status update on everyone's tasks. In that meeting, we summarize the progress of our big topics(which right now includes Supabase, React Native, new Services, just to name a few), follow ups on the issues set up for the next minor release (2.7) next week, and just updates on what everyone's tasks are or how their progress is going.

It'll be my first time trying to lead a big team of developers (most of them who are way more skilled/knowledgeable than I am) so I hope I can lead it in the right direction. Either way it'll be really good project managing experience.

OSD700

Last week, after jumping from issue to issue, I finally ended up doing some backend work for an issue regarding JWT signing in our auth service. I got assigned to that issue because Dave said it would be a good opportunity to anyone looking to do some deep back end work, and so I volunteered. Between then and now, I've gained a lot of knowledge on how JWTs , authorization and authentication, and our auth service works.

On the other hand, we're currently trying to implement Supabase as a firebase alternative for Telescope. This means services such as auth and users will need to be modified to reflect the Supabase changes. And because of that, a lot of the solutions for the previous auth issues have to be rethought of. For example, the JWT issue was initially to switch to private/public key signing, but it seems like Supabase only supports a shared secret for the tokens at the moment, so we'll have to put that on hold.

Dave's been super helpful and informative with the research process too, by referencing docs, giving suggestions for solutions, etc. Right now I'm working closely with Duc, who's leading the helm on this Supabase stuff, to help implement it, which right now includes making the e2e tests for the newly renovated SSO service (previously auth) Other than that, some changes need to be made in the users service.

Conclusion

Hopefully the Sheriff responsibilities won't deprive me of time to code. I'm still waiting for my big PR to hit the repo, and I'm working on it to make it happen!

Comments

Post a Comment

Popular posts from this blog

HacktoberFest Entry No.2

-
Image
So around last week I found a great github repo of a chrome extension that previews contents of a webpage when you hover over a link. I stumbled upon it after a suggestion from my professor about taking a look at chrome extensions for a possible repo to contribute to. I'm glad I did because this was a chrome extension that was interesting, seemed practical and had a maintainer who was keen on receiving contributions to better his program. The extension is called Survol First I had to install it and test it out first, can't just contribute to a repo meaninglessly just to force a pr. I tested the extension and liked the functionality, it was useful and is well designed. Makes it all the more exciting for me to try and contribute to it. So I read the docs and learned how the extension worked. It uses a javascript file to inject html elements through the dom and uses mousemove event to detect anchor links to request information of a page, and positions and fills the div with conten...
Read more

Lab 1 : Our First Open Source Contributions

-
So for Lab 1 our tasks were fairly simple. Find a partner to review a repo on and make contributions, no matter the scale, to their code. Be it a suggestion for their code, reporting an issue, or even fixing up small details in their readme. So through slack I partnered up with one of my coursemates  Niaz Much like me, he wrote his code in nodejs, so it was perfect since I can go through his code easier through my understanding of node. His code, though written in the same language, differed from mine a lot. For one, he didn't use yargs so he had to process the arguments manually, and secondly he didn't use fetch and opted for a module called linkinator. No problem, in fact it's an opportunity for me to understand the logic and components that he used. I forked a copy of the repo, cloned it and tested it out for myself. The code worked perfectly as intended and processed urls well. Functionally, I couldn't find find anything in the code I could identify as a flaw or imp...
Read more

Hack.... vemberfest.. PR No. 3

-
Image
OK so this is pretty long overdue (sorry Prof!) And I still have one more pull request to go and that's on me yes. BUT, this week I spent working (or should I say learning) on our course's aggregated blog website which coincidentally, our prof is making us work on this week for the lab, so I guess I got a good head start going on.  So I took on an issue that seemed pretty straight forward in the repo. It was to change the functionality of the search bar when filtered by author. Seemed pretty straightforward enough, so I went ahead, forked the repo and cloned it on my computer. Now the reading begins, the lengthy process of coding. And the fact that this was a whole website coupled with different technologies that I'm not familiar with only made it waaayyy longer, which maybe is a sign that I should have started working on this much much earlier. But that's what happens when your time management skills is hot garbage. Anyways, I spent the next few days learning about eac...
Read more