bgilbert reported a new issue against the project: `fedora-websites` that you are following:
``
With Fedora CoreOS entering preview within the next month or two, we'll need a download page on getfedora.org, and that page will need several unusual elements:
- All release image URLs, cloud image IDs, etc., will come from [stream metadata](https://github.com/coreos/fedora-coreos-tracker/issues/98) JSON documents which are fetched client-side and rendered into the page. That metadata will be hosted alongside the artifacts, and will change at least every two weeks.
- We'll need to link to release images for three different streams: `stable`, `testing`, and `next`. We'll need language explaining the difference (similar to [this](https://coreos.com/releases/)), and a recommendation to run a small percentage of nodes on `testing` and `next` and report problems to our [issue tracker](https://github.com/coreos/fedora-coreos-tracker/issues).
- Each OS platform will have a separate release image. There will be an initial set of platforms, and more will be added over time:
- Bare metal and virtualized images (e.g. QEMU, VMware) will have downloadable artifacts, with corresponding hashes and GPG signatures. Hashes will come from stream metadata; detached signatures will be a separate artifact.
- Cloud images will have image identifiers (e.g. AMI IDs on AWS) and corresponding instructions (such as a launch button or sample command line) for running the image.
- Preferably, we'd include a recommendation to subscribe to the [coreos-status mailing list](https://lists.fedoraproject.org/archives/list/coreos-status@lists.fed…, to ensure we have a way to send operational notifications to our users.
The above is a lot of requirements, I know. It might be too much to fit on one page, even with most of the content shown conditionally; I'd like some input there. CoreOS Container Linux addressed a similar problem by having [distinct pages for each platform](https://coreos.com/os/docs/latest/#running-coreos), which was a maintenance nightmare and probably too complex. I'm happy to work with folks to arrive at something implementable.
As to timing: this doesn't _need_ to be ready for the preview release in the next month or two, but it would help. (If that's infeasible, the Fedora CoreOS team will need to put together a temporary page elsewhere with substantially the items listed above.) The page must be ready before Fedora CoreOS goes stable, which will be ~6 months after the preview release.
Thanks!
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/964
ankursinha reported a new issue against the project: `fedora-websites` that you are following:
``
Hello,
Just noticed this on my phone: when accessing labs.fp.o there, the spins aren't show. We skip from the "Fedora 32 released .." bit straight to "What is Fedora labs?".
<!!image>
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/1032
mattdm reported a new issue against the project: `fedora-websites` that you are following:
``
Putting this here in one ticket for reference:
* Fedora Workstation as normal
* Fedora Server: same, but will *also* include Fedora Cloud (but not Atomic/CoreOS)
* Fedora Atomic: no longer an edition. As I understand it, current version will be supported a little longer yet but we don't want to encourage new installs
* Fedora CoreOS: not _quite_ ready to be an edition, but we want to launch as an edition shortly after. (June?)
* Fedora IoT: also not quite ready to be an edition. Will be at https://iot.fedoraproject.org/. Also plan to launch as an edition in around June.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/946
sanne reported a new issue against the project: `fedora-websites` that you are following:
``
On page https://alt.fedoraproject.org/ the footer contains a link "Get Fedora Atomic", which points to a 404.
Not sure what needs to be done, probably just removed?
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/1027
catanzaro reported a new issue against the project: `fedora-websites` that you are following:
``
https://alt.fedoraproject.org/alt/ looks bad except at large window sizes. Here's a screenshot at 1169x1019 with the rendering of the download list clearly broken:
<!!image>
Here it is again a little bit wider, at 1291x1019. Now it looks OK:
<!!image>
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/1023
bcotton reported a new issue against the project: `fedora-websites` that you are following:
``
Opened by @ankursinha as fedora-web/websites#71:
Hello,
The Comp-Neuro lab was accepted as a change for F32. We need to set up a page for it on labs.fp.o. How would we go about this please?
Cheers!
cc the neuro-sig @major @bt0dotninja @alciregi @mhough @zbyszek @sagitter @gicmo @blackfile @dan1mal @lbazan @sagitter @victortyau @sergiopr @terezahl @tanvi @sergiopr
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/1010
bcotton reported a new issue against the project: `fedora-websites` that you are following:
``
Jam has been brought back to life for F32, so we need to bring it back to the website.
cc @eeickmeyer
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/1031
Does anyone here know where the sources for spins.fedoraproject.org are? I've been searching through pagure.io/fedora-web, github.com/fedora-infra, and other places I would expect to find the sources for them, but I've been unable to locate them. I'm interested in making the whole thing look less dated (e.g. the KDE spin page is displaying a years-old screenshot and displays decade-old icons.)