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@xxxxxxxxxxxxxxxxxxxxxxx/), 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 _______________________________________________ websites mailing list -- websites@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to websites-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/websites@xxxxxxxxxxxxxxxxxxxxxxx
