Mid way before release 2.6
Tags: opensource
Published: 2022-01-29 15:49:31

A lot happened this week, on Tuesday meeting the sheriff, went through the task to-do for release 2.6, and on Thursday it was a triage of Pull requests and issues. During the triage, I go assigned to more issues, in the area of react native, docker, and a bit of front-end fix.
Also, did my first release on an open sources project in [Satellite repo](https://github.com/Seneca-CDOT/satellite).

## What I have done for release 2.6

### Issue listed from my previous blog

- [Issue #2678](https://github.com/Seneca-CDOT/telescope/issues/2678) - Fixed by [Pull Request #25](https://github.com/Seneca-CDOT/satellite/pull/25). This wasn't too difficult to do since it was just removing `@elastic/ecs-pino-format`, `elastic-apm-node`, and its code. Then update `jest` for fixing deprecating dependencies.
- [Issue #2694](https://github.com/Seneca-CDOT/telescope/issues/2694) - Fixed by [Pull Request #37](https://github.com/Seneca-CDOT/satellite/pull/37). This one was a bit of research with `pnpm engine` and `yml`. Thanks to this [Pull request #2545](https://github.com/Seneca-CDOT/telescope/pull/2545). It helped me to complete this issue quickly. I also had to learn about yml file and ci, how it's configured. Documentation I read, [Github ci/cd](https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python), [Actions setup-pnpm](https://github.com/marketplace/actions/setup-pnpm), [Actions setup-node-js-environment](https://github.com/marketplace/actions/setup-node-js-environment), and [Actions checkout](https://github.com/marketplace/actions/checkout). 
- [Issue #2499](https://github.com/Seneca-CDOT/telescope/issues/2499) - Fixed by [Pull Request #26](https://github.com/Seneca-CDOT/satellite/pull/26). Thanks to my cloud computing class. I had used what I learned from that class and transferred to contribute to this issue. This makes me feel happy and glad to have taken this course, that I was able to use what I learned from a class and used it for other things besides class assignments. 
- [Issue #2497](https://github.com/Seneca-CDOT/telescope/issues/2497) - Fixed by [Pull Request #2700](https://github.com/Seneca-CDOT/telescope/pull/2700). This issue was similar to [Pull Request #26](https://github.com/Seneca-CDOT/satellite/pull/26), but for the date format, I had to read a bit of documentation [pino-pretty](https://github.com/pinojs/pino-pretty), and [node-dateformat](https://github.com/felixge/node-dateformat). Why [node-dateformat](https://github.com/felixge/node-dateformat), because it's what [pino-pretty](https://github.com/pinojs/pino-pretty) uses for `translateTime`.
- [Issue #2306](https://github.com/Seneca-CDOT/telescope/issues/2306) - Issue still under progress, this one is a bit hard to reproduce since I get blocked by Medium. I had a hard time getting the feed data from telescope. I talked with Duc, the one who created that issue, he also had trouble reproducing it. Since most of our users use dev.to as blog posts. This issue is not my priority and will be put in the backlog.

### What I have picked after my previous blog

- [Issue #39](https://github.com/Seneca-CDOT/satellite/issues/39) - This was a hotfix fixed by [Pull Request #40](https://github.com/Seneca-CDOT/satellite/pull/40), telescope e2e was failing because in satellite repo we added `preinstall` to only use `pnpm` but docker was still using `npm`, so it was failing there during the installation. I had to revert and do a release. The process to do a release was pretty simple thanks to this [Issue #38](https://github.com/Seneca-CDOT/satellite/issues/38), documented by AmasiaNalbandian. 
- [Issue #2707](https://github.com/Seneca-CDOT/telescope/issues/2707) - In progress will be fixed by [Pull request #2751](https://github.com/Seneca-CDOT/telescope/pull/2751), this one was a bit tough to do, it was either grab the username from the regex and do a call to the API of GitHub to check if real username, but with that solution, we'll hit the API rate in a second. The second solution is less perfect but will work, it was to hardcode the list of reserved names, and in the filter only grab the ULR that doesn't match the reserved names. I had a nice talk with Andrew, the one who created that, and since we cannot filter all the GitHub names, it could be considered as [The Ostrich algorithm](https://en.wikipedia.org/wiki/Ostrich_algorithm).
- [Issue #2731](https://github.com/Seneca-CDOT/telescope/issues/2731) - This is still in progress and with some discussion with the group that does react native, it will be done by Hung.
- [Issue #2732](https://github.com/Seneca-CDOT/telescope/issues/2732) - Issue open for discussion about the deployment of the react native app.
- [Issue #2733](https://github.com/Seneca-CDOT/telescope/issues/2733) - Issue open for discussion, and mainly will be done by AmasiaNalbandian. I will assist in reviewing Pull request.
- [Issue #2734](https://github.com/Seneca-CDOT/telescope/issues/2734) - Issue open for discussion, and probably mainly will be done by AmasiaNalbandian and DukeManh. I will assist in reviewing Pull request.
- [Issue #2745](https://github.com/Seneca-CDOT/telescope/issues/2745) - I will be working on this one, I have a sort of working version in my local, and will create a Draft pull request for feedback since I'm not too familiar with docker. Used this [documentation] (https://docs.docker.com/engine/reference/builder/) to complete this issue.

One of the best quote:

> Never be afraid to fail. Be afraid of not learning from mistakes. 
> -- W. Brett Wilson 

Open source is the place where you make mistakes and learn from it to become a better developer.