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
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
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
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
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
ryanlerch reported a new issue against the project: `fedora-websites` that you are following:
``
Currently, we use a bunch of scripts and Make to generate the websites. Furthermore, we use genshi tempates as the basis of the sites.
This system is quite old, and has some challenges. From a template / theming point of view, there are many times where templates contain duplicated code, and other issues that make it hard for community members to jump into helping out on the websites.
The idea of this ticket is to facilitate discussion on issues of the current process, and progress through to thinking up solutions.
Ultimately, hopefully, we can use this ticket as a tracking ticket for tasks as we progress.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/942
langdon reported a new issue against the project: `fedora-websites` that you are following:
``
Would be nice if "Fedora 29 Beta released! Test it in the Download section." linked to something like https://spins.fedoraproject.org/prerelease.html. Or, failing that, had a section on the page about the beta.
If you see this sentence and search for "beta" in the page you find nothing. If you search for "download" you only find the download block in the footer which doesn't seem relevant.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/882
ryanlerch reported a new issue against the project: `fedora-websites` that you are following:
``
fudcon.fedoraproject.org is no longer in use, and just redirects to the flock website.
IMHO, we should remove it from the repo, since it is no longer in use.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/939
ryanlerch reported a new issue against the project: `fedora-websites` that you are following:
``
fedorahosted.org is now just a redirect to the wiki page. we should remove it from the repo.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/940
sinnykumari reported a new issue against the project: `fedora-websites` that you are following:
``
In the favor of upcoming Fedora CoreOS, Atomic Host last release is based on Fedora 29 https://lists.projectatomic.io/projectatomic-archives/atomic-announce/2019-… .
This ticket is to make sure that we stay on Fedora 29 as major version for future Fedora Atomic Host Two Week releases instead of moving to Fedora 30.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/945
zbyszek reported a new issue against the project: `fedora-websites` that you are following:
``
The licenses for ISOs and other stuff that Fedora Project produces is not specified on the download website. It should be prominently visible. I think there should be a short sentence like
> Fedora is always free for anyone to use, modify, and distribute. It is a compilation of software packages, each under its own license. Images that can be downloaded here are available under the combination of licenses of the constituent software packages and the license of the Fedora project itself. See [https://fedoraproject.org/wiki/Legal:Licenses/LicenseAgreement#License]
https://get.adobe.com/flashplayer/ is a good example of how this could be done. It has three panes, and the third one is "terms & conditons" and includes an obvious link to a license.
See https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org….
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/889
charnik reported a new issue against the project: `fedora-websites` that you are following:
``
Translated message "Choose Freedom. Choose Fedora" in Greek use different font family than the rest Greek text and English text in this page. Result is not aesthetically good. Look at the image:
<!!image>
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/787
jibecfed reported a new issue against the project: `fedora-websites` that you are following:
``
we recently had the luck to get translation for Gujarati language, but I couldn't switch to the language to help the contributor. Can you please add a language button as we have for other websites?
http://fedoracommunity.org/en/emea
thanks a lot
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/761
jibecfed reported a new issue against the project: `fedora-websites` that you are following:
``
Hello, the Fedora project migrates its translation platform to Weblate [1].
This tool directly interact with your git repository, and requires us to know:
* [mandatory] which branch is your development branch?
* [mandatory] have you merged latest translation from Zanata and locked the project?
* [info] Weblate will handle updates when pot file changes, don't edit po files for this [2]
* [optional] what is the license of translation? (please use a code from https://spdx.org/licenses/)
* [optional] do you have any announcement/warning you would like to display to the translators? (it will be displayed in Weblate)
* [optional] do you need us to activate any specific checks? (this is a setting per component [3])
* [optional] do you need us to automatically detect new translation files? (typical usecase: website translation with one translation file per page)
Please note:
* For github and gitlab hosted projects, Weblate open pull request. For other git hosting, you'll have to add a key to allow commits.
* In Weblate's vocable, one project is a group of component. Each component is a translation file. You can have many projects or many components or both.
* You can change your mind over time, just reach trans(a)lists.fedoraproject.org
[1] https://communityblog.fedoraproject.org/fedora-localization-platform-migrat…
[2] https://docs.weblate.org/en/latest/admin/continuous.html#avoiding-merge-con…
[3] https://docs.weblate.org/en/latest/user/checks.html#translation-checks
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/1013
sharkcz reported a new issue against the project: `fedora-websites` that you are following:
``
Please migrate the build system to Python3 as Python2 is a no-go in newer Fedora releases.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/1009
kevin reported a new issue against the project: `fedora-websites` that you are following:
``
There does seem to be a cookie, I am not sure what it's for, but we should either drop it or figure out how to make it not appear like a tracking cookie to firefox.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/947
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
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
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
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
adamwill reported a new issue against the project: `fedora-websites` that you are following:
``
Fedora 30 Final RC2 (RC-1.2) was the compose we signed off as the final release. Unfortunately, this compose was missing several images that failed due to download blips in the compose process. These include:
x86_64 Design Suite live
x86_64 Python Classroom live
x86_64 LXDE live
armhfp MATE image
armhfp LXqt image
and a few other less important ones. We have a plan to - as we have done a few times before - take nightly builds from composes after the Final packages are pushed stable (so the contents should be identical to the RC) and ship them alongside the RC contents in an 'unofficial' directory, and would like to ensure these images are linked from the download site.
This ticket is kinda intended to track this whole process, so tagging the relevant releng folks: @kevin @mohanboddu
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/951
fwolff reported a new issue against the project: `fedora-websites` that you are following:
``
I just uploaded a (mostly) complete translation of getfedora.org to Zanata. I didn't see any instructions on how new languages are added, so I thought I would create an issue here. I'll be happy to review the translations in context once it is deployed.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/965
Hello,
My name is Douglas and I'm a Computer Science student. I am currently
studying HTML, CSS and JavaScript. I do not have experience in the field
and also do not work on it.
Fellow website-ers,
Please see Jean-Baptiste's questions on fedora-websites#1014[1]. Does
anyone have answers for him? Does anyone object to merging the pull request?
[1] https://pagure.io/fedora-websites/pull-request/1014
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis