DEV Community

Tue
Tue

Posted on

Narrowing the work scope

We're only 2 releases away from 3.0 so we need to narrow the vision and focus on what we want to ship in 3.0

What part do I own?

  • Well, I've been working on Parser exclusively, it's moving slower than I thought and I've hit a road block where I can't get the Parser service to shutdown gracefully which affects Jest to not shutdown cleanly.
  • I've also looked at and attempted implementing Supabase so I'll help Telescope to bring it to the front-end and rework Parser to use Supabase. To do this, I need to under the Docker pieces more essentially, we need to hide the Supabase studio behind Portainer (admin app for Docker containers).
  • There's also a PR I put up but there have been different opinions, let's see how we can solve it

Foreseeable roadblocks:

  • To this point, I'm not sure why my e2e test is not working properly, I think I'll ask a few people to join a call so that I can demonstrate the problem.
  • I might need some time with Docker but I think I'm catching up quite quickly
  • Communication between areas is actually very important and hard which is often overlooked, my Parser will be reworked to user Supabase, to serve Dependency Discovery's purpose.

Top comments (0)