my-photohub VS telescope

1) My Photohub 📸

1. My favorite repository: My-Photohub 📸

I picked my favorite Seneca College project my-photohub and successfully created two pull requests there.

Continuing from last post, I have completed my feature that produces optimized images, create a remote repository and make a commit with the files. My PR may be updated, but I think the change would not be so big from now.

1) The open-source contributions are going well! - I was able to successfully make pull requests to flutter and to my-photohub - I am currently working on responding to the issues I worked on.

For the following PR I had to come up with logo for the project.

I have had my pull request merged for creating the UI for creating a new project. What I have created is purely visual and has little functionality. With my contribution, I have integrated my UI with what already exists.

For 0.4, I plan to create the UI for my-photohub. I am choosing this project because I thought the concept of it was interesting. Also, I wanted to work on a React project, I had previously worked on a personal project using React and wanted to put that practice to use on a real project. Another reason I chose this project was because did not want to spend too much time looking for an external project to work on that was viable.

Continuing on my story for My PhotoHub Image optimization GitHub Action, my approach was to convert files using JavaScript framework Sharp and shell script creates a repo and pushes the files to it. I pushed my script with my questions to ask how we should deploy the app. With this PR, I wanted to make sure my approach was ok and what the next steps would be.

My Photohub: I have already contributed to this project a few weeks ago where I created the UI of the progressive web app (PWA) using React. I plan on working on the other issues filed for this project and try to get closer to the finished product of this project.

It all starts with an old 400 error that was occurring in Telescope for a while now, first documented here.

Sattelite for the back end

There are a few places to start with this, one is that we have an issue in Telescope that relates to what I think is the session no longer existing in certain situations that results in a 400. This will give me an opportunity to take a look at Telescopes auth flow. I still am kind of unfamiliar with Telescope despite having been in the last OSD course. I know that we use passport SAML in Telescope however and in the new project we will use a different library called SAMLIFY.

The project is currently in the planning phase, and being part of the development team, I have been researching ways to add relevant bits of Satellite in the Remix Blues Stack project, we intend on using for Starchart.

As a good well-established project, Telescope provides a great environment setup guide, which covers most use cases.

It's been a year since I was supposed to work on Telescope for a class. When the war in Ukraine started in February 24th, 2022, I almost fully stopped contributing. Now, this year I am trying to do more, even though it's not my class anymore. Because I wish that I did more back then.

This week, I decided to setup Telescope locally. I had previously contributed to telescope and had set it up already. However, I faced some problems starting it up locally after a shutdown and startup sequence. This was hard to debug since there was no error message, just containers on docker would not start up even after waiting for several minutes. These problems would fix after a restart or just randomly after a few tries. So, I decided to go through the setup again.

Task This week, I try to revisit my setup for running the Telescope project, a single page website that aggregates blog posts.

This week, I finished implementing the feature for filtering out irrelevant feed URLs. Previously, I had added a function for the filtering but had to write the test for it.

The two PRs(1 2) mentioned last time were merged without a hitch. For the one that's about parsing Twitch channel feed URL, the maintainer and I agreed that there should be a follow-up issue opened to expand it to YouTube Channel(s). They also found another bug in the sign-up that should exist as its own issue about the RSS feed URL(s) having incorrect domain. For details about them, please see my last post.