On Jun 8, 2025, at 5:49 AM, Christopher Clark <christopher.w.clark@xxxxxxxxx> wrote:
I think this should be dropped. We don't need a link to a design
document without an implementation. You can add it once you've
upstreamed the implementation.
OK, I'll remove this section for the next version of the series.
What's the recommended location of Xen design documents, requirements for future improvements, roadmaps or pointers to related work in adjacent open-source communities? The Xen wiki is being deprecated.
What's the recommended way for the Xen community to discover the existence of Argo documentation that is not hosted by the Xen community? If necessary, we can create a new semantic label or Xen docs directory tree, to host technical content that might otherwise be lost.
Should we add a sentence to Xen's Argo documentation, to the effect of "Please refer to the Xen [wiki in archive.org, website, mailing list], external sites [A, B, C, D], or your preferred [search engine, LLM] for more technical documents on Argo design and implementation"?
Rich |
