From: Felix Lechner via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 51000@debbugs.gnu.org
Cc: John Kehayias <john.kehayias@protonmail.com>,
Tobias Geerinckx-Rice <me@tobias.gr>,
Efraim Flashner <efraim@flashner.co.il>
Subject: bug#51000: Please drop web manuals for released versions
Date: Sun, 21 May 2023 18:59:20 -0700 [thread overview]
Message-ID: <CAFHYt549HO9d1W_=pZoMEQyQZS1iE25AAk2JUcoYKpmQmqY2ww@mail.gmail.com> (raw)
In-Reply-To: <87ilydycps.fsf@nckx>
Hi,
> Here is an untested patch
Guix suffers from an unhelpful anachronism that search engines
consistently rank historical versions of the Reference Manual [1]
above the latest edition. [2] It's probably because third-parties link
to historical versions more often than they do to the current version.
Please drop the historical versions.
Historical versions are irrelevant for current users and should only
be shipped on installation media. The current edition is only a 'guix
pull' away—a command we encourage widely.
As an example for the grave but unnecessary confusion, the manual
generally perceived as official lists the incorrect email address
guix-patches@debbugs.gnu.org as a way to contribute to Guix. [3]
Let's not put stumbling blocks before the blind, please. I beg you,
let's think of our fellow human beings. Thanks!
Kind regards,
Felix Lechner
[1] https://guix.gnu.org/manual/en/guix.html
[2] https://guix.gnu.org/en/manual/devel/en/guix.html
[3] https://guix.gnu.org/en/manual/en/guix.html#Multiple-Patches-1
next prev parent reply other threads:[~2023-05-22 2:01 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
2021-10-04 6:31 ` Efraim Flashner
2021-10-04 6:58 ` zimoun
2023-05-22 1:59 ` Felix Lechner via Bug reports for GNU Guix [this message]
2023-09-27 9:26 ` 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='CAFHYt549HO9d1W_=pZoMEQyQZS1iE25AAk2JUcoYKpmQmqY2ww@mail.gmail.com' \
--to=bug-guix@gnu.org \
--cc=51000@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=felix.lechner@lease-up.com \
--cc=john.kehayias@protonmail.com \
--cc=me@tobias.gr \
/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).