all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: "\(" <paren@disroot.org>, 59822@debbugs.gnu.org
Subject: [bug#59822] [PATCH guix-artwork] website: base: home: Add 'DOWNLOAD LATEST' button.
Date: Tue, 06 Dec 2022 18:45:13 +0100	[thread overview]
Message-ID: <86pmcwifyu.fsf@gmail.com> (raw)
In-Reply-To: <87o7sg5w5n.fsf@pelzflorian.de>

Hi,

On Tue, 06 Dec 2022 at 17:33, "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> wrote:

> Yes (’s patch was merely about discoverability of the latest installer
> page, that already exists.  Also the latest installer page has a warning
> that points users to the standard installer.  So we could push

For what it is worth, I think it is better to keep the front page with
only 2 buttons: “Download v1.x“ and “Contribute”.

For discoverability, what I propose instead is to redirect the users
from,

    https://guix.gnu.org/en/download/

If the user does not read the header or is not interested in, they can
process with the current released images.  Otherwise, as I propose, a
mention to the latest development, and hop to the other page,

    https://guix.gnu.org/en/download/latest/


> But then, shouldn’t we tell users there are bugs in the standard image and
> they better use latest?

By mentioning in the header of:

    https://guix.gnu.org/en/download/

For example, it reads,

--8<---------------cut here---------------start------------->8---
As of version 1.3.0, the standalone Guix System can be installed on an
i686, x86_64, ARMv7, or AArch64 machine. It uses the Linux-Libre kernel
and the GNU Shepherd init system. Alternately, GNU Guix can be installed
as an additional package manager on top of an installed Linux-based
system.
--8<---------------cut here---------------end--------------->8---

Therefore, we can add here one sentence or two for mentioning 1. the
latest download webpage and 2. the potential issue.


> Could we maybe wait until such reasons pop up for 1.4.0?  Or have a new
> standard installer independent of the Guix release?

As every program, bugs are around. ;-)  I mean, I do not see why we
should wait.


> Mathieu will know better, but I think there were few issues with 1.3.0
> (UUID checks in commit f5d9d6ec68f78f5651bd5a698f489ab57bf77d5d) but
> latest has better logging.  On the other hand, the latest installer had
> few new bugs except missing mkfs.ext4.

From my opinion, the latest installer has less bugs than the v1.3 one. :-)


>> Therefore, I still propose on the webpage <https://guix.gnu.org/en/download/>
>> to add this sentence:
>>
>> These images are well-tested released images, and since Guix follows
>> rolling release model, the [latest development images are
>> here](https://guix.gnu.org/en/download/latest/).
>
> Why mention rolling release?

It is a proposal. :-) I do not know if it is the correct wording.  The
idea is to explain that the installer is continuously improved.  The
model is not stable (release) vs unstable (development) but instead
frozen (release) vs latest.  And mention (point) this latest webpage.

I think this proposal about mentioning the latest download webpage from
the current release webpage improves about discoverability.  And it
keeps the usual entry point with the current release – for sure, it is
well-tested and it should be the recommended way for installing.

Cheers,
simon




  reply	other threads:[~2022-12-06 17:46 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-04 19:50 [bug#59822] [PATCH guix-artwork] website: base: home: Add 'DOWNLOAD LATEST' button ( via Guix-patches via
2022-12-04 21:50 ` pelzflorian (Florian Pelz)
2022-12-04 21:58   ` pelzflorian (Florian Pelz)
2022-12-04 22:03     ` pelzflorian (Florian Pelz)
2022-12-05  7:02       ` ( via Guix-patches via
2022-12-05  8:00         ` pelzflorian (Florian Pelz)
2022-12-05  9:00           ` zimoun
2022-12-05 17:06             ` pelzflorian (Florian Pelz)
2022-12-05 17:41               ` pelzflorian (Florian Pelz)
2022-12-06 11:22               ` zimoun
2022-12-06 16:33                 ` pelzflorian (Florian Pelz)
2022-12-06 17:45                   ` zimoun [this message]
2022-12-07 14:26                     ` pelzflorian (Florian Pelz)
2022-12-08  9:36                       ` pelzflorian (Florian Pelz)
2022-12-08 10:12                         ` zimoun
2022-12-08 11:50                           ` bug#59822: " pelzflorian (Florian Pelz)
2022-12-08 15:49                             ` [bug#59822] " ( via Guix-patches via
2022-12-05 16:51           ` ( via Guix-patches via
2022-12-08 16:44             ` pelzflorian (Florian Pelz)
2022-12-08 16:46               ` ( via Guix-patches via
2022-12-08 18:10               ` zimoun
2022-12-08 19:44                 ` pelzflorian (Florian Pelz)
2022-12-21 13:40                 ` Ludovic Courtès
2022-12-30 12:21                   ` zimoun
2022-12-31 15:43                     ` pelzflorian (Florian Pelz)
2023-01-06 22:53                     ` Ludovic Courtès
2023-01-07  7:29                       ` pelzflorian (Florian Pelz)
2023-01-09 10:13                         ` Simon Tournier
2023-01-09 19:35                           ` pelzflorian (Florian Pelz)
2023-01-11 16:11                             ` Simon Tournier
2023-01-12 17:56                               ` pelzflorian (Florian Pelz)
2022-12-05  7:01   ` ( via Guix-patches via

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=86pmcwifyu.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=59822@debbugs.gnu.org \
    --cc=paren@disroot.org \
    --cc=pelzflorian@pelzflorian.de \
    /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.