request: rename project to `nixified-ai`

[DavHau]

The name flake is not optimal because:

• after cloning the project it will end up in a directory called flake which might collide with other tings and also in not very expressive.
• Also after forking the project on github it just ends up as DavHau/flake which has the same problems as described above.

How about just calling the project nixified-ai/nixified-ai ?

[MatthewCroughan]

after cloning the project it will end up in a directory called flake

I wonder if there's a way we could fix that with Nix itself, some low level thing.

[adamcstephens]

The name of the repo is used by git when cloning. Even if I could hack around this with Nix to rename the repo on clone, I wouldn't want to.

[MatthewCroughan]

Does anyone know how long GitHub will redirect the URL for, or whether it will at all?

[adamcstephens]

Yes, a single redirect will happen. AFAIK it is indefinite.

[MatthewCroughan]

Right, better to do it sooner rather than later then. Can anyone think of a better name than nixified-ai in this case, to make the most of this opportunity?

[DavHau]

I think the name is fine

[max-privatevoid]

nixified.ai could also be an option if we want to make our fancy domain stand out more

[MatthewCroughan]

Is there any way that is known to give the Nix flake URI a default repository? So for example nix run github:nixified-ai would default to a repository that we specify?

[MatthewCroughan]

I think it would be reasonable if the Nix/libfetcher C++ implementation for Flake URIs defaulted to repositories of the same name.

nix run github:nixified-ai would be the same as nix run github:nixified-ai/nixified-ai

[max-privatevoid]

To that end, we could ask for a spot in the global flake registry, in which case we'd be at nix run nixified-ai.

[max-privatevoid]

Opened a feature request https://github.com/NixOS/nix/issues/8205