Xen Orchestra and XCP-ng founder. Vates CEO and co-founder.
This is not just a powerful symbolic thing: by closing issue n°1, we are really reaffirming our independance and our capacity to build everything without using any binary provided by Citrix.
It's really a great news for XCP-ng's future!
https://github.com/xcp-ng/xcp/issues/1
Since last week, we have a new team member 
@ronan-a is now part of Vates XCP-ng team, with @stormi and myself.
@r1 and @johnelse are still with us as external contributors.
@ronan-a , feel free to introduce yourself here (and the stuff you are working on)
It's far from being complete, but it's a great first step in improving XCP-ng existing documentation and also visibility/credibility!
Everyone can still contribute (link on the bottom of each page), even if it's a bit more difficult than the wiki.
Let me know what you think about it
What about the wiki? We'll probably to continue to have very specific content there, and "promote" content to the doc if it "fits" for enough people.
https://xcp-ng.org/blog/2020/04/17/100-000-downloads-for-xcp-ng/
So you probably spotted the news, feel free to comment here 
To avoid splitting the community, we'll merge XO forum in this category. It seems not possible (or very not trivial) to fetch the previous XO threads here, so we'll probably have a transition time until we redirect directly XO forum URL toward this category directly.
Maybe it wasn't clear? French gov won't do anything in the project, they just support it as a research and dev project boosting innovation, and indirectly contributing to create more jobs that can't be replicated easily elsewhere.
There's no "control" on how we decide to do the R&D, as long as we put resources into it as we said.
XCP-ng is a free and community project, and everybody who want to contribute can do it. There's no "link" between us and any government.
So far we got 4 templates available:
Would you like other OS? Or even apps installed in those OS? Let us know!
Less yellowish terminal to use less different colors and keeping the variations in the logo:
For XCP-ng 8 we thought that it might be interesting to get a dedicated visual identity outside the boot splash: the prompt and the "ncurse" display.
rootNew vs old:
Obviously, we got a fallback for terminal without color support.
Also, it also works on white background terms:
New vs old:
There is also a fallback on terminals without color support (unchanged)
Maybe you could think it's a minor thing, but in the end, that's how we show XCP-ng is not just a clone of CH/XS
Obviously, you can still configure this easily (especially the prompt, because you can override it).
What do you think?
Untrue.
If XCP-ng doesn't work on top of some KVM installs, it doesn't mean Xen can't run in nested. In fact, it works: you can run XCP-ng on top of XCP-ng.
Xen is a bit different than KVM, so I'm not surprised there's bug when you have Xen on top of it. I don't know for the other way, it might be interesting to test.
And to fix your last statement: untrue too. XCP-ng on top of XCP-ng.
It would be interesting to report snapshots in this case that aren't related to a backup job (to avoid noise).
I know for the picture upload on the forum, but there's no trivial fix for now. I'll spend more time later.
Good to know about your XOA deploy thing solved
Hi!
Let me rephrase: in short, you'd like an improvement to the "usage report" plugin and get a section dedicated to snapshots older than X days? How long would be a good info in your opinion?
If your VBox can't have a working nested virtualization, it won't work.
XOA is a HVM guest, so you need HVM support in your XCP-ng.
Nested virt is complex, and there's not a lot of systems able to make it work.
Ping @julien-f who'll take a look when he can
And you still have the issue?
Do you have perf mode enabled in your BIOS? It's obviously not normal.
To get the complete speed, just take a look at XOA network stats while the backup is happening in… Xen Orchestra 
Hi,
Not supported just means Citrix won't have security fixes for those CPUs, simply because Intel isn't shipping microcode fixes anymore for those CPUs.