• Allow devcontainer.json to be used to define DevSpaces workspace.
• Whether developers are working locally in VSCode or DevSpaces, it would make sense to allow defining the Workspace of DevSpaces also in the `devcontainer.json` file.
  This would allow developers to have reproducible development environments by providing and maintaining only one workspace description file, regardless of whether they want to work in DevSpaces or also locally in VSCode.

• You must create and maintain a `devfile.yaml` and a `devcontainer.json` separately to achieve this, leading to more maintenance effort and possible drifts in the configuration, like having different development images defined on accident.

• It would be great to implement some translation layer, e.g., allowing to define a `devcontainer.json` in a project and DevSpaces automatically translating it to a `devfile.yaml` or DevSpaces being able to use the `devcontainer.json directly`.

As mentioned in the proposal, the customer currently always have to maintain two different files, which is a maintenance overhead and can lead to possible configuration drifts.