In reply to @tomberek:matrix.org
Thanks for putting it together. What prompted it?

In reply to @0x4a6f:matrix.org

Since 24.11, the Xen Project now has its own functioning options, available under the virtualisation.xen.* option set.

There seems to be a further history of this option set down the history lane of that other repo:

commit 5c1f8cbc70cd5e6867ef6a2a06d27a40daa07010
Author: Eelco Dolstra <eelco.dolstra@logicblox.com>
Date:   Thu Oct 10 13:28:20 2013 +0200

    Move all of NixOS to nixos/ in preparation of the repository merge

diff --git a/nixos/modules/virtualisation/xen-dom0.nix b/nixos/modules/virtualisation/xen-dom0.nix

In reply to @0x4a6f:matrix.org

Since 24.11, the Xen Project now has its own functioning options, available under the virtualisation.xen.* option set.

There seems to be a further history of this option set down the history lane of that other repo:

commit 5c1f8cbc70cd5e6867ef6a2a06d27a40daa07010
Author: Eelco Dolstra <eelco.dolstra@logicblox.com>
Date:   Thu Oct 10 13:28:20 2013 +0200

    Move all of NixOS to nixos/ in preparation of the repository merge

diff --git a/nixos/modules/virtualisation/xen-dom0.nix b/nixos/modules/virtualisation/xen-dom0.nix

In reply to @tomberek:matrix.org
Something about this sentence doesn't parse right as I read it.

> The Xen maintenance team recommends Xen because it provides exciting new opportunities to discover circular vendored build dependencies that normal software is incapable of providing, and also to anyone looking for:

In reply to @tomberek:matrix.org
Overall, yes. Once you're happy with the article, it is a good thing to put out. Do they also have some article about Nix/NixOS?

In reply to @sigmasquadron:matrix.org
As far as I'm aware, they don't use NixOS, so no. Maybe we can change that in the future!

Hi!

I was redirected here to discuss things. I've made some PRs, some merged, some stalled, some pending, some closed. I'm happy to follow process, but I'd also like to be able to productively use my time and Github issues seems like a perfectly reasonable way of working out in the open (and discoverability for Matrix is suboptimal for discussion and decisonmaking when compared with forge tooling).

The PRs in question I'd like feedback on on pushing forward:

• https://github.com/NixOS/nixos-homepage/pull/1587 -- This one is about closing 1511, a pretty straightforward request by somebody ( fricklerhandwerk I think?) to start debloating the community page.
• https://github.com/NixOS/nixos-homepage/pull/1573 -- This one is about trying to figure out how to make security front-and-center on the site as something the NixOS distribution cares about. Currently, it's kinda buried in the community security team page--and working on this has shown that the email alias for security@nixos.org seems to be either busted or have spotty connectivity to the folks on the security team (based on testing). The thing here is that I don't actually know what the security policy should be (though I have guesses) and I'm trying to avoid telling the security folks how to do their job. I was kinda hoping we could workshop the PR and get to a good place with stakeholders (as has happened successfully with, for example, the extensive work on the immich PR).

Thanks!

There's another philosophical question which is: would it be a good idea to put security right on the navbar? My personal bet is yes, because:

• there was a semi-high-profile kerfluffle earlier this year and not having an obvious single touchpoint seems to have hurt there.
• more generally (outside of internal NixOS stuff), one of the hugely useful things about using NixOS is supply chain integrity and other things of interest to security-conscious users.

there was a semi-high-profile kerfluffle earlier this year and not having an obvious single touchpoint seems to have hurt there.

Uh … what?