unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: John Kehayias via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "51000@debbugs.gnu.org" <51000@debbugs.gnu.org>
Subject: bug#51000: The Web manual situation is still needlessly confusing
Date: Mon, 04 Oct 2021 04:19:41 +0000	[thread overview]
Message-ID: <susz0kTIZduiBm3i-bxbWioXd1-7m0GKVQJHBNMOHlb7o-yzcFfKyFS77l1TZEZuag_GtYjhtIJmZflLEbZNZbTMIYwNbX6Rgluz0O6KEuA=@protonmail.com> (raw)
In-Reply-To: <87ilydycps.fsf@nckx>

Hi everyone,

Definitely agree with needing this to be clearer than it is currently. As a new user I was a bit confused over the different manual versions on the website (which is still how I prefer to read the manual). As a side note, when searching online with Guix questions, I think I only see the 'stable' version come up in results.

We could perhaps be clearer in what is meant by the 'stable'/1.3.0 documentation. Seems this is mostly needed in preparing for installation (with the 1.3.0 image, not if building a current install image, of course) and during installation. Afterward, users will probably run a guix pull very soon (as in Getting Started, or as recommended by the guix command itself) and thus no longer be on the 1.3.0 manual. I'm not sure how best to communicate this on the website, but to me it is related to the next point:

I think we need something describing what we mean by Guix versions and releases, perhaps in the Intro and/or Getting Started sections (and on an About type page?). I was confused by this starting out, as I'm used to rolling distros like Arch (or, a long time ago, distros like Debian). While Guix is mostly 'rolling', we also have releases with certain package changes (like core-updates) and Guix changes. Just a simple description would I think help new users and give better context for the manual versions, however we label or make them available.

I'm happy to take a stab and making either of these points clearer, especially as one newer to Guix with these questions and assumptions nearer to mind.

John




  reply	other threads:[~2021-10-04  4:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-03 22:12 bug#51000: The Web manual situation is still needlessly confusing Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-10-04  4:19 ` John Kehayias via Bug reports for GNU Guix [this message]
2021-10-04  6:31 ` Efraim Flashner
2021-10-04  6:58 ` zimoun
2023-05-22  1:59 ` bug#51000: Please drop web manuals for released versions Felix Lechner via Bug reports for GNU Guix
2023-09-27  9:26 ` bug#51000: The Web manual situation is still needlessly confusing Simon Tournier

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='susz0kTIZduiBm3i-bxbWioXd1-7m0GKVQJHBNMOHlb7o-yzcFfKyFS77l1TZEZuag_GtYjhtIJmZflLEbZNZbTMIYwNbX6Rgluz0O6KEuA=@protonmail.com' \
    --to=bug-guix@gnu.org \
    --cc=51000@debbugs.gnu.org \
    --cc=john.kehayias@protonmail.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 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).