[Announcement] State of vscode-dev-containers contributions

[bamurtaugh]

Hi folks! We wanted to give you the latest update on this repository.

We're currently thinking about how to best scale the growth of dev container definitions, as there's increasing interest in new definitions and configurations. This includes how to best manage existing and future community contributions. We'll be having open discussions on this in an issue in the new dev container spec repo.

We are also evolving the idea of a dev container feature, with the goal of being better able to mix, match, and share config that can be acquired remotely. You can view and join the discussion in this issue, and read more about features in this doc.

Please know that we tremendously value your contributions to and usage of dev containers and their definitions! In the near-term, we'll look to accept changes in this repo with a high-priority user impact/need. For the long term, we're still discussing the best process to accept and manage contributions. Since there may be fewer responses in this repository as we figure out this plan, we wanted to make you all aware and assure you that we see and appreciate your work.

Thank you for your patience and engagement!

[samruddhikhandale]

Closing this in favor of a latest update mentioned in #1589