From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] RFC: add a downloads.md page
Date: Wed, 19 Aug 2020 12:20:56 +0000 [thread overview]
Message-ID: <CAFSF3XOh=9PQ_c1HbbcLv8p9H+owTvQeiG9hF=RH1XQ2GobjDg@mail.gmail.com> (raw)
In-Reply-To: <158A09494BC07582889006A200849F02@ewsd.inri.net>
big complaint: omission of "isohybrid"
On 8/19/20, sl@stanleylieber.com <sl@stanleylieber.com> wrote:
> here's what i did:
>
> - integrated most of the requested information into the latest and all
> future release announcements. this seems like a good place for the
> information, and alleviates having to duplicate it anywhere else on
> the site (except for more detailed instructions in the fqa; see
> below). note: this still requires loading some images, but is the
> difference in load time really that meaningful?
>
> - download/ added to the top bar on all 9front sites (redirects to
> releases/).
>
> - bugs.9front.org removed from the top bar on all 9front sites (nobody
> complained when the bugs.9front.org front page has been defunct for
> several years). which reminds me: http://9front.org/bugtracker
>
> - iso/ removed from the sidebar (redundant).
>
> - releases/ moved from About: to Download: on the sidebar.
>
> - kept the link to the dash 1 under Download:, because why not have it
> there? unless we create a long list of all the available files to be
> downloaded, we're never going to have "one click" downloading of
> bootable files on the front page. if there is some compelling
> argument for removing more helpful links from the sidebar, please let
> me know.
>
> here's what needs to be done:
>
> - someone write a patch for fqa4 detailing specific instructions for
> creating bootable media in all the present forms we support. we
> already have old instructions, but they were never updated to reflect
> the changes made since 2016. once that's done, we can also link to it
> specifically in the release announcement.
>
> - fqa documentation of rpi stuff is so far outdated as to be useless.
>
> it may seem like i'm parsing this awfully finely here, but i'm not
> sure how much extra effort is justified to satisfy the
> "zero-to-installed" metric for users incapable of locating the
> .iso/.img files, or for ones incapable of conceiving what to do with
> them once they've found them. the location of the files has never
> been a mystery, and what to do with them is the same thing you'd do
> with an .iso or .img from any operating system. i do think the
> instructions are good to provide, i'm just not sure it all belongs on
> the download page, be that the primary or auxiliary variety.
>
> anyway, let me know if this sucks.
>
> sl
>
next prev parent reply other threads:[~2020-08-19 12:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 20:27 hiro
2020-08-18 22:20 ` [9front] " ori
2020-08-18 22:50 ` Stanley Lieber
2020-08-18 23:08 ` Stanley Lieber
2020-08-18 23:34 ` Stanley Lieber
2020-08-18 23:40 ` Kurt H Maier
2020-08-19 3:52 ` sl
[not found] ` <158A09494BC07582889006A200849F02@ewsd.inri.net>
2020-08-19 12:20 ` hiro [this message]
2020-08-19 13:20 ` Stanley Lieber
2020-08-19 13:25 ` hiro
2020-08-19 13:37 ` Stanley Lieber
2020-08-19 13:53 ` hiro
2020-08-19 20:01 ` hiro
2020-08-19 21:59 ` Stanley Lieber
2020-08-20 2:14 ` sl
[not found] ` <54754B562FB01625084E1BA75A9A12C3@ewsd.inri.net>
2020-08-20 2:18 ` hiro
2020-08-20 2:24 ` hiro
2020-08-20 2:30 ` hiro
2020-08-20 2:46 ` ori
2020-08-19 23:12 ` hiro
2020-08-19 23:40 ` Stanley Lieber
2020-08-20 2:14 ` hiro
2020-08-21 17:24 ` Ethan Gardener
2020-08-22 12:59 ` hiro
2020-08-22 15:34 ` Stanley Lieber
2020-08-19 12:15 ` hiro
2020-08-19 12:49 ` telephil9
2020-08-19 13:02 ` hiro
2020-08-19 13:06 ` hiro
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='CAFSF3XOh=9PQ_c1HbbcLv8p9H+owTvQeiG9hF=RH1XQ2GobjDg@mail.gmail.com' \
--to=23hiro@gmail.com \
--cc=9front@9front.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.
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 NNTP newsgroup(s).