From: zimoun <zimon.toutoune@gmail.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>,
"(" <paren@disroot.org>
Cc: 59822@debbugs.gnu.org
Subject: [bug#59822] [PATCH guix-artwork] website: base: home: Add 'DOWNLOAD LATEST' button.
Date: Mon, 05 Dec 2022 10:00:06 +0100 [thread overview]
Message-ID: <86tu2a444p.fsf@gmail.com> (raw)
In-Reply-To: <878rjm9t5l.fsf@pelzflorian.de>
Hi,
On Mon, 05 Dec 2022 at 09:00, "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> wrote:
> So maybe better not lead users to the untested version.
>
> Agreed? Can I close the bug without applying the patch?
Well, maybe the « latest » could be more discoverable. For instance,
when an user is here:
https://guix.gnu.org/
then they click to the button « DOWNLOAD v1.3.0 ». Moreover nothing
mention upfront the latest version. The user has to click on top right
Download and select «Latest» – probably not done when they have already
seen the button. I agree that another «Download latest» on the
frontpage could be confusing.
Instead, I propose, on the webpage,
https://guix.gnu.org/en/download/
and in the header,
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.
this sentence could be added,
--8<---------------cut here---------------start------------->8---
These images are well-tested released images, and since Guix follows
rolling release model, you might prefer to use [latest images](https://guix.gnu.org/en/download/latest/)
--8<---------------cut here---------------end--------------->8---
WDYT?
Cheers,
simon
next prev parent reply other threads:[~2022-12-05 9:01 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 [this message]
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
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=86tu2a444p.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.