Change strings and docs to Lix in the code where that is correct

jade commented

2024-03-18 22:17:32 +00:00

Owner

No description provided.

jade added this to the v2.90 milestone 2024-03-18 22:17:32 +00:00

jade added the

release-blocker

label 2024-03-18 22:17:32 +00:00

jade added this to the Release engineering project 2024-03-18 22:17:32 +00:00

raito self-assigned this 2024-03-19 01:18:26 +00:00

jade commented

2024-03-19 01:19:42 +00:00

Author

Owner

I have a CL happening that i seem to have ... misplaced? that changes it inside the codebase.

jade commented

2024-03-19 01:19:59 +00:00

Author

Owner

Docs still important but we might want to go after backports of docs prs first.

raito commented

2024-03-19 01:28:48 +00:00

Owner

@jade Should we over-replace here, e.g. replace systematically in documentation any allusion or keep some concepts like "Nix store" instead of "Lix store", etc. ?

I feel like we should keep comment code / classes names / variable names to use Nix until we rewrite the code, right?

@jade Should we over-replace here, e.g. replace systematically in documentation any allusion or keep some concepts like "Nix store" instead of "Lix store", etc. ? I feel like we should keep comment code / classes names / variable names to use Nix until we rewrite the code, right?

jade commented

2024-03-19 01:29:42 +00:00

Author

Owner

https://gerrit.lix.systems/c/lix/+/576 I have un-misplaced my CL.

jade commented

2024-03-19 01:30:17 +00:00

Author

Owner

@jade Should we over-replace here, e.g. replace systematically in documentation any allusion or keep some concepts like "Nix store" instead of "Lix store", etc. ?

I feel like we should keep comment code / classes names / variable names to use Nix until we rewrite the code, right?

I meant to put this in a document somewhere.

I think that style guide wise, it should still be Nix store, because it is referring to the technology. But the implementation is Lix.

> @jade Should we over-replace here, e.g. replace systematically in documentation any allusion or keep some concepts like "Nix store" instead of "Lix store", etc. ? > > I feel like we should keep comment code / classes names / variable names to use Nix until we rewrite the code, right? I meant to put this in a document somewhere. I think that style guide wise, it should still be Nix store, because it is referring to the technology. But the implementation is Lix.

ktemkin modified the project from Release engineering to Soft Launch

2024-04-27 01:16:17 +00:00

lunaphied changed title from ~~Change strings and docs to Lix where that is correct~~ to Change strings and docs to Lix in the code where that is correct

2024-04-28 23:58:03 +00:00

lunaphied referenced this issue

2024-04-28 23:59:13 +00:00

Remove all Nix branding and references to the NixOS GitHub in non-code #162