Remote: Iteration Plan for January 2020

[kieferrm]

This plan captures our work on the Remote development extensions in January. We follow the same iteration cycle as VS Code. Although we plan for a whole iteration, we not only ship at the end of an iteration but throughout.

Plan Items

Below is a summary of the top level plan items.

Legend of annotations:

Mark	Description
🏃	work in progress
✋	blocked task
💪	stretch goal for this iteration
🔴	missing issue reference
🔵	more investigation required to remove uncertainty
⚫	under discussion within the team

Remote - Core

• Provide common UI for port forwarding (finish API, persisting of forwarded ports per workspace) Unified port forwarding UI #1777 @alexr00
• 🔴 Investigate improving reconnect behaviour @alexdima @sbatten
• Improve case-sensitivity for file system providers Case-sensitivity and file system providers vscode#48258 @isidorn
• Improve downloading and uploading of files Drag and drop from remote to Windows explorer not working #1839 Incorrect pre-filled folder name when "Download"ing a folder #1840 https://github.com/microsoft/vscode-remote-release/issues/1149 Downloading a remote file from explorer does not overwrite a local file with the same name when there is no extension in the filename. #1851 @isidorn

Remote - SSH

• Adopt common port forwarding UI in Remote-SSH Adopt unified port forward UI in Remote-SSH #2077 @roblourens
• Productize support for Remote server support on Windows Windows Server Support #25 @roblourens

Remote - Containers

• Open repository in container - support private repositories (private repos, more flexible volume usage) Open Repository in Container does not work with private repos (even if credential manager setup) #1578 @chrmarti @Chuxel
• Adopt common port forwarding UI in Remote-Containers @alexr00
• Simplify adding extensions to the devContainer.json: Provide Intellisense and validations for the extensions section Make it easier to put an extension in my devContainer.json #1800 @chrmarti
• Explore dotfiles repositories https://dotfiles.github.io/ Explore dotfiles repositories #2153 @chrmarti
• Improve the experience when user is iteratively developing a devcontainer's Dockerfile and the building fails. Provide access to the last log, make reopen locally a primary action) Improve iteratively developing a devcontainer's Dockerfile #1125 @chrmarti
• Add 'Rebuild and Reopen in Container' Add "Rebuild and Reopen in Container" #1750 @chrmarti
• Investigate .devcontainer support for the VS Code repo Investigate .devcontainer support for the VS Code repo #2154 @chrmarti
• Introduce a forwardPorts property to reduce port conflicts Port forwarding issue in Containers #1009, Remote Explorer shows container published ports as "forwarded", which is misleading #1809 @chrmarti
• Complete roll out of first set of pre-built vscode-dev-containers images speed up first time experiences Pre-build images for Microsoft maintained container images in this repository vscode-dev-containers#140 @Chuxel

Remote - WSL

• Support 'Reveal in Explorer' Support 'Reveal in Explorer' in WSL #1659 @aeschli
• Explore: Allow piping to stdin Allow piping to stdin #1764 @aeschli

---

Deferred Items

• Explore using the git installed on Windows remote-wsl: allow some way to use Windows git for git repo #1844 @aeschli

[bhack]

Please give some sense to the community top upvoted priorities in containers section:
https://github.com/microsoft/vscode-remote-release/issues?q=is%3Aopen+label%3Acontainers+sort%3Areactions-%2B1-desc

[imba-tjd]

I have the same issue of Allow piping to stdin #1764 using Remote - SSH

[Chuxel]

@bhack We've been away for the holidays, but now that we're back I wanted to briefly mention that the draft 2020 roadmap for VS Code was published before the holidays which includes Kubernetes investigations (along with macOS which is the top one today). See the VS Code Roadmap and Remote Roadmap drafts.

For a bit of insight, here’s a how we’re thinking about new platforms: For existing platforms, we know that lots little or medium sized issues can cause major problems for something you use every day. We don’t want to let the community down, so we want to be sure we’re in good shape on existing supported platforms before moving onto the next one. When the product is at that point is primarily driven by community feedback - particularly the 2000+ issues that have been logged here. Each platform we’ve added has had its own unique challenges, even for something as consistent as SSH, and we know Kubernetes is going to be bigger change particularly given we try to cater to people running any of the three major platforms locally (Linux, macOS, and Windows). For SSH, we started with server operating systems, and containers we started with Docker - so while we haven’t picked them up quite yet, macOS and Kubernetes were explicitly called out on the roadmap given community interest.

Also, if anyone is interested in the planning process, the VS Code Remote Development extensions use the same process as VS Code. As with the microsoft/vscode repo, once we understand an issue, we watch 👍 reactions across issues to understand interest rather than individual responses due to the sheer volume of them that comes across between the two repos. We absolutely hear the feedback and definitely appreciate the upvoting - it really does help!

[bhack]

@Chuxel We cannot help you to achieve this Roadmap faster. It Is the downside of the full closed source strategy on this extension.
So It Is totally out of our control how many resources you can allocate on this extension. We can just ask you to schedule incrementally over the most popular upvoted features.
If these are too big you can just approach incrementally as you have done with the other core features.

[Coderx7]

Please add offline support for completely offline/behind firewall systems (both host and the remote) #2176
The current situation assumes, the host has access to internet but this shouldnt be. at least providing an offline package with all the dependencies would be great (just like how the cpptools extension does it)
Thank you all very much for all of this.

[Lastwisher]

Also there this one one of highest voted feature request and its fairly simple one

#222

Just need a option for argument