robyduck reported a new issue against the project: `fedora-websites` that you are following:
``
We have 10 days before Readiness meeting to setup the websites for F27 Beta release, although the state of F27 Beta is bad, so we might expect to slip a bit. I branched f27-beta right now, so pull the new branch before start working on the beta release.
To do list:
* Pyrhon Classroom has also ARM images, we should add them to arm.fp.o and make a new section for labs. Design folks did the icon already. #719
* update globalvars
* update docs links (we need to do that also on master!!) on all websites #722
* add checksums
* update image sizes
* check if builds are done for the actual spins and labs, if not remove them
* check all download links, we don't expect changes in the paths
* at some point check if we can build getfedora and have atomic images
We do not need to freeze translations this time, so we will just merge at release date and all should be fine. But we have to update all POT files *and* po files in our repo. Would be nice to have always an updated content when we tag a release.
Please ask, also by adding a comment if you want to work on something or if you have doubts. All pushes need to go to f27-beta.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/725
robyduck reported a new issue against the project: `fedora-websites` that you are following:
``
Due to an [https://pagure.io/pungi/issue/744](issue in pungi) we don't have any checksum files for 32 bit images, except for Server. Looking at nearer, we saw that i686 ISO files have not been built at all, while the i686 netinstall images are there, but they are missing checksums.
The fact that most 32bit images on our websites are normal i686 ISO files will already drop many of the links, specially in labs.fp.o and spins.fp.o.
So, the question is: Do we want to keep 32bit netinst images on Beta pages even without checksums or do we want to drop them completely?
* From a technical side, it makes totally sense to drop them, because we would have a security issue otherwise
* From a marketing POV, we should consider that:
a) F27 Beta is already special due to the missing F27 Beta Server image (Modular Server will come later)
b) If we drop them totally, this could produce a message like "Did you drop 32 bit support?"
Persoanlly I am fine with bot (it is a Beta release and just for a few weeks), but it is important for us to know which way we want to go for.
So, I would like to have inputs from @mattdm or @pfrields before taking any decision here. Thanks!
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/744
robyduck added a new comment to an issue you are following:
``
> If we can't get an MVP of hubs up, can we look to create a non-brochure landing page that will hopefully rank higher?
And what do you want to target with that page? A remake of fedoraroject.org??
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/695
bex added a new comment to an issue you are following:
``
If we can't get an MVP of hubs up, can we look to create a non-brochure landing page that will hopefully rank higher?
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/695
augenauf reported a new issue against the project: `fedora-websites` that you are following:
``
Download of Fedora Media Writer for Windows Clients shows wrong file size, see https://getfedora.org/en/workstation/download/ , click View all platform downloads.
In addition, could those downloads be equipped with checksums for file verification?
The links on getfedora could also point to https://github.com/MartinBriza/MediaWriter/releases/latest where downloads for "all" platforms are available in their latest version.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/733