The End Draws Near
Tags: opensource
Published: 2022-03-18 00:54:44

This week's blog is going to be a little different than the others. Instead of doing a walk-through of the work I've done, this week we have been asked to plan for the inevitable conclusion of our course. The following questions have been given to us:

**1)** Which part of Telescope 3.0 do I own?
**2)** Which existing Issues are part of this?  Which new Issues do I need to file in order to properly describe the work? When will those issues be filed?
**3)** Who can I depend on for support in development, debugging, testing, and reviews?  I can't do this alone.
**4)** What are the risks that I see, which could prevent me from getting this shipped?
**5)** How will I mitigate these risks?


## Which part of Telescope 3.0 do I own?

As mentioned in my original [planning blog](https://dev.to/tddr/a-glimpse-into-my-future-40ka) a few weeks back, I plan on owning the new Docker registry we have set up. Most people in the course are aware I'm the Docker guy, even though I know there's others in the class who probably have a better understanding of it all than I do :sweat_smile:

## Which existing Issues are part of this?  Which new Issues do I need to file in order to properly describe the work? When will those issues be filed?

![Issues](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/lv0y3r2r59c9676w8i1l.png)

My main area of concern right now for release 2.9 is attempting to slim the Docker images. After going through the process outlined in [issue #3189](https://github.com/Seneca-CDOT/telescope/issues/3189), to start actually using our registry images in staging an production, I must do the same process for all of the other microservices used in the project. 

Once the images have been slimmed and our registry put to use, I think I can confidently say that "I own Docker", or at least the registry for Telescope. 

## Who can I depend on for support in development, debugging, testing, and reviews?  I can't do this alone.

[Kevan](https://dev.to/pandanoxes) has been a huge help in getting the registry up an running. He was the one that did the majority of the authorization portion needed for the registry. 

Josue, who is an alumni from the course, and who has also helped me out a great amount in setting up the registry, will be of great assistance on things to come, I am sure. 

Finally, the professor himself, HumphD, will also be a key player in the success of this. As he has been for entirety of the course. 

## What are the risks that I see, which could prevent me from getting this shipped?

I seem to be hitting a rut here this week. I don't know if it's just the daylight savings time kicking my butt, if I'm fighting something off, or what is happening, but I have found it hard to concentrate on work/school this past week. Hopefully I can snap out of this daze soon and start feeling productive again. 

Another risk is not asking for enough help. I feel like I am finally getting a better understanding of how you can configure and use a `Dockerfile`, and `docker-compose`, but I know I still have a lot to learn. I have done some more reading into the issues on deck and I feel like I'm at a loss for what to do. I just need to remember that I'm almost always lost and that my educated guesses have been spot on or pretty darn close so far, just gotta trust my gut and reason it out like I always end up doing.

## How will I mitigate these risks?

In order to mitigate these risks, I just need to follow my own advise from last week and send up a PR so that I can start collaborating. Even though I am taking ownership for the registry, it's still a team effort.