Comments (12)
I really think the basic idea of RFCs is great: Writing down motivation, detailed design, arguments and alternatives for a decision (also see ADR). It would be unfortunate if the negative stigma of the RFC process discourages us from writing such documents.
So this sounds like a great plan to me, I'll try to write this down in such a format here once I have some time to spare!
from nix.dev.
To me this feels as if we are yet again mixing up the products and mangling it into oneβ¦
We should strive to a clear seperation of concerns and do a strict distinction between nix the build tool + nixpkgs as kind of its stdlib on one side and NixOS as the Linux distribution built using nix on the other side.
If I were to visit docs.nixos.org
I'd expect to see what is currently available under nixos.org/manuals/nixos
, not some mostly nix related cookbook.
If we were to collect everything under nixos.org
, I'd prefer nix.nixos.org/docs
or something like that much more, to make clear, this is about nix specifically!
from nix.dev.
I have no issues with this plan. Domain consistency feels more important to me. One thing to keep in mind is that the theme/css of nix.dev
is different from the one usually used in nixos.org
pages, so we may have to fix that at some point to maintain visual consistency as well. I don't think it's important to have that before the move to docs.nixos.org
though, so I say go ahead!
from nix.dev.
@GetPsyched started with an effort to write an RFC in this repository. I think it's better to keep this separate from https://github.com/nix-rfc-canonical-domain/rfcs, since that one is more about moving to another domain.
Just opened a PR to add some stuff: GetPsyched/nixos-domain-unification#1
from nix.dev.
@NobbZ that's also generally my concern, but between docs.nixos.org/nix
and nix.nixos.org/docs
is only a cosmetic difference. What we're building here is an entry point to the ecosystem's documentation. That needs a place. Today it only may appear like a Nix-specific cookbook because we haven't systematically dealt with NixOS yet.
There's still an option to move everything somewhere else (such as nix.dev
that we currently own or nix.org
if we ever get it) and rightfully make NixOS a special case in its own corner. But that's future work.
from nix.dev.
How do you think the fact that the domain mentions NixOS affect the message that the docs are actually about the whole platform?
This is an old issue and not resolved by the nix.dev domain either, fwiw.
from nix.dev.
How do you think the fact that the domain mentions NixOS affect the message that the docs are actually about the whole platform?
I believe that's mainly an orthogonal issue, it's not really affected by this. I guess if we do decide to use nix.dev in the end, we'd be moving back-and-forth nix.dev -> docs.nixos.org -> docs.nix.dev, which is a bit special, but not a problem.
from nix.dev.
I'm struggling to make up my mind about this. So I'm not enthusiastic, but it's probably not wrong, and therefore I won't oppose.
Given this is quite an impactful change nonetheless, and the discussion is scattered over a good number of threads, I'd really appreciate a summary of the trade-offs for posterity though. Sorry if that sounds like "please make an RFC" (I really don't want more RFCs). But not having a summary for the announcement will very likely lead to questions and raised concerns, and more scattered discussion. If not communicated properly, most outsiders will see this and think "what the hell are they doing there".
Assuming no one from the docs team opposes, how about making a Discourse post with all we had so far, and if no one cries up, go ahead and implement it? We may as well go on and rename this repository to NixOS/docs
for consistency.
from nix.dev.
I think the only blocker right now is the unresolved question of there being docs for NixOS itself; however, that could be the new official wiki, likely located at wiki.nixos.org
.
I don't mean to add unnecessary additional discussion on the topic, but consider these alternatives:
- Move the existing
nixos.org/learn
todocs.nixos.org
and we can go deeper from there,docs.nixos.org/nixos
,docs.nixos.org/nix
. - Same as above but on
learn.nixos.org
from nix.dev.
So nix.dev will become a landing page for the Nix project then?
from nix.dev.
So nix.dev will become a landing page for the Nix project then?
The original proposal was to move nix.dev
to docs.nixos.org
, and then nixos.org
to nix.dev
.
This has shifted to nix.dev
moving to docs.nixos.org
, and that's it.
Feel free to read more in the original comment of this issue or the "RFC" in my repo for reference.
from nix.dev.
nix.land
I liked it, I try to buy it, but the price was so high. To be honest, would not use it for nix home page, I'm biased since I want it for nixos.land.
Related: πΈοΈ
Nix related domains that I someone here controls
Pre-RFC: A single canonical domain name (forum)
BTW, nixify.io is available.
from nix.dev.
Related Issues (20)
- CI stuck HOT 2
- Link does not go where expected HOT 2
- use an open service on /tutorials/module-system/module-system.html HOT 6
- Expand and improve the Module System tutorial HOT 5
- Missing `rec-expression` anchor redirect and inquiry into redirect logic
- Issue on page /tutorials/first-steps/declarative-shell.html | Setting environment variables HOT 1
- Issue on page /tutorials/packaging-existing-software.html HOT 3
- Documentation for nix.conf HOT 2
- 404. Nixos.org link to channels in "learning" HOT 2
- Issue on page /tutorials/nix-language.html HOT 1
- Typos causing errors in https://nix.dev/tutorials/working-with-local-files HOT 1
- incorrect redirect for nix manual HOT 4
- Redirect (stable/unstable) issues from nixos.org
- Issue on learn page, the nix installation link shows "Page not found" HOT 1
- [SEO] Duplication HOT 1
- broken Link in https://nix.dev/tutorials/packaging-existing-software "selecting xorg"
- Setting up a binary cache HOT 1
- Setting up distributed builds HOT 1
- Provisioning remote machines HOT 1
- Introduce notation and clarify prerequsites
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nix.dev.