unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Simon Josefsson <simon@josefsson.org>
Cc: Vagrant Cascadian <vagrant@debian.org>,
	 guix-devel@gnu.org, Luis Felipe <luis.felipe.la@protonmail.com>
Subject: Re: advanced?
Date: Wed, 04 Jan 2023 12:00:06 +0100	[thread overview]
Message-ID: <874jt65zux.fsf@gnu.org> (raw)
In-Reply-To: <871qpnp28t.fsf@latte> (Simon Josefsson's message of "Mon, 28 Nov 2022 15:44:50 +0100")

Hello,

(Cc: Luis, for the web site design.)

Simon Josefsson <simon@josefsson.org> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Or if we do want to explain more, then perhaps we need a list of
>> features that would also include things like Docker/VM image generation,
>> declarative home environments, etc.  But that’s broader topic.
>
> Yes, that makes sense.  I'm not the best person to summarize it, but
> starting pointers if someone wants to take it further:
>
> * Dedication to free software goals and the GNU community
>
> * Shepherd init system written in Guile
>
> * Declarative stateless system configurations
>
> * Transactional upgrades and roll-backs
>
> * Reproducible build environments
>
> * Designed towards bootstrappable builds
>
> Maybe this fits better directly in the Introduction section of the
> manual?  https://guix.gnu.org/manual/en/html_node/Introduction.html

I guess we should rework the “Introduction” and “Features” sections,
which were written in the early days.

The points you list above are a great starting point, and I guess that
would also be a good fit for the front page; currently there’s no
“feature list” there.  That old “Guix in action” video also ought to be
replaced.

Luis, do you have ideas as to how we could present things?

Thanks,
Ludo’.


  parent reply	other threads:[~2023-01-04 11:00 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       ` Ludovic Courtès [this message]
2023-01-09 12:02         ` advanced? Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2022-11-28 15:35   ` advanced? Denis 'GNUtoo' Carikli
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

  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=874jt65zux.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=luis.felipe.la@protonmail.com \
    --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 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).