From: Oleg Pykhalov <go.wigust@gmail.com>
To: myglc2@gmail.com
Cc: guix-devel@gnu.org, sirgazil <lizagris@protonmail.com>
Subject: Re: website: say what Guix is at the very top
Date: Wed, 24 Jan 2018 17:24:34 +0300 [thread overview]
Message-ID: <87fu6vgwrh.fsf@gmail.com> (raw)
In-Reply-To: <86zi53vm18.fsf@gmail.com> (myglc2@gmail.com's message of "Wed, 24 Jan 2018 00:54:59 -0500")
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
Hello,
myglc2@gmail.com writes:
[...]
>> (I’m not as sure about these proposed individual changes as I am about
>> the proposal to separate the pages for Guix and GuixSD.)
>
> ISTM this difficulty in splitting the content across two pages is a
> reason to consider again how to unify the presentation of Guix/GuixSD.
Nix folks have a talk about splitted web pages for Nix package manager,
NixOS, Nix Expression Language. They don't like it much, because when a
new person come to Nix, he cannot find a documentation for Nix
Expression language, because it's not clear that you need to go to the
separate page <https://nixos.org/nix/manual/> and not for example
<https://nixos.org/nixpkgs/manual/>.
Again while I'm writing current message, I cannot find their NixOS
installation page manual. :-) It's under support if you want to get
there with a mouse. <https://nixos.org/nixos/manual/>
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-01-24 14:24 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 17:30 website: say what Guix is at the very top Ricardo Wurmus
2018-01-17 18:08 ` Tobias Geerinckx-Rice
2018-01-19 8:04 ` Ricardo Wurmus
2018-01-21 17:11 ` Tobias Geerinckx-Rice
2018-01-19 6:09 ` George myglc2 Clemmer
2018-01-19 7:42 ` Ricardo Wurmus
2018-01-19 13:32 ` Ludovic Courtès
2018-01-19 20:35 ` myglc2
2018-01-21 14:47 ` Ricardo Wurmus
2018-01-24 5:54 ` myglc2
2018-01-24 14:24 ` Oleg Pykhalov [this message]
2018-01-24 14:22 ` Ludovic Courtès
2018-01-26 23:03 ` myglc2
2018-01-27 16:14 ` Ludovic Courtès
2018-01-27 18:20 ` myglc2
2018-01-27 21:59 ` Pjotr Prins
2018-01-28 16:24 ` Ricardo Wurmus
2018-01-29 4:14 ` myglc2
2018-01-29 7:37 ` Pjotr Prins
2018-01-29 21:31 ` Cook, Malcolm
2018-01-29 22:20 ` Ricardo Wurmus
2018-01-29 22:24 ` Cook, Malcolm
2018-01-30 1:03 ` Ricardo Wurmus
2018-01-30 22:17 ` myglc2
2018-01-30 1:43 ` George myglc2 Clemmer
2018-01-30 2:56 ` Ricardo Wurmus
2018-01-30 7:31 ` Pjotr Prins
2018-01-30 7:46 ` Pjotr Prins
2018-01-31 16:58 ` myglc2
2018-01-31 17:27 ` Pjotr Prins
2018-01-31 18:11 ` myglc2
2018-01-31 18:13 ` Pjotr Prins
2018-01-28 0:35 ` Chris Marusich
2018-01-22 7:04 ` Chris Marusich
2018-01-22 16:43 ` myglc2
2018-03-16 7:14 ` Pjotr Prins
2018-01-24 14:19 ` Ludovic Courtès
2018-01-28 0:33 ` Chris Marusich
2018-01-28 21:58 ` Ludovic Courtès
2018-01-29 2:08 ` Chris Marusich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fu6vgwrh.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=guix-devel@gnu.org \
--cc=lizagris@protonmail.com \
--cc=myglc2@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.