Compare commits
1 commit
main
...
trailing-s
| Author | SHA1 | Date | |
|---|---|---|---|
 Rebecca Turner
|
69ec60125b
|
4
TODO.md
4
TODO.md
|
|
@ -17,9 +17,9 @@ TODO List
|
|||
- Create `/roadmap`.
|
||||
- Create '/usability'.
|
||||
- Create `/infrastructure`.
|
||||
|
||||
|
||||
### Graphics
|
||||
|
||||
|
||||
- Add nice images to the "/about" page.
|
||||
- Replace the primary "hero" graphic with a Lix one.
|
||||
- Monocolor the social media icons and then apply the color filter.
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ summaryLength: 20
|
|||
params:
|
||||
title: "Lix"
|
||||
description: "Lix is an independent variant of the Nix package manager, developed by a team of open-source volunteers, and maintained by and for a passionate community of users."
|
||||
images:
|
||||
images:
|
||||
- "images/hero-image.png"
|
||||
|
||||
logo: "lix_logo.png"
|
||||
|
|
|
|||
|
|
@ -7,20 +7,20 @@ author: "Lix Team"
|
|||
|
||||
**Lix** is an implementation of the Nix _functional package management_ language. Originally
|
||||
codified by [CppNix](https://github.com/NixOS/nix/), the Nix language allows you to create
|
||||
packages that can be used for anything from **putting configuration files into place** to
|
||||
**declaratively managing an entire system**.
|
||||
packages that can be used for anything from **putting configuration files into place** to
|
||||
**declaratively managing an entire system**.
|
||||
|
||||
That means that, with a few well-written Nix expressions, one
|
||||
That means that, with a few well-written Nix expressions, one
|
||||
can easily configure a system into a known state -- and the packages that are created this
|
||||
way are guaranteed to run _exactly the same way_ on any system of the same architecture.
|
||||
|
||||
As a fork of CppNix, Lix is designed to be fully compatible with the original CppNix
|
||||
As a fork of CppNix, Lix is designed to be fully compatible with the original CppNix
|
||||
implementation -- but also designed to allow evolution of the language and tooling, so
|
||||
its developers can improve usability and ergonomics without sacrificing correctness.
|
||||
|
||||
### Why use Nix?
|
||||
|
||||
If you're not familiar with the Nix approach, we recommend checking out some of the
|
||||
If you're not familiar with the Nix approach, we recommend checking out some of the
|
||||
[writing on the subject](https://nixos.org/guides/nix-pills/01-why-you-should-give-it-a-try.html).
|
||||
|
||||
|
||||
|
|
@ -30,39 +30,39 @@ The **Nix language** is used for a variety of applications ranging from individu
|
|||
to clusters of critical infrastructure. With this in mind, the Lix team has been working to
|
||||
provide a collection of necessary improvements over CppNix:
|
||||
|
||||
- **Built for a community, not for a corporation.**
|
||||
Lix is built by a team of open-source volunteers -- and exists to provide an alternative to the
|
||||
- **Built for a community, not for a corporation.** <br>
|
||||
Lix is built by a team of open-source volunteers -- and exists to provide a alternative to the
|
||||
commercial interests that have long plagued both upstream CppNix and corporate-authored forks.
|
||||
We're proud to stand by our open [conflict of interest statements](/team#conflict-of-interest-statements),
|
||||
and proud to listen to community voices on issues of sponsorship, direction, and moderation.
|
||||
|
||||
- **A safe community for developers of all backgrounds.**
|
||||
- **A safe community for developers of all backgrounds.** <br>
|
||||
Lix is developed by a diverse group of users -- and accordingly is committed to providing a
|
||||
space that's safe for users and developers typically underrepresented in technical projects.
|
||||
We take moderation seriously, and are committed to preventing bad actors from driving out
|
||||
We take moderation seriously, and are committed to preventing bad actors from driving out
|
||||
marginalized groups.
|
||||
|
||||
- **A correct implementation of the Nix language.**
|
||||
- **A correct implementation of the Nix language.** <br>
|
||||
Recent versions of the CppNix project have introduced significant regressions -- so much so
|
||||
that the upstream [Nixpkgs](https://github.com/nixos/nixpkgs) team has opted to remain several
|
||||
versions behind. Lix is forked from the last truly-stable version of CppNix -- but has both
|
||||
introduced new features and backported a number of features from newer versions without
|
||||
sacrificing correctness.
|
||||
|
||||
- **A more modern implementation of Nix.**
|
||||
Lix is designed for evolution of its codebase. Lix already uses the more modern
|
||||
[meson build system](https://mesonbuild.com/), which improves developer usability and decreases build times.
|
||||
- **A more modern implementation of Nix.** <br>
|
||||
Lix is designed for evolution of its codebase. Lix already uses the more modern
|
||||
[meson build system](https://mesonbuild.com/), which improves developer usability and decreases build times.
|
||||
Plans include a gradual, piecewise introduction of the memory-safe [Rust](https://www.rust-lang.org/)
|
||||
programming language -- to both supplement and replace sections of the current C++ codebase.
|
||||
programming language -- to both supplement and replace sections of the current C++ codebase.
|
||||
|
||||
- **A language with room to grow.**
|
||||
- **A language with room to grow.** <br>
|
||||
Unlike upstream Nix, Lix intends to be an evolving language -- a robust language versioning
|
||||
system will allow the language to grow and evolve without sacrificing backwards-compatibility or correctness.
|
||||
And room to grow means room for **usability and ergonomics improvements** -- both in the language and in
|
||||
And room to grow means room for **usability and ergonomics improvements** -- both in the langauge and in
|
||||
tooling.
|
||||
|
||||
<br>
|
||||
|
||||
## Community, Team & Governance
|
||||
|
||||
**Looking for information about the people behind the project?**
|
||||
Check out our [community](/community) and [team](/team) pages.
|
||||
**Looking for information about the people behind the project?** <br>
|
||||
Check out our [community](/community) and [team](/team) pages.
|
||||
|
|
|
|||
|
|
@ -1,58 +1,13 @@
|
|||
---
|
||||
title: "Switching To Lix"
|
||||
description: "or: how to make your existing configuration Delicious"
|
||||
description: "or: how to make your existing configruation Delicious"
|
||||
date: "2024-04-27"
|
||||
author: "Lix Team"
|
||||
---
|
||||
|
||||
If you have an existing configuration on **NixOS** or **nix-darwin**, there are
|
||||
a couple of ways to switch to Lix, all of which are relatively easy.
|
||||
|
||||
- Using Lix from nixpkgs:
|
||||
- Potentially slightly older version of Lix
|
||||
- Working binary caching
|
||||
- Programs like nix-eval-jobs and colmena still use the default version of
|
||||
Nix (may be unacceptable depending on your use case)
|
||||
- Using the Lix NixOS module:
|
||||
- Fresh version of Lix right out of the freezer
|
||||
- You will be compiling Lix yourself, for now at least
|
||||
- Programs like nix-eval-jobs and colmena have the version of Nix they use
|
||||
overridden by an overlay such that most of the system uses Lix.
|
||||
|
||||
# Using Lix from nixpkgs
|
||||
|
||||
This approach has some caveats: since it is not using an overlay, it does not
|
||||
set the version of Nix depended on by other tools like colmena or
|
||||
nix-eval-jobs. Consequently, those tools will be using whichever version of
|
||||
CppNix is default in nixpkgs, likely leading to an inconsistent experience. It
|
||||
is, however, easy, and it does not take the few minutes to compile Lix from
|
||||
source.
|
||||
|
||||
Add the following code to your NixOS configuration:
|
||||
|
||||
```nix
|
||||
{ pkgs, ... }:
|
||||
{
|
||||
nix.package = pkgs.lix;
|
||||
}
|
||||
```
|
||||
|
||||
That's it, you're done.
|
||||
|
||||
You can verify that it works by running the following command:
|
||||
|
||||
```sh
|
||||
$ nix --version
|
||||
nix (Lix, like Nix) 2.90.0-rc1
|
||||
```
|
||||
|
||||
# Using the Lix NixOS module
|
||||
|
||||
The Lix NixOS module is the way to get the most consistent experience using
|
||||
Lix, and to have a system that has Lix as the default Nix implementation
|
||||
wherever possible by using an overlay to replace `pkgs.nix`. It will result in
|
||||
building Lix from source, which takes a few minutes on every update, which is a
|
||||
perfect time to get up, get some water, and stretch for a bit.
|
||||
If you have an existing configuration on **NixOS** or **nix-darwin**, the easiest way
|
||||
to switch to Lix is currently by using our provided _NixOS module_. Fortunately, this
|
||||
usually means adding only a couple of lines to your configuration.
|
||||
|
||||
## Flake-based Configurations
|
||||
|
||||
|
|
@ -67,8 +22,13 @@ Adding Lix to a flake-based configuration is relatively simple. First, add the L
|
|||
# Note that this assumes you have a flake-input called nixpkgs,
|
||||
# which is often the case. If you've named it something else,
|
||||
# you'll need to change the `nixpkgs` below.
|
||||
lix = {
|
||||
url = "git+https://git@git.lix.systems/lix-project/lix?ref=refs/tags/2.90-beta.1";
|
||||
flake = false;
|
||||
};
|
||||
lix-module = {
|
||||
url = "https://git.lix.systems/lix-project/nixos-module/archive/2.90.0-rc1.tar.gz";
|
||||
url = "git+https://git.lix.systems/lix-project/nixos-module";
|
||||
inputs.lix.follows = "lix";
|
||||
inputs.nixpkgs.follows = "nixpkgs";
|
||||
};
|
||||
|
||||
|
|
@ -118,17 +78,12 @@ Add the Lix _NixOS Module_ to your configuration:
|
|||
}
|
||||
```
|
||||
|
||||
<!--
|
||||
FIXME: the binary cache doesn't do much good given that everyone is running a
|
||||
different nixpkgs than Lix is actually cached with during the release process.
|
||||
We need a hydra to be able to fix that.
|
||||
|
||||
Finally, if you'd prefer not to build Lix yourself, you can add our binary cache.
|
||||
Add the following to any NixOS module in your configuration (e.g. `configuration.nix`):
|
||||
|
||||
```nix
|
||||
{
|
||||
nix.settings.substituters = [
|
||||
nix.settings.extra-substituters = [
|
||||
"https://cache.lix.systems"
|
||||
];
|
||||
|
||||
|
|
@ -138,14 +93,12 @@ Add the following to any NixOS module in your configuration (e.g. `configuration
|
|||
}
|
||||
```
|
||||
|
||||
-->
|
||||
|
||||
Rebuild and switch into your new system (either using `nixos-rebuild` or `darwin-rebuild`).
|
||||
You should now be using Lix! You can verify this by asking the `nix` command to report its version:
|
||||
|
||||
```sh
|
||||
$ nix --version
|
||||
nix (Lix, like Nix) 2.90.0-rc1
|
||||
nix (Lix, like Nix) 2.90.0-beta.0
|
||||
```
|
||||
|
||||
As long as you see `Lix` in the output, you're good! If you're not sure what to do now, it's a
|
||||
|
|
@ -160,6 +113,12 @@ Lix release tarball, and then add it to your `configuration.nix`.
|
|||
Open your `/etc/nixos/configuration.nix` in the editor of your choice. Find the `imports`
|
||||
section, and add the line provided in the configuration
|
||||
|
||||
<mark>
|
||||
<b>This section is currently pending on a quick update.</b>
|
||||
</mark>
|
||||
<br/>
|
||||
<br/>
|
||||
|
||||
```nix
|
||||
{ config, lib, pkgs, ... }:
|
||||
{
|
||||
|
|
@ -167,30 +126,20 @@ section, and add the line provided in the configuration
|
|||
[ # Include the results of the hardware scan.
|
||||
./hardware-configuration.nix
|
||||
|
||||
# This includes the Lix NixOS module in your configuration along with the
|
||||
# matching version of Lix itself.
|
||||
#
|
||||
# The sha256 hashes were obtained with the following command in Lix (n.b.
|
||||
# this relies on --unpack, which is only in Lix and CppNix > 2.18):
|
||||
# nix store prefetch-file --name source --unpack https://git.lix.systems/lix-project/lix/archive/2.90.0-rc1.tar.gz
|
||||
# This is the core line -- it pulls down the Lix module and
|
||||
# includes it in your configuration. It looks much nicer with a let
|
||||
# binding -- but for clarity, we'll leave that as an exercise for the
|
||||
# reader. :)
|
||||
#
|
||||
# Note that the tag (e.g. v2.90) in the URL here is what determines
|
||||
# which version of Lix you'll wind up with.
|
||||
(let
|
||||
module = fetchTarball {
|
||||
name = "source";
|
||||
url = "https://git.lix.systems/lix-project/nixos-module/archive/2.90.0-rc1.tar.gz";
|
||||
sha256 = "sha256-64lB/NO6AQ6z6EDCemPSYZWX/Qc6Rt04cPia5T5v01g=";
|
||||
};
|
||||
lixSrc = fetchTarball {
|
||||
name = "source";
|
||||
url = "https://git.lix.systems/lix-project/lix/archive/2.90.0-rc1.tar.gz";
|
||||
sha256 = "sha256-WY7BGnu5PnbK4O8cKKv9kvxwzZIGbIQUQLGPHFXitI0=";
|
||||
};
|
||||
# This is the core of the code you need; it is an exercise to the
|
||||
# reader to write the sources in a nicer way, or by using npins or
|
||||
# similar pinning tools.
|
||||
in import "${module}/module.nix" { lix = lixSrc; }
|
||||
(import
|
||||
(
|
||||
(fetchTarball { url = "https://git.lix.systems/lix-project/nixos-module/archive/main.tar.gz"; }) + "/module.nix"
|
||||
)
|
||||
{
|
||||
lix = fetchTarball { url = "https://git.lix.systems/lix-project/lix/archive/2.90-beta.1.tar.gz"; };
|
||||
}
|
||||
)
|
||||
];
|
||||
|
||||
|
|
@ -198,15 +147,12 @@ section, and add the line provided in the configuration
|
|||
}
|
||||
```
|
||||
|
||||
<!--
|
||||
FIXME: as above, doesn't work, we should not recommend it.
|
||||
|
||||
Finally, if you'd prefer not to build Lix yourself, you can add our binary cache.
|
||||
Add the following to any NixOS module in your configuration (e.g. `configuration.nix`):
|
||||
|
||||
```nix
|
||||
{
|
||||
nix.settings.substituters = [
|
||||
nix.settings.extra-substituters = [
|
||||
"https://cache.lix.systems"
|
||||
];
|
||||
|
||||
|
|
@ -215,14 +161,13 @@ Add the following to any NixOS module in your configuration (e.g. `configuration
|
|||
];
|
||||
}
|
||||
```
|
||||
-->
|
||||
|
||||
Rebuild and switch into your new system (either using `nixos-rebuild` or `darwin-rebuild`).
|
||||
You should now be using Lix! You can verify this by asking the `nix` command to report its version:
|
||||
|
||||
```sh
|
||||
$ nix --version
|
||||
nix (Lix, like Nix) 2.90.0-rc1-lixpre20240615-253546d
|
||||
nix (Lix, like Nix) 2.90.0-beta.0
|
||||
```
|
||||
|
||||
As long as you see `Lix` in the output, you're good! If you're not sure what to do now, it's a
|
||||
|
|
@ -230,7 +175,7 @@ great time to check out some of the [community's resources on Nix](/resources).
|
|||
|
||||
## Having Trouble?
|
||||
|
||||
**One quick thing to check:** have you set `nix.package` anywhere in your configuration?
|
||||
**One quick thing to check:** have you set `nix.package` anywhere in your configuration? <br>
|
||||
If so, your configuration option will override the Lix module. You'll want to remove it, first --
|
||||
or, if you're feeling savvy, point it to the provided Lix package.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: "Community Standards"
|
||||
description: "making Lix a safe and productive environment <3"
|
||||
date: "2024-05-14"
|
||||
date: "2024-04-27"
|
||||
author: "Lix Team"
|
||||
---
|
||||
|
||||
|
|
@ -15,7 +15,7 @@ The following are *principles* and do not in any way limit the authority of the
|
|||
- We want to avoid creating unnecessary social hierarchy and avoid unaccountable positions in the project.
|
||||
- These expectations apply to everyone in the project including the core team and the interim community team.
|
||||
- The Lix community is significantly comprised of people of various marginalised backgrounds. We are committed to protecting these people and providing a safe environment for them.
|
||||
- If you are of a less-marginalised background, keep in mind that you are a guest in our spaces but are nonetheless welcome. Think of it like staying at a friend's place where they might have different cultural customs; you may have to do things a little bit differently.
|
||||
- If you are of a less-marginalised background, keep in mind that you are a guest in our spaces and although you are welcome, you are nonetheless a guest.
|
||||
- We want to build leadership in community members and help them grow.
|
||||
- Technology is neither neutral nor apolitical. We consider how decisions affect different groups of people, and how they may create power dynamics or other consequences.
|
||||
- Impact is more important than intent.
|
||||
|
|
@ -44,9 +44,8 @@ We encourage working through conflicts privately with involved parties, but we a
|
|||
|
||||
If you wish to contact a member of the interim community team about a concern, consider contacting one of the following people:
|
||||
|
||||
- qyriad (@qyriad:katesiria.org)
|
||||
- piegames (@piegames:flausch.social)
|
||||
- ktemkin (@ktemkin:katesiria.org)
|
||||
- hexchen (@hexchen:colon.at)
|
||||
- lunaphied (@lunaphied:lunaphied.me)
|
||||
- jade (@jade_:matrix.org)
|
||||
- qyriad (@qyriad:katesiria.org)
|
||||
- hexchen (@hexchen:colon.at)
|
||||
- lunaphied (@lunaphied:lunaphied.me)
|
||||
|
|
@ -30,7 +30,7 @@ governance.
|
|||
|
||||
## Engaging with the Community
|
||||
|
||||
The best way to engage with the community currently is to **join our Matrix space** -- a decentralized
|
||||
The best way to engage with the community currently is to **join our Matrix space** -- a decentralized
|
||||
chat platform commonly used among open-source projects.
|
||||
|
||||
### Lix Matrix
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ extension system for the tooling -- which will allow technologies like flakes, a
|
|||
extensions -- to seamlessly act with the Lix core without needing to reside long-term in the Lix tree.
|
||||
|
||||
_Flakes are not the only way to write Nix language code in Lix, and we intend to provide a good experience
|
||||
to those using flakes -- while also improving the experience for those not using them --
|
||||
to those using flakes -- while also improving the experience for those not using them --
|
||||
by evolving a compatible but more flexible flake-like abstraction in the periphery of the Lix system._
|
||||
|
||||
|
||||
|
|
@ -55,11 +55,11 @@ compiling lists of resources, web design, bug tracker triage, and more. If you'r
|
|||
to get started on, we have triaged some tasks
|
||||
[that we believe should be straightforward](https://git.lix.systems/lix-project/lix/issues?q=&type=all&sort=&state=open&labels=157&milestone=0&project=0&assignee=0&poster=0). To read more
|
||||
about which tasks we recommend taking on, see
|
||||
[Freezes and recommended contributions](https://wiki.lix.systems/link/9).
|
||||
[Freezes and recommended contributions](https://git.lix.systems/lix-project/lix/src/branch/main/CONTRIBUTING.md).
|
||||
|
||||
Feel free to ask for help in the Lix development channel. Especially feel free to ask for us to write down
|
||||
more work that we would like help with, or to write contribution information that is missing;
|
||||
it is a goal of the project for it to be easy to get up to speed. Also, if you need additional access to
|
||||
Feel free to ask for help in the Lix development channel. Especially feel free to ask for us to write down
|
||||
more work that we would like help with, or to write contribution information that is missing;
|
||||
it is a goal of the project for it to be easy to get up to speed. Also, if you need additional access to
|
||||
do some task, such as fixing a typo in the wiki, let us know and we will figure it out.
|
||||
|
||||
#### Q: How do I submit changes to the Lix project?
|
||||
|
|
@ -80,9 +80,9 @@ it commit-by-commit.
|
|||
Lix has a central accounts system for all its services. These accounts allow access to Forgejo (the Lix bug tracker
|
||||
and repositories), Gerrit Code Review, the wiki and other collaboration software we use.
|
||||
|
||||
To get started contributing to Lix, you need a Lix account. The easiest way to obtain one is to use GitHub
|
||||
To get started contributing to Lix, you need a Lix account. The easiest way to obtain one is to use GitHub
|
||||
for login, as it will let you get started immediately. We also have local accounts available for those who
|
||||
wish not to use GitHub; if you would like one, please speak to a member of the Lix team on Matrix and we
|
||||
wish not to use GitHub; if you would like one, please speak to a member of the Lix team on Matrix and we
|
||||
will gladly make you one manually.
|
||||
|
||||
#### Q: If Lix plans to adopt Rust, what makes it different from Tvix?
|
||||
|
|
|
|||
|
|
@ -20,11 +20,13 @@ first, to get familiar with how Nix works.
|
|||
|
||||
If you haven't already installed NixOS, do so using any upstream
|
||||
[install image](https://nixos.org/download/#NixOS) and the instructions in the
|
||||
[NixOS Manual](https://nixos.org/manual/nixos/stable/#sec-installation).
|
||||
[NixOS Manual](https://nixos.org/manual/nixos/stable/#sec-installation). Then, follow
|
||||
the instructions for either:
|
||||
|
||||
Then, follow the [instructions to add Lix to your
|
||||
configuration](/add-to-config). Both flake-based and non-flake-based
|
||||
configurations are fully supported.
|
||||
- [flake-based configurations](/add-to-config#flake-based-configurations); or
|
||||
- [non-flake configurations](/add-to-config#non-flake-configurations)
|
||||
|
||||
depending on how you prefer to configure your system.
|
||||
|
||||
|
||||
## On an Existing `nix-darwin` Install
|
||||
|
|
@ -67,12 +69,12 @@ of the `upgrade-nix` command.
|
|||
Thanks to Nix, we can actually ask Lix to upgrade your system directly. Run the following command:
|
||||
|
||||
```sh
|
||||
sudo --preserve-env=PATH nix run \
|
||||
sudo nix run \
|
||||
--experimental-features "nix-command flakes" \
|
||||
--extra-substituters https://cache.lix.systems --extra-trusted-public-keys "cache.lix.systems:aBnZUw8zA7H35Cz2RyKFVs3H4PlGTLawyY5KRbvJR8o=" \
|
||||
'git+https://git@git.lix.systems/lix-project/lix?ref=refs/tags/2.90.0-rc1' -- \
|
||||
upgrade-nix \
|
||||
--extra-substituters https://cache.lix.systems --extra-trusted-public-keys "cache.lix.systems:aBnZUw8zA7H35Cz2RyKFVs3H4PlGTLawyY5KRbvJR8o="
|
||||
--extra-substituters https://cache.lix.systems \
|
||||
--trusted-public-keys "cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY= cache.lix.systems:aBnZUw8zA7H35Cz2RyKFVs3H4PlGTLawyY5KRbvJR8o=" \
|
||||
'git+https://git@git.lix.systems/lix-project/lix?ref=refs/tags/2.90-beta.0' -- \
|
||||
upgrade-nix
|
||||
```
|
||||
|
||||
You should now have upgraded to Lix! You can verify this by asking the `nix` command
|
||||
|
|
@ -80,7 +82,7 @@ to report its version:
|
|||
|
||||
```sh
|
||||
$ nix --version
|
||||
nix (Lix, like Nix) 2.90.0-rc1-lixpre20240615-253546d
|
||||
nix (Lix, like Nix) 2.90.0-beta.1
|
||||
```
|
||||
|
||||
As long as you see `Lix` in the output, you're good! If you're not sure what to do now, it's a
|
||||
|
|
@ -94,4 +96,4 @@ If you're having difficulty installing Lix, don't panic! Hop on over to our
|
|||
## Feedback?
|
||||
|
||||
If you have thoughts on these instructions, feel free to drop by our [community](/community),
|
||||
or to [make a pull request to our website](https://git.lix.systems/lix-project/lix-website/pulls)!
|
||||
or to [make a pull request to our website](git@git.lix.systems:lix-project/lix-website.git)!
|
||||
|
|
|
|||
|
|
@ -8,9 +8,9 @@ tags = [
|
|||
]
|
||||
+++
|
||||
|
||||
Emoji can be enabled in a Hugo project in a number of ways.
|
||||
Emoji can be enabled in a Hugo project in a number of ways.
|
||||
<!--more-->
|
||||
The [`emojify`](https://gohugo.io/functions/emojify/) function can be called directly in templates or [Inline Shortcodes](https://gohugo.io/templates/shortcode-templates/#inline-shortcodes).
|
||||
The [`emojify`](https://gohugo.io/functions/emojify/) function can be called directly in templates or [Inline Shortcodes](https://gohugo.io/templates/shortcode-templates/#inline-shortcodes).
|
||||
|
||||
To enable emoji globally, set `enableEmoji` to `true` in your site's [configuration](https://gohugo.io/getting-started/configuration/) and then you can type emoji shorthand codes directly in content files; e.g.
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ In this example we will be using [KaTeX](https://katex.org/)
|
|||
|
||||
- Create a partial under `/layouts/partials/math.html`
|
||||
- Within this partial reference the [Auto-render Extension](https://katex.org/docs/autorender.html) or host these scripts locally.
|
||||
- Include the partial in your templates like so:
|
||||
- Include the partial in your templates like so: <br>
|
||||
|
||||
```bash
|
||||
{{ if or .Params.math .Site.Params.math }}
|
||||
|
|
@ -45,5 +45,5 @@ Inline math: \(\varphi = \dfrac{1+\sqrt5}{2}= 1.6180339887…\)
|
|||
|
||||
Block math:
|
||||
$$
|
||||
\varphi = 1+\frac{1} {1+\frac{1} {1+\frac{1} {1+\cdots} } }
|
||||
\varphi = 1+\frac{1} {1+\frac{1} {1+\frac{1} {1+\cdots} } }
|
||||
$$
|
||||
|
|
|
|||
|
|
@ -12,15 +12,6 @@ of the community.
|
|||
We're also currently in the process of writing brand new documentation, which will be listed here
|
||||
once available.
|
||||
|
||||
## A note of caution
|
||||
|
||||
Nix has a long history. Some things that seemed like good ideas once are no longer common practice. In particular:
|
||||
|
||||
- It's probably a good idea to ignore `nix-env` and mutable environments in favor of declarative configuration
|
||||
- If you don't already use channels, it's probably a good idea to learn about flakes or some other pinning mechanism instead
|
||||
|
||||
If you're learning about those topics because you want to understand the ideas that are currently in favor in the historical contexts they are responses to, or because you think you see a benefit to them that others don't, that's totally fine; this warning is only here to help beginners have a fruitful experience.
|
||||
|
||||
## Understanding Nix
|
||||
|
||||
- [The official Nix ecosystem documentation](https://nix.dev), maintained by the **NixOS Foundation**.
|
||||
|
|
|
|||
|
|
@ -17,41 +17,40 @@ tasks is to establish a lasting governance model -- and other teams to handle th
|
|||
|
||||
Members (in alphabetical order):
|
||||
|
||||
- **hexchen ([@hexchen](https://github.com/hexchen), she/her)**
|
||||
- **hexchen ([@hexchen](https://github.com/hexchen), she/her)** <br>
|
||||
hexchen is working primarily on maintaining and extending the Lix project infrastructure.
|
||||
|
||||
- **Irenes ([@IreneKnapp](https://github.com/IreneKnapp), they/them)**
|
||||
- **Irenes ([@IreneKnapp](https://github.com/IreneKnapp), they/them)** <br>
|
||||
Irenes are an outside-context problem. They are fond of cats.
|
||||
|
||||
- **jade ([@lf-](https://github.com/lf-), they/them)**
|
||||
jade is working on packaging, testing, infrastructure, tooling, review, stability, and a large amount of
|
||||
- **jade ([@lf-](https://github.com/lf-), they/them)** <br>
|
||||
jade is working on packaging, testing, infrastructure, tooling, review, stability, and a large amount of
|
||||
the writing in Lix. They recently graduated from a Computer Engineering program at UBC in Canada.
|
||||
|
||||
- **Kate Temkin ([@ktemkin](https://github.com/ktemkin), she/her [singular] or they/them [plural])**
|
||||
A performance art piece written live by a collective of hardware hackers & low-level engineers.
|
||||
- **Kate Temkin ([@ktemkin](https://github.com/ktemkin), she/her [singular] or they/them [plural])** <br>
|
||||
A performance art piece written live by a collective of hardware hackers & low-level engineers.
|
||||
Kate works on Lix as part of a commitment to helping you do cool things, and is seriously considering
|
||||
rewriting every bit of documentation ever to cross paths with Nix.
|
||||
|
||||
<br>
|
||||
- **Lily ([@lilyinstarlight](https://github.com/lilyinstarlight), she/they)**
|
||||
|
||||
- **Lunaphied ([@Lunaphied](https://github.com/lunaphied), she/her [singular] or they/them [plural])**
|
||||
- **Lunaphied ([@Lunaphied](https://github.com/lunaphied), she/her [singular] or they/them [plural])** <br>
|
||||
Lunaphied spend a disproportionate amount of their time considering how to get FPGAs as far from Earth as possible.
|
||||
When they're not working on Space Stuff, they consider doing the same for Nix regressions.
|
||||
|
||||
- **pennae (aka "eldritch horrors", they/them)**
|
||||
- **pennae (aka "eldritch horrors", they/them)** <br>
|
||||
The shadow at the end of a dark hallway. An ancient, nameless evil. Likes cookies
|
||||
|
||||
- **puck ([@puckipedia](https://github.com/puckipedia), she/her [singular] or they/them [plural])**
|
||||
|
||||
- **Qyriad ([@Qyriad](https://github.com/Qyriad), she/her [singular] or they/them [plural])**
|
||||
Build system experts who delve way, way too deep into tooling -- so you don't have to.
|
||||
- **Qyriad ([@Qyriad](https://github.com/Qyriad), she/her [singular] or they/them [plural])** <br>
|
||||
Build system experts who delve way, way too deep into tooling -- so you don't have to.
|
||||
|
||||
- **raito ([@RaitoBezarius](https://github.com/RaitoBezarius), he/him)**
|
||||
Raito is working on nixpkgs packaging, infrastructure, and review in Lix.
|
||||
- **raito ([@RaitoBezarius](https://github.com/RaitoBezarius), he/him)** <br>
|
||||
Raito is working on nixpkgs packaging, infrastructure, and review in Lix.
|
||||
They are a Tvix developer focusing on the store and the evaluator.
|
||||
|
||||
- **Rebecca Turner ([@9999years](https://github.com/9999years), she/her)**
|
||||
Rebecca is working on the evaluator and error messages.
|
||||
- **Rebecca Turner ([@9999years](https://github.com/9999years), she/her)**
|
||||
|
||||
<br/>
|
||||
|
||||
|
|
@ -74,22 +73,22 @@ conflicts of interest.
|
|||
expectation for her to contribute to Lix on company time. **Should a governance decision involving
|
||||
these or any other financial ties arise, hexchen will recuse herself from decision-making.**
|
||||
|
||||
- **Irene Knapp** (they/them) is the technology director of Internet Safety Labs (ISL), a US-based 501(c)(3)
|
||||
non-profit. To the best of Irene's knowledge, ISL has no financial involvement with any Lix or Nix
|
||||
effort or organization, other than its own internal infrastructure.
|
||||
Irene is also involved in an advisory capacity with the Coworker Solidarity Fund, a US-based 501(c)(4).
|
||||
**Should a governance decision involving these or any other financial ties arise, Irene will recuse themselves
|
||||
- **Irene Knapp** (they/them) is the technology director of Internet Safety Labs (ISL), a US-based 501(c)(3)
|
||||
non-profit. To the best of Irene's knowledge, ISL has no financial involvement with any Lix or Nix
|
||||
effort or organization, other than its own internal infrastructure.
|
||||
Irene is also involved in an advisory capacity with the Coworker Solidarity Fund, a US-based 501(c)(4).
|
||||
**Should a governance decision involving these or any other financial ties arise, Irene will recuse themselves
|
||||
from decision-making.** Additionally, while the following does not fall within the scope of any reasonable
|
||||
conflict of interest policy and is not within the scope of the recusal promise,
|
||||
Irene chooses to affirm that they have many personal ties to trans, disabled and
|
||||
neurodivergent tech workers, and are involved with providing and encouraging peer support to same.
|
||||
Irene views the broader queer, disabled, and neurodivergent communities as the primary people to whom
|
||||
conflict of interest policy and is not within the scope of the recusal promise,
|
||||
Irene chooses to affirm that they have many personal ties to trans, disabled and
|
||||
neurodivergent tech workers, and are involved with providing and encouraging peer support to same.
|
||||
Irene views the broader queer, disabled, and neurodivergent communities as the primary people to whom
|
||||
they are responsible as an activist, regardless of whatever other affiliations they may have.
|
||||
|
||||
- **Jade** is currently not working on anything else relevant to Lix development.
|
||||
She thus declares that she has **no conflicts of interest** regarding the governance of Lix.
|
||||
- **Jade** is currently not working on anything else relevant to Lix development.
|
||||
She thus declares that she has **no conflicts of interest** regarding the governance of Lix.
|
||||
|
||||
- **Kate Temkin** is the CEO and one-third owner of **Tactile Metrology LLC (TMLLC)**, a company that currently
|
||||
- **Kate Temkin** is the CEO and one-third owner of **Tactile Metrology LLC (TMLLC)**, a company that currently
|
||||
sponsors Lix development. TMLLC declares that it has no financial stake in the future of Lix or Nix,
|
||||
no ties to the military-industrial-complex, and a strong commitment to avoiding such ties. TMLLC is
|
||||
owned by individuals, and not VC investors. **Should any decision arise in which TMLLC's interests are
|
||||
|
|
@ -99,34 +98,29 @@ conflicts of interest.
|
|||
|
||||
- **Lunaphied** declare that they have **no conflicts of interest** regarding the governance of Lix.
|
||||
|
||||
- **pennae** declare that they have **no conflicts of interest** regarding the governance of Lix.
|
||||
- **pennae** declare that they have **no conflicts of interest** regarding the governance of Lix.
|
||||
|
||||
- **Puck** is working on a NLnet project involving Nix. **Should a governance decision involving relevant
|
||||
- **Puck** is working on a NLnet project involving Nix. **Should a governance decision involving relevant
|
||||
financial interests arise, she will recuse herself from the relevant decision-making.**
|
||||
|
||||
- **Qyriad** is a one-third owner of **Tactile Metrology LLC (TMLLC)**, a company that currently
|
||||
- **Qyriad** is a one-third owner of **Tactile Metrology LLC (TMLLC)**, a company that currently
|
||||
sponsors Lix development. TMLLC declares that it has no financial stake in the future of Lix or Nix,
|
||||
no ties to the military-industrial-complex, and a strong commitment to avoiding such ties. TMLLC is
|
||||
owned by individuals, and not VC investors. **Should any decision arise in which TMLLC's interests are
|
||||
owned by individuals, and not VC investors. **Should any decision arise in which TMLLC's interests are
|
||||
relevant,Qyriad will recuse herself from the relevant decision-making**.
|
||||
|
||||
- **raitobezarius** declares that he's self-employed in a cooperative, offers Nix-based consulting and training.
|
||||
- **raitobezarius** declares that he's self-employed in a cooperative, offers Nix-based consulting and training.
|
||||
He has currently no stake in the cooperative, though this will change soon. He's also employed by INRIA until
|
||||
August 2024 on Rust formal verification matters. **Should a governance decision involving these or any other
|
||||
August 2024 on Rust formal verification matters. **Should a governance decision involving these or any other
|
||||
financial ties arise, raitobezarius will recuse himself from decision-making.**
|
||||
Additionally, raitobezarius is co-president of DGNum (dgnum.eu), a French "loi 1901" nonprofit organization
|
||||
aiming to promote the parisian Ecole Normale Superieure (45 rue d'Ulm, 75005 Paris) excellence on computer
|
||||
Additionally, raitobezarius is co-president of DGNum (dgnum.eu), a French "loi 1901" nonprofit organization
|
||||
aiming to promote the parisian Ecole Normale Superieure (45 rue d'Ulm, 75005 Paris) excellence on computer
|
||||
science using heavily Nix/NixOS based technologies.
|
||||
|
||||
- **Rebecca Turner** works for [Mercury](https://mercury.com/), a financial
|
||||
services startup that [uses
|
||||
Nix](https://serokell.io/blog/haskell-in-production-mercury) to build
|
||||
software. **Should a governance decision involving these or any other
|
||||
financial ties arise, Rebecca will recuse herself from the relevant
|
||||
decision-making.**
|
||||
- **Rebecca Turner** works for mercury.com, a company that uses nix to build software. **Should a governance decision involving these or any other financial ties arise, wiggles will recuse herself from the relevant decision-making.**
|
||||
|
||||
<br />
|
||||
|
||||
These declarations were last updated on **May 5st, 2024**, and are believed to be up-to-date to the current date.
|
||||
If the bolded date is more than 28 days in the past, feel free to reach out via our
|
||||
These declarations were last updated on **May 5st, 2024**, and are believed to be up-to-date to the current date.
|
||||
If the bolded date is more than 28 days in the past, feel free to reach out via our
|
||||
[community channels](/community) to request these declarations be updated.
|
||||
|
|
|
|||
|
|
@ -12,8 +12,8 @@
|
|||
flake-utils.url = "github:numtide/flake-utils";
|
||||
};
|
||||
|
||||
outputs = { self, nixpkgs, flake-utils }:
|
||||
flake-utils.lib.eachDefaultSystem (system:
|
||||
outputs = { self, nixpkgs, flake-utils }:
|
||||
flake-utils.lib.eachDefaultSystem (system:
|
||||
let
|
||||
pkgs = import nixpkgs { inherit system; };
|
||||
in
|
||||
|
|
|
|||
|
|
@ -44,6 +44,6 @@ version of the website with the theme.
|
|||
Hugo Up Business Theme is based on a [Figma Design by Abell
|
||||
Vo](https://www.figma.com/community/file/1022163547182520272).
|
||||
|
||||
## License
|
||||
## License
|
||||
|
||||
Up Business is licensed under the MIT license.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
<svg xmlns="http://www.w3.org/2000/svg" width="16px" height="16px" viewBox="0 0 92 92"><defs><clipPath id="a"><path d="M0 .113h91.887V92H0Zm0 0"/></clipPath></defs><g clip-path="url(#a)"><path style="stroke:none;fill-rule:nonzero;fill:#f03c2e;fill-opacity:1" d="M90.156 41.965 50.036 1.848a5.918 5.918 0 0 0-8.372 0l-8.328 8.332 10.566 10.566a7.03 7.03 0 0 1 7.23 1.684 7.034 7.034 0 0 1 1.669 7.277l10.187 10.184a7.028 7.028 0 0 1 7.278 1.672 7.04 7.04 0 0 1 0 9.957 7.05 7.05 0 0 1-9.965 0 7.044 7.044 0 0 1-1.528-7.66l-9.5-9.497V59.36a7.04 7.04 0 0 1 1.86 11.29 7.04 7.04 0 0 1-9.957 0 7.04 7.04 0 0 1 0-9.958 7.06 7.06 0 0 1 2.304-1.539V33.926a7.049 7.049 0 0 1-3.82-9.234L29.242 14.272 1.73 41.777a5.925 5.925 0 0 0 0 8.371L41.852 90.27a5.925 5.925 0 0 0 8.37 0l39.934-39.934a5.925 5.925 0 0 0 0-8.371"/></g></svg>
|
||||
<svg xmlns="http://www.w3.org/2000/svg" width="92pt" height="92pt" viewBox="0 0 92 92"><defs><clipPath id="a"><path d="M0 .113h91.887V92H0Zm0 0"/></clipPath></defs><g clip-path="url(#a)"><path style="stroke:none;fill-rule:nonzero;fill:#f03c2e;fill-opacity:1" d="M90.156 41.965 50.036 1.848a5.918 5.918 0 0 0-8.372 0l-8.328 8.332 10.566 10.566a7.03 7.03 0 0 1 7.23 1.684 7.034 7.034 0 0 1 1.669 7.277l10.187 10.184a7.028 7.028 0 0 1 7.278 1.672 7.04 7.04 0 0 1 0 9.957 7.05 7.05 0 0 1-9.965 0 7.044 7.044 0 0 1-1.528-7.66l-9.5-9.497V59.36a7.04 7.04 0 0 1 1.86 11.29 7.04 7.04 0 0 1-9.957 0 7.04 7.04 0 0 1 0-9.958 7.06 7.06 0 0 1 2.304-1.539V33.926a7.049 7.049 0 0 1-3.82-9.234L29.242 14.272 1.73 41.777a5.925 5.925 0 0 0 0 8.371L41.852 90.27a5.925 5.925 0 0 0 8.37 0l39.934-39.934a5.925 5.925 0 0 0 0-8.371"/></g></svg>
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 820 B After Width: | Height: | Size: 820 B |
|
|
@ -1,4 +1,4 @@
|
|||
<svg xmlns="http://www.w3.org/2000/svg" width="16px" height="17.15px" viewBox="0 0 216.4144 232.00976">
|
||||
<svg xmlns="http://www.w3.org/2000/svg" width="61.076954mm" height="65.47831mm" viewBox="0 0 216.4144 232.00976">
|
||||
<path fill="#2b90d9" d="M211.80734 139.0875c-3.18125 16.36625-28.4925 34.2775-57.5625 37.74875-15.15875 1.80875-30.08375 3.47125-45.99875 2.74125-26.0275-1.1925-46.565-6.2125-46.565-6.2125 0 2.53375.15625 4.94625.46875 7.2025 3.38375 25.68625 25.47 27.225 46.39125 27.9425 21.11625.7225 39.91875-5.20625 39.91875-5.20625l.8675 19.09s-14.77 7.93125-41.08125 9.39c-14.50875.7975-32.52375-.365-53.50625-5.91875C9.23234 213.82 1.40609 165.31125.20859 116.09125c-.365-14.61375-.14-28.39375-.14-39.91875 0-50.33 32.97625-65.0825 32.97625-65.0825C49.67234 3.45375 78.20359.2425 107.86484 0h.72875c29.66125.2425 58.21125 3.45375 74.8375 11.09 0 0 32.975 14.7525 32.975 65.0825 0 0 .41375 37.13375-4.59875 62.915"/>
|
||||
<path fill="#fff" d="M177.50984 80.077v60.94125h-24.14375v-59.15c0-12.46875-5.24625-18.7975-15.74-18.7975-11.6025 0-17.4175 7.5075-17.4175 22.3525v32.37625H96.20734V85.42325c0-14.845-5.81625-22.3525-17.41875-22.3525-10.49375 0-15.74 6.32875-15.74 18.7975v59.15H38.90484V80.077c0-12.455 3.17125-22.3525 9.54125-29.675 6.56875-7.3225 15.17125-11.07625 25.85-11.07625 12.355 0 21.71125 4.74875 27.8975 14.2475l6.01375 10.08125 6.015-10.08125c6.185-9.49875 15.54125-14.2475 27.8975-14.2475 10.6775 0 19.28 3.75375 25.85 11.07625 6.36875 7.3225 9.54 17.22 9.54 29.675"/>
|
||||
</svg>
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 1.4 KiB After Width: | Height: | Size: 1.4 KiB |
|
|
@ -1,4 +1,4 @@
|
|||
<svg version="1.1" viewBox="0 0 27.9 32" width="16px" height="18px" xmlns="http://www.w3.org/2000/svg" xmlns:cc="http://creativecommons.org/ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
|
||||
<svg version="1.1" viewBox="0 0 27.9 32" xmlns="http://www.w3.org/2000/svg" xmlns:cc="http://creativecommons.org/ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
|
||||
<title>Matrix (protocol) logo</title>
|
||||
<g transform="translate(-.095 .005)" fill="#040404">
|
||||
<path d="m27.1 31.2v-30.5h-2.19v-0.732h3.04v32h-3.04v-0.732z"/>
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 1.4 KiB After Width: | Height: | Size: 1.4 KiB |
|
|
@ -10,7 +10,7 @@
|
|||
{{ end }}
|
||||
</div>
|
||||
</div>
|
||||
<div class="row g-4 g-md-5">
|
||||
<div class="row g-5">
|
||||
{{ range .content.cards }}
|
||||
<div class="col-12 col-xl-4">
|
||||
<div class="card bg-blue-16 border-0 border-radius-34 p-4">
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
<p class="small text-black-61">{{ .Site.Params.description }}</p>
|
||||
{{ with .Site.Params.social }}
|
||||
<ul class="d-flex justify-content-center justify-content-xl-start list-unstyled">
|
||||
{{ with .mastodon }}<li class="rounded-circle bg-blue-63 me-2 p-2"><a rel="me" class="d-flex align-items-center justify-content-center size-16 svglogo" href="{{ . }}">{{ partial "icons/mastodon.html" }}</a></li>{{ end }}
|
||||
{{ with .mastodon }}<li class="rounded-circle bg-blue-63 me-2 p-2"><a class="d-flex align-items-center justify-content-center size-16 svglogo" href="{{ . }}">{{ partial "icons/mastodon.html" }}</a></li>{{ end }}
|
||||
{{ with .matrix }}<li class="rounded-circle bg-blue-63 me-2 p-2"><a class="d-flex align-items-center justify-content-center size-16 svglogo" href="{{ . }}">{{ partial "icons/matrix.html" }}</a></li>{{ end }}
|
||||
{{ with .github }}<li class="rounded-circle bg-blue-63 me-2 p-2"><a class="d-flex align-items-center justify-content-center size-16 svglogo" href="{{ . }}">{{ partial "icons/github.html" }}</a></li>{{ end }}
|
||||
{{ with .git }}<li class="rounded-circle bg-blue-63 me-2 p-2"><a class="d-flex align-items-center justify-content-center size-16 svglogo" href="{{ . }}">{{ partial "icons/git.html" }}</a></li>{{ end }}
|
||||
|
|
|
|||
Loading…
Reference in a new issue