diff --git a/web/config/_default/menus/menus.en.toml b/web/config/_default/menus/menus.en.toml index ad5f66e93..11f088168 100644 --- a/web/config/_default/menus/menus.en.toml +++ b/web/config/_default/menus/menus.en.toml @@ -39,10 +39,10 @@ # url = "/docs/1.0/prologue/introduction/" weight = 20 -# [[main]] -# name = "Blog" -# url = "/blog/" -# weight = 30 +[[main]] + name = "Blog" + url = "/blog/" + weight = 30 [[main]] name = "Contact" diff --git a/web/content/blog/2025-03-16-intro/index.md b/web/content/blog/2025-03-16-intro/index.md new file mode 100644 index 000000000..b7348e05d --- /dev/null +++ b/web/content/blog/2025-03-16-intro/index.md @@ -0,0 +1,71 @@ +--- +title: "Announcing Snix" +description: "Announcing the Snix Project" +date: 2025-03-16T15:32:28+00:00 +lastmod: 2025-03-16T15:32:28+00:00 +draft: false +weight: 50 +categories: [] +tags: [] +contributors: [] +pinned: false +homepage: false +--- + +## A New Chapter + +For a long time now, Tvix development has been a bit of a tug-of-war between +differing priorities. The TVL community's side project, or Tvix as an end in its +own right. The evaluator front and center, or castore as the major innovation. +The repository itself, the contributor onboarding flow, and even the choice of +IRC channel have laboured under these conflicting views of Tvix's future. + +Snix is where we're hoping to put this to a rest, on infrastructure and +community dedicated to driving an innovative implementation of Nix forward. + +## Background + +While initially being homed in the TVL community, for a while now already, +most Tvix development has been going on in a separate `#tvix-dev` IRC +channel, with little overlap with TVL. + +Onboarding new contributors was hard in general: + - Newcomers had to clone the entire monorepo to contribute, bringing in a lot + of unrelated projects, that are confusing at best. + - Having all these projects made navigation hard, and changing some things in + one place caused regressions far away in another corner of the repository. + - Onboarding frequently required sending patches via email, as the SSO login + process was somewhat neglected. + +There's been different requirements on CI for Tvix and TVL: + - TVL overrides Nix to their 2.3 fork in their nixpkgs instance, which + frequently causes rebuilds for contributors, caused CI deadlocks in the + past, and most recently an entirely broken build for all contributors on + MacOS. + - Tvix has an extensive regression test suite, and nixpkgs bumps regularly + caused them to fail, requiring investigation. However, as some peoples' + system configurations are also in the monorepo, and they have an interest + in getting nixpkgs updates quickly, causing Tvix tests to frequently get + disabled, risking breakage of Tvix functionality. + +There have also been a few disagreements on which areas of Tvix development +should be prioritized, and how certain things should be architected. + +# Snix + +Rather than continuing to navigate all these conflicting priorities, and +spending lots of time coming up with a compromise both sides are not really +happy about, I think it's better to put the project on its own legs, not only +in terms of community, but also in terms of where it's hosted, using a new name, +**Snix**. + +The fork will: + + - allow tailoring the surrounding build infrastructure to the needs of Snix + - make contributions easier, allowing for a broader contributor base + - unblock some long-deadlocked decisions on the future of Tvix development + +We're excited to work with new and existing contributors to Tvix and other Nix +implementations to drive a modular approach to Nix infrastructure forwards. + +Find us at [Contact]({{< ref "/contact" >}}) diff --git a/web/website/content/blog/example/index.md b/web/website/content/blog/example/index.md deleted file mode 100644 index 6f1d49392..000000000 --- a/web/website/content/blog/example/index.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: "Example Post" -description: "Just an example post." -summary: "You can use blog posts for announcing product updates and features." -date: 2023-09-07T16:27:22+02:00 -lastmod: 2023-09-07T16:27:22+02:00 -draft: true -weight: 50 -categories: [] -tags: [] -contributors: [] -pinned: false -homepage: false -seo: - title: "" # custom title (optional) - description: "" # custom description (recommended) - canonical: "" # custom canonical URL (optional) - robots: "" # custom robot tags (optional) ---- - -Well-thought-through product announcements will help increase feature awareness and engage users with new functionality. Just like [sharing your public roadmap](https://canny.io/blog/should-you-have-a-public-roadmap/), it's also a great way to let potential customers see that you're constantly improving. - -## Further reading - -- Read [How to announce product updates and features](https://canny.io/blog/announce-product-updates-features/)