From: Simon Josefsson via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Vagrant Cascadian <vagrant@debian.org>,
guix-devel@gnu.org, Luis Felipe <luis.felipe.la@protonmail.com>
Subject: Re: advanced?
Date: Mon, 09 Jan 2023 13:02:42 +0100 [thread overview]
Message-ID: <871qo3difx.fsf@josefsson.org> (raw)
In-Reply-To: <874jt65zux.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 04 Jan 2023 12:00:06 +0100")
[-- Attachment #1: Type: text/plain, Size: 2185 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> 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.
Reflecting on the feature list, I think we should mention that Guix is a
_rolling_ distribution and package manager, and maybe explain what that
means. I don't think this is clear from the web site or manual now, but
I may be missing it.
Perhaps the release and update model of Guix could use some dedicated
new documentation? The relationship between the rolling master branch,
the core-updates branch, the security graft mechanism, the substitute
build servers and the versioned installer releases is not terribly clear
to me as a new user, and having an understanding of these concepts helps
to make contributions. I have a feeling there may be more nuances that
are useful to know about that I'm not familiar with; for example, the
intended use of the version-X.Y.Z branches.
/Simon
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]
next prev parent reply other threads:[~2023-01-09 13:12 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 ` Simon Josefsson via Development of GNU Guix and the GNU System distribution. [this message]
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=871qo3difx.fsf@josefsson.org \
--to=guix-devel@gnu.org \
--cc=ludo@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).