Web IDE Strategy to be more focused on what/why
Problem to Solve
It sounds like it’s sort of nebulous what the strategy is, or how we’re choosing what to work on for the Web IDE.
Additional Details
One way to think about that is that some of things (ci jobs, ci linting, editor in MR) is that they’re part of deeper integrations with the most used parts of GitLab. The lens that you’re looking at the Web IDE should help to communicate why you’re doing what you’re doing vs. all of the sort of random things that could be done.
Edited by Kai Armstrong