websites February 2022

websites@lists.fedoraproject.org

10 discussions

[fedora-websites] Issue #771: Fedoracommunity.org is not fully loaded in Zanata
by Zdenek Chmelar 03 Jun '22

03 Jun '22

zdenek reported a new issue against the project: `fedora-websites` that you are following: `` Topic discussed in translation mailing list - there are strings in Fedoracommunity.org that cannot be loaded in Zanata due to genshi mistakes in the web source code and thanks that can't be translated. Please fix those mistakes to allow the scripts an upload of the strings to Zanata. Thank you Z. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-websites/issue/771

3 4

[fedora-websites] Issue #821: Recreate a script that only shows languages translated over 25%
by Robert Mayr 03 Jun '22

03 Jun '22

robyduck reported a new issue against the project: `fedora-websites` that you are following: `` We had this functionality on transifex and it was easy to set up. Now on zanata we have much more languages, but most of them son't have more than 5-10% translated strings. We should recreate our script which doesn't show languages if they are not translated for at least 25%. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-websites/issue/821

4 4

[fedora-websites] Issue #941: alt downloads french: "netinstall" is translated and breaks the design
by Anisse Astier 03 Jun '22

03 Jun '22

anisse reported a new issue against the project: `fedora-websites` that you are following: `` On https://alt.fedoraproject.org/fr/alt/ "netinstall" is translated and its long translation breaks the design of the page. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-websites/issue/941

5 9

[fedora-websites] Issue #961: Minor content issues with flocktofedora.org
by David Yaffe 03 Jun '22

03 Jun '22

dyaffe reported a new issue against the project: `fedora-websites` that you are following: `` Three are some minor content issue with [https://flocktofedora.org](https://flocktofedora.org). Using page source for line numbers: 1. Under **WHAT WILL WE DO AT FLOCK?** - There is an extra 'm' at the end of the 'Communicate the Fedora Strategy' Bullet (line 82) 2. Under **Download**, 'Get Fedora Atomic' should be updated to 'Get Fedora Silverblue'. The corresponding link also needs to be updated. (line 359) 3. Under **Support**, The link for 'Installation Guide' should be updated for Fedora 30. (Line 375) `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-websites/issue/961

4 6

[fedora-websites] Issue #969: flocktofedora.org is not fully mobile ready
by Rafał Lużyński 03 Jun '22

03 Jun '22

rluzynski reported a new issue against the project: `fedora-websites` that you are following: `` Screenshot by @x3mboy (thank you). This explains all. <!!image> `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-websites/issue/969

5 6

[fedora-websites] Issue #1117: Update README.md
by Ojong Enow 03 Jun '22

03 Jun '22

d-enow reported a new issue against the project: `fedora-websites` that you are following: `` The README.md file can be updated to include details that would make it easier for new contributors to get started such as how to submit a first pull request. Also, the setup procedure is slightly different for other Unix-based distros like Debian. This can be included too for non-fedora users. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-websites/issue/1117

2 3

[fedora-websites] Issue #1059: F34 Final release updates
by Ben Cotton 03 Jun '22

03 Jun '22

bcotton reported a new issue against the project: `fedora-websites` that you are following: `` Creating a tracking issue since we have F34 content queued `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-websites/issue/1059

6 6

[fedora-websites] Issue #1115: Fedora 34 Everything ISO checksum under ARM aarch64 Architecture
by Juwana Zerman 17 May '22

17 May '22

jzerman reported a new issue against the project: `fedora-websites` that you are following: `` All of the images under the ARM arrch64 Architecture section at https://alt.fedoraproject.org/alt/ when you click verify it goes to https://alt.fedoraproject.org/en/verify.html and you're able to choose your version and verify your image. However, the Everything image isn't located on that verify page. It links to it's own checksum page which has a broken link at https://getfedora.org/static/checksums/Fedora-Everything-34-1.2-aarch64-CHE…. The correct link seems to be at https://getfedora.org/static/checksums/34/iso/Fedora-Everything-34-1.2-aarc…. This link needs to be updated. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-websites/issue/1115

2 4

[fedora-websites] Issue #1078: Copyright Year on Website Pages!
by Ardit Dani 17 May '22

17 May '22

ard1t reported a new issue against the project: `fedora-websites` that you are following: `` © 2020 Red Hat, Inc. and others. <!!image> `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-websites/issue/1078

6 8

[fedora-websites] Issue #1123: Change default branch to main
by Justin W. Flory 17 May '22

17 May '22

jflory7 reported a new issue against the project: `fedora-websites` that you are following: `` # Summary Change default Pagure git branch from `master` to `main` and recreate `master` as a branch alias # Background Fedora Linux 34 [switched default git branches to `main`](https://fedoraproject.org/wiki/Changes/GitRepos-master-to-main) as a Self-Contained Change. Many repositories use `main` as the default branch. In addition to being courteous, kind, and respectful, there are a few places that mention this branch to use `main` already, so we should take some form of action with the [Pagure git branch aliases](https://docs.pagure.org/pagure/changelog.html#id5). # Details 1. Create a new main branch checked out from master 1. Change Pagure default branch to main 1. Delete master branch 1. Recreate master branch as a Pagure branch alias to main The only risk to this change is what the impact will be to all opened Pull Requests. In `#websites:fedora.im`, we were thinking to work through the backlog of Pull Requests first in order to make this change safely. # Outcome * Syncs up with other distro-wide efforts to change default branches * Use git branch aliases to allow both `master` and `main` to serve the same content `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-websites/issue/1123

4 7

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

websites February 2022