Dev setup precision to use devcontainer

[bougui]

In reference to this request Remove obsolete dev-setup documentation #1908

[WadeBarnes]

I'd recommend getting rid of the whole dev-setup folder.

[bougui]

@WadeBarnes, done like proposed.

Guillaume

[WadeBarnes]

Great. However the ./docs/source/setup-dev.md, which is referenced on the main page, still contains references to the dev-setup folder as well as instructions on how to set up a bare metal development environment manually. That document could be deleted and the relevant content about using the dev container moved out to the How to Start Working with the Code section of the main README.

[bougui]

@WadeBarnes I would keep the file since the python instructions are still relevant and it make the main README.md file bigger If I bring back what was in the setup-dev.md. Since we already have a seperate file I propose to only delete part refering to the code that is not maintain anymore.

[WadeBarnes]

@WadeBarnes I would keep the file since the python instructions are still relevant and it make the main README.md file bigger If I bring back what was in the setup-dev.md. Since we already have a seperate file I propose to only delete part refering to the code that is not maintain anymore.

If there are still manual development environment setup steps that are relevant, I'd suggest those steps be incorporated into the dev container setup so everyone has a consistent development environment. However in this case I'd argue the python virtual environment is more relevant to a bare metal setup where the user is more likely to have a conflicting version of python installed. The dev container sets up the version of python supported by the corresponding version of Ubuntu and code, and it's already a virtual environment.