Preparing the open specification

[bamurtaugh]

Let's use this issue to track monthly goals and progress on the spec.

[bamurtaugh]

May goals:

• Move more content to devcontainers org
  • Public CLI and website repos
  • Template repo
• Ongoing partner discussions
• Amplify content
  • Initial blog post for cli, some spec context
  • More amplification once we have reference implementation, website, and template repos in place

Granular list:

• May Add appropriate code to devcontainers org
  • 🏃 Reference implementation Publish reference implementation #9
  • Json schemas(s) (to enable a proposal PR to be in one repository) Publish devcontainer.json schema #14
• Web content
  • 🏃 May Use custom domain to host GitHub pages site and in labels
• Docs
  • 🏃 May Re-hosted devcontainer.json markdown in spec repo https://github.com/devcontainers/spec/issues/pull/12
    • Add link from docs, aka.ms
  • May Finalize content in spec repo, i.e. more copy on intent of spec
  • May Info on intent of spec and repo overall in VS Code doc (already link to repo in Questions and feedback, but could use more context, link to reference implementation)
  • 🏃 May Blog post for CLI, PR: Dev containers blog microsoft/vscode-docs#5347
  • Strategy
    • More docs content (some of the "advanced" content, "hello world" using the dev container CLI)
    • What future and current docs live where?
• Content on supporting tools and partners
  • 🏃 May Supporting tools in repo and website Add devcontainer.json reference #12, https://bamurtaugh.github.io/dev-container-spec/supporting
  • 🏃 May Communicate with interested parties
  • 🏃 May Mention open spec in existing and future issues about alternate engines in vscode-remote-release

[bamurtaugh]

June goals:

• Expand and iterate content in devcontainers org, based on user feedback
• Scalable, secure plan for community template contributions
• Ongoing partner discussions
• Amplify content
  • More amplification once we have reference implementation, website, and template repos in place

Granular list:

• Add appropriate code to devcontainers org
  • Json schemas(s) (to enable a proposal PR to be in one repository) Publish devcontainer.json schema #14
• 🏃 Plan for community contributions Distribution proposal. #40
• Docs
  • Update docs or aka.ms links (i.e. for re-hosted devcontainer.json markdown in spec repo)
    • Add link from docs, aka.ms
  • More info on spec in existing docs (i.e. VS Code doc- already link to repo in Questions and feedback, but could use more context, link to reference implementation)
• Supporting tools and partners
  • 🏃 Communicate with interested parties
  • 🏃 Mention open spec in existing and future issues about alternate engines in vscode-remote-release

[bamurtaugh]

As these are largely tracked in other issues, and the spec and CLI are publicly available, closing out this issue.