all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: Simon Josefsson <simon@josefsson.org>, guix-devel@gnu.org
Subject: Re: advanced?
Date: Mon, 28 Nov 2022 16:35:09 +0100	[thread overview]
Message-ID: <20221128163509.02912a29@primary_laptop> (raw)
In-Reply-To: <878rjw5jq6.fsf@contorta>

[-- Attachment #1: Type: text/plain, Size: 2382 bytes --]

On Sun, 27 Nov 2022 10:35:13 -0800
Vagrant Cascadian <vagrant@debian.org> wrote:
> It also makes me wonder if "advanced" will stand the test of
> time. Someday Guix-style systems might just be status quo, and thus no
> longer advanced. Guix of course will likely evolve over time... maybe
> it will still hold qualities worthy of being called "advanced", [...]
Something interesting would be to convey what users need to know or
learn for using Guix. In "1.1 Managing Software the Guix Way" we
already have hints that it might require to know the command line and
scheme. Though maybe it could be clarified for less technical users.

For instance it "provides" [a command line interface], but that is not
clear that it's the only way to interact with some of Guix features.

If we compare Guix with other FSDG compliant distributions:
- Trisquel is usable by users that don't know the command
  line but less technical users might need a bit of help for upgrading
  from a version to another (in install parties for instance). Sometimes
  they just need somebody to be there just in case something goes wrong
  though.
- Parabola x86_64 can probably be used by users without command line
  knowledge (for a desktop/laptop usage) but the boot sometimes break,
  so less technical users also need to plan ahead and know how to
  reinstall it if needed (that could be done by having a separate home
  for instance). A server usage does require to know the command line
  and also to know how to edit configuration files (like Apache
  configuration file).
- Once installed, LibreCMC (and OpenWRT) are probably also relatively
  easy to configure for people that know what an IP address is, what is
  DHCP, what is an SSID, etc. Guix has the potential to be similar.
- Freedombox (available in PureOS, Debian, etc) looks way easier but it
  is also way less configurable.

Guix has the potential to have the same kind of balance between
easiness and empowerment/configurability than LibreCMC (if
graphical interfaces are written).

Making the current status more clear can probably help users. On my side
I've already taken that into account on the documentation I wrote on
FSDG compliant distributions on the Libreplanet wiki, but I'm not sure
how to improve the text in that manual section, or how to promote more
that information.

Denis.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2022-11-28 15:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-26 21:47 advanced? Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2022-11-27  8:51 ` advanced? Liliana Marie Prikler
2022-11-27 12:39 ` advanced? zimoun
2022-11-27 17:22 ` advanced? Ryan Prior
2022-11-27 18:35 ` advanced? Vagrant Cascadian
2022-11-28 11:18   ` advanced? Ludovic Courtès
2022-11-28 14:44     ` advanced? Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2022-11-28 18:36       ` advanced? zimoun
2023-01-04 11:00       ` advanced? Ludovic Courtès
2023-01-09 12:02         ` advanced? Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2022-11-28 15:35   ` Denis 'GNUtoo' Carikli [this message]
2023-01-04 10:54 ` advanced? Ludovic Courtès
2023-01-09 11:12   ` advanced? Ludovic Courtès
2023-01-09 11:37     ` advanced? Julien Lepiller

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=20221128163509.02912a29@primary_laptop \
    --to=gnutoo@cyberdimension.org \
    --cc=guix-devel@gnu.org \
    --cc=simon@josefsson.org \
    --cc=vagrant@debian.org \
    /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.