@BrunoQuaresma @dwahler - I put #2989 in the "smaller, but mighty" section since it's almost done and addressed in the July roadmap.

Putting all the replies in here to make the conversation a bit easier to follow:

@tjcran:
This sounds like it needs an epic to wrap all these together? Is there a need for an RFC on this to consider a more holistic strategy for dealing with it?
Also noting #3048 as related

@spikecurtis:
I'd want to start with some strategic discussion & brainstorming, maybe @ketang @kylecarbs @spikecurtis @tjcran (optionally @ammario, optionally other engineers with deep distributed systems experience). One outcome of that discussion could be to move to RFC, but it could also be that we're going to punt on the larger problem and just fix bugs.

@ammario:
@spikecurtis is this RFC something you are proposing for the August roadmap?

@spikecurtis:
My personal feeling is that this trumps several things on the August list, like activity based auto-off.

@ammario
I have encountered the problem personally and I agree it's a fundamental problem with our model that we need to resolve. We have a few issues related to this problem, and no silver bullet has been identified. There are a bunch of small things that make progress, e.g #3035 and #2256 (comment).

But it's not clear what exactly we would pursue on if the "orphanage problem" was added to roadmap.

You can probably think of more/better solutions than the aforementioned issues too.

Another thing to note is activity based auto stop has been requested many times by users where orphanage resolution hasn't.

@tjcran
I suggest we add the orphaning problem to the roadmap as an RFC item for August so we can work out how to solve it. But I don't think we can properly assess the cost and prioritize it to this month's roadmap without an RFC.

Moving conversation into a thread:

@tjcran
good callout. I'll make the update for #1763 item.
The workspace edit issue needs some prep work and some product direction. @bpmct were you still planning to work on that one?

@bpmct
#802 and #660 is something that we need to define more in August! However, it is still something we want to do in August. It needs an owner and I'd estimate it's fairly complex and needs backend work as well.

I added a problem statement and definition of done to #802, it is now a lot more than a page to edit parameters, as there is some underlying complexity that needs to be worked out first.

I think it will likely become an epic and spin out into a few different tasks, once a solution is landed on.

Opening IDEs and getting errors seems like basic error handling and should be a high priority.

I reported this in June.

Which IDEs are still seeing issues? @spikecurtis did a lot of work on JetBrains as part of the July roadmap #3042

I did work on JetBrains Gateway, which doesn't use coder_apps

Good point. Either way, I think the issue Ben suggested should be a high prio this month.

This one should be part of the September roadmap

I'll be working on getting this merged in today, probably under a flag. If we see no issues after dogfooding this week, I'd say it's good to make primary.

Cool - I'll add it under "must have" for August.

I went ahead and just added it.