Bug 2037222 - [getfedora.org] Fedora IoT download formats are not documented
Summary: [getfedora.org] Fedora IoT download formats are not documented
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora Documentation
Classification: Retired
Component: homepage
Version: devel
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Petr Bokoc
QA Contact: Fedora Docs QA
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-05 09:47 UTC by Pierre Prinetti
Modified: 2024-05-21 10:41 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-21 10:41:50 UTC
Embargoed:


Attachments (Terms of Use)

Description Pierre Prinetti 2022-01-05 09:47:32 UTC
Description of problem:
On the Fedora IoT downloads page[1], I am presented with two formats: "Raw Images" versus "Installer ISOs". It is not explained why I would choose one over the other.

[1]: https://getfedora.org/en/iot/download/


Version-Release number of selected component (if applicable):
Fedora IoT 35


How I got there:
1. I searched 'Fedora iot' in my favourite search engine
2. I landed on 'https://getfedora.org/iot/'
3. I clicked 'Download' in the top right-hand corner of the page


Actual results:
I am presented the two format options without any explanation


Expected results:
I am presented the download format that matches the documentation


Additional info:
In the Fedora IoT documentation[2], neither the words "Raw Image" nor "Installer ISO" seem to be ever mentioned.
In both the "Getting Started" sections "Setting up a Virtual Machine" and "Setting up a Physical Device", the command-line examples refer to the downloaded file as `Ferora-IoT-[version].raw.xz` (and not .iso).

[2]: https://docs.fedoraproject.org/en-US/iot/

Comment 1 Petr Bokoc 2024-05-21 10:41:50 UTC
I'm working on closing the Fedora Documentation component in bugzilla, so I moved this to Gitlab: https://gitlab.com/fedora/websites-apps/fedora-websites/fedora-websites-3.0/-/issues/296


Note You need to log in before you can comment on or make changes to this bug.