Repository navigation
doc: link the OpenVMM upstream roadmap from the documentation index - #478
Merged
Pedro Henrique Penna (ppenna) merged 1 commit intoOct 10, 2026
Merged
Conversation
doc/openvmm-upstream-roadmap.md was not linked from README.md or any other document, so readers could reach it only by browsing doc/. Index it in the README's Development list, and point to it from the contributing guide's OpenVMM source-change section, which now also states that nanvix/openvmm is a fork of microsoft/openvmm. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
Both links resolve correctly and accurately describe the roadmap.
0 open findings
What changed in this PR
Indexes the OpenVMM upstream roadmap so contributors can discover the fork’s upstreaming plan.
Changes:
- Adds the roadmap to the main documentation index.
- Links and explains it in the OpenVMM contribution guide.
| File | Description |
|---|---|
README.md |
Adds the roadmap to Development documentation. |
doc/contribute.md |
Documents the fork relationship and roadmap purpose. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Pedro Henrique Penna (ppenna)
deleted the
doc-sync/openvmm-roadmap-index
branch
October 10, 2026 16:21
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
doc/openvmm-upstream-roadmap.mdwas an orphan: no document linked to it, and the README's documentation index omitted it (it appeared only as plain text in thedoc/project-structure.mdtree). This PR indexes it from the README and points to it from the contributing guide's OpenVMM section, where contributors changing OpenVMM look for how the fork relates to upstream.Changes
README.md: add OpenVMM upstream roadmap to the Development list.rg openvmm-upstream-roadmap.md doc README.mdfound no Markdown link to the file before this change.doc/contribute.md(OpenVMM > Source changes): state thatnanvix/openvmmis a fork ofmicrosoft/openvmm, and that the roadmap groups the fork's microVM commits into planned upstream pull requests and marks fork-only ones.gh api repos/nanvix/openvmm --jq '.fork, .parent.full_name'returnstrue/microsoft/openvmm.NandFmark fork-only commits, and its PR graph and commit-to-PR mapping cover the microVM commits. Its fork basee1cdbd916is an ancestor of the pinned revision, 305 commits back (166 mapped + 139 after the mapped tip, matching the roadmap's Scope).No design chapter changed. For reference, the pinned OpenVMM revision is
7bf0ee28b826374a2d386067df0456b81bcae818.The roadmap file itself is touched by open PR #475, so this PR leaves it alone and only adds links to it.
Follow-ups
scripts/setup/README.mdis a guide outsidedoc/.scripts/test_tool_versions.pyreads it in place, andscripts/setup/tool-versions.confrefers to it as the README next to the scripts, so moving it would need code and test changes. I left it in place.unittest_results.txtis tracked at the repository root and looks like an accidentally committed test log. It's not Markdown, so it's out of scope here.python scripts/nvx.py --helpstill describesinitas "initialize the private submodule", but the OpenVMM submodule is public (seedoc/contribute.md#access). This is a code help string, so I'm reporting it rather than changing it.doc/design/time-abi.mdis about 170 KB, far longer than the other chapters. It's touched by open PRs test-microvm: pause and resume a microVM through OpenVMM state control #405 and Adopt bind-once microVM image slots #406, so I left it alone.Validation
python -m unittest scripts.test_nvx_tools.CliTests scripts.test_performance.PerformanceTests: Ran 110 tests, OK (skipped=1).doc/design.mdlinks every chapter indoc/design/. Result: OK.git diff --check: clean.python scripts/nvx.py verify: source tree and submodule metadata are consistent.^(doc/|.*\.md$), so CI treats this PR as documentation-only.