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