August 2020 - websites - Fedora Mailing-Lists

[fedora-websites] Issue #955: Instructions for Mac install

by Erez Tavor

erezpitke reported a new issue against the project: `fedora-websites` that you are following: `` For those that have Mac detected a note at the bottom on how to install after the image below is shown <!!image> (Preferences > Security & Privacy > General > Allow Apps downloaded from unidentified developers) There is a link below the download button asking - 'Need instructions? and it brings you to a section with no instructions.. Of course, it would be great if the file was from an 'identified developer' `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-websites/issue/955

3 years, 2 months

4
3
0 / 0

[fedora-websites] Issue #1030: Fedoramagazine should provide HSTS

by Christoph Kern

sheogorath reported a new issue against the project: `fedora-websites` that you are following: `` The Fedoramagazine websites doesn't provide a [HSTS header](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security). It is a security best practice to provide HSTS these days in order to have everyone using HTTPS by default and prevent downgrade attacks. https://hstspreload.org/?domain=fedoramagazine.org `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-websites/issue/1030

3 years, 3 months

3
4
0 / 0

[fedora-websites] Issue #964: Download page for Fedora CoreOS

by Benjamin Gilbert

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.f..., 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

3 years, 3 months

5
11
0 / 0

[fedora-websites] Issue #1032: labs.fedoraproject.org does not show labs on mobile

by Ankur Sinha

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

3 years, 3 months

2
3
0 / 0

[fedora-websites] Issue #1042: Content for infographic to highlight accomplishments of Fedora Web!

by Smera Goel

smeragoel reported a new issue against the project: `fedora-websites` that you are following: `` As a thank you for all the efforts Fedora Web puts in building and maintaining websites for the Fedora Project, the design team is working on a set of infographics to highlight the accomplishments of all the people who worked and contributed to Fedora in the past year. For this, we request you to share accomplishments, stories, metrics etc. of individuals and/or teams in your group! It can be anything from the number of new websites added to easter eggs hidden in websites. Looking forward to reading amazing things! :D `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-websites/issue/1042

3 years, 3 months

2
1
0 / 0

[fedora-websites] Issue #946: Expected editions status for F30

by Matthew Miller

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

3 years, 3 months

3
4
0 / 0

[fedora-websites] Issue #1027: Dead link in footer :download Fedora Atomic

by Sanne Grinovero

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

3 years, 3 months

3
3
0 / 0

[fedora-websites] Issue #1037: Link of "Get Fedora Atomic" in footer is no longer found at destination page.

by Ooyama Yosiyuki

sujiniku reported a new issue against the project: `fedora-websites` that you are following: ``  The footer of https://spins.fedoraproject.org/en/ , Although "Get Fedora Atomic" is exist, but the target page is "Not Found". Because of changing of CoreOS . https://getfedora.org/en/coreos?stream=stable We should change the Atomic link in the footer to CoreOS link . `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-websites/issue/1037

3 years, 3 months

3
3
0 / 0

[fedora-websites] Issue #1048: alt.fedoraproject.org: alternative download page: Netinstall is marketed as Server edition

by Flo H

augenauf reported a new issue against the project: `fedora-websites` that you are following: `` I noted that on https://alt.fedoraproject.org/en/ that the netinstall image is marketed as Server edition. I think this is misleading and playing down the huge potential of this image. As far as I am aware, the netinstall image, by default, isn't a certain edition. It is rather a tool to install any edition the user may want. Should we change that? `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-websites/issue/1048

3 years, 3 months

4
8
0 / 0

[fedora-websites] Issue #1045: start.fp.o parses the Magazine RSS feed incorrectly when an article has embedded video

by Ben Cotton

bcotton reported a new issue against the project: `fedora-websites` that you are following: `` The magfeed.py script blindly takes the first `<enclosure>` element to use as the thumbnail for start.fedoraproject.org. This is fine in most cases, but if the article has embedded video, we end up with a blank thumbnail. The RSS feed in that case contains multiple enclosure elements and the featured image is listed last. <enclosure url="https://fedoramagazine.org/wp-content/uploads/2020/06/Screencast-from-25-..." length="410087" type="video/webm"/> <enclosure url="https://fedoramagazine.org/wp-content/uploads/2020/06/Screencast-from-25-..." length="388173" type="video/webm"/> <enclosure url="https://fedoramagazine.org/wp-content/uploads/2020/06/Screencast-from-24-..." length="398605" type="video/webm"/> <enclosure url="https://fedoramagazine.org/wp-content/uploads/2020/06/Screencast-from-25-..." length="1964954" type="video/webm"/> <enclosure url="https://fedoramagazine.org/wp-content/uploads/2020/07/networkansible-300x..." length="36634" type="image/jpg"/> We want it to only use enclosures with a type of `"image/jpg"` (note that the RSS feed uses this type for both jpg and png images) to prevent this. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-websites/issue/1045

3 years, 8 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

websites August 2020