unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: website: say what Guix is at the very top
Date: Fri, 19 Jan 2018 09:04:12 +0100	[thread overview]
Message-ID: <87d1266zr7.fsf@elephly.net> (raw)
In-Reply-To: <1e6cee12-07d0-6d08-1dcf-35ce19bdd58d@tobias.gr>


Hi Tobias,

> I don't know who wrote the current intro, but I think it's pretty good.
> Have you got negative feedback from curious visitors?

Unfortunately, I have.  The most common feedback is an expression of
confusion about the difference between GuixSD and Guix.

But to be fair: this email was not triggered by negative feedback, but
by my own failure to find a succint explanation of Guix on the home
page.  I had hoped to find a concise intro that I could send someone to
explain what this Guix thing is all about but none of the sentences on
the home page really did the job well enough.

I ended up opening the Introduction section of the manual and edited it
to reduce the number of words.

> It's not just a list of features. The current intro is:
>
>   - Liberating. The Guix System Distribution (GuixSD) is an advanced
>     distribution of the GNU operating system developed by the GNU
>     Project—which respects the freedom of computer users.
>
>   - Dependable. It comes with the GNU Guix package manager, which in
>     addition to standard package management features, supports
>     transactional upgrades and roll-backs, unprivileged package
>     management, per-user profiles, and more.
>
>   - Hackable. It provides Guile Scheme APIs, including high-level
>     embedded domain-specific languages (EDSLs) to define packages and
>     whole-system configurations.
>
> I like the way it mixes description, features, and values without
> getting lost in marketing-speak. It also breaks up the text into small
> chunks, which is apparently mandatory on the 'Net.

Yes, I’m not saying it’s poorly written.  I agree with all of the
positive things you wrote about the intro.

What I don’t like is that it comes across as a list of features (single
word after bullet) with further explanation of those features — but
that’s not what it is.  It’s not even a list of features for the same
thing!

>> We should add a very short paragraph above that list to say what Guix
>> and GuixSD are.
>>> What do you think?
>
> Hm, what do you suggest?

I suggest moving the GuixSD parts to a sub-page first.  What’s left on
the front-page would only be about Guix, the package manager.  This
means that the current first paragraph would disappear and would have to
be replaced.

The current second paragraph “Dependable…” could be split up such that
we can elaborate a little more about the novel features of Guix.  Right
now it doesn’t real all *that* novel to me:

- “standard package management features”

- “transactional upgrades and roll-backs”: yum did that too, but in
  quite a different way than Guix.

- “unprivileged package management”: this deserves to be higher up

- “per-user profiles, and more”: ah, now it gets interesting, but the
  list is already too long, so we end immediately with “and more”.  Hmm.

I suggest to not even mention “standard package management features”.


Let’s look at the Conda intro.  There are many things I don’t like about
it, but there are some things we can learn from it:

    https://conda.io/docs/index.html

The first paragraph states:

    Conda is [a] package management system and environment management
    system that runs on Windows, macOS and Linux. Conda quickly
    installs, runs and updates packages and their dependencies. Conda
    easily creates, saves, loads and switches between environments on
    your local computer. […]

It then drifts off and talks about Python all the time, but these first
sentences clearly tell me what it does: package and environment
management, installing packages and dependencies,
creating/loading/switching between environments.

Guix does all this but with reproducibility at its core, yet our
introduction neither mentions reproducibility nor does it say anything
about environments.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2018-01-19 15:50 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 [this message]
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
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d1266zr7.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).