Release 2.9 rethinking about my goal

Which part of Telescope 3.0 do I own?

In the past 2 weeks in telescope, I have been working in Docker, nginx, and oauth. So I guess I'm gonna own those parts.

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?

• Add full OAuth2 capabilities to SSO service #3088, new issue, after adding oauth to Portainer, we found that it's not convenient to create 2 different oauth github app for staging and development, also in the future if we want to secure more route with oauth2-proxy, we will have to create more oauth github app. This issue will solve that, by enabling full OAuth2 capabilities in our SSO.
• Apply Dockerfile best practices from Snyk recommendations #1668, undergoing, I started to refactoring some Dockerfile already and will keep refactoring the rest for 2.9 release.
• Refactor all our dockerfile to use our base image. #3278, new issue, in #2803 we created a base to be used in all other of dockerfile.
• Expose supabase studio under nginx #3033 - undergoing, waiting on #2979, once the secret thing is done. I can push my local change into it.
• See if our nginx configs make any of these common mistakes #3029, new issue, this issue for check if we setup our nginx config correctly.

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

@TDDR, is our Docker guy, along @manekenpix, and @humphd who knows most of the telescope part and provide a lot of help.

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

I think time is a big issue. With my course load specially PRJ class + job hunting + doing research and preparing the document to be able to work in Canada is starting, my schedule is getting filled quickly. I started 2 different side projects at the beginning of the semester utilizing web3, nextjs, and redux, but had to pause them because not enough time.

How will I mitigate these risks?

I think to mitigate those risks. It will be great to find more contributors to have an interest in oauth part and docker. Working as a group is much faster than working alone.