[fedora-websites] #274: UEFI consistency warning
by fedora-badges
#274: UEFI consistency warning
--------------------------+-----------------------
Reporter: immanetize | Owner: webmaster
Type: enhancement | Status: new
Priority: critical | Milestone: Fedora 21
Component: get.fp.o | Keywords:
Blocked By: | Blocking:
--------------------------+-----------------------
Please add a prominent warning advising users to be consistent in their
usage of UEFI or CSM (BIOS) style installation when booting multiple
operating systems. Whether by misconception, firmware quirks, poor media
creation tools, or accident, users have been consistently reporting issues
with booting their Windows installations after installing Fedora. I have
observed that a significant number of these issues relate to the user
"disabling UEFI" to install Fedora, then discovering that their UEFI
installation of Windows no longer boots. Browse through
ask.fedoraproject.org for Windows related questions, and you'll see how
prevalent these issues are.
There is documentation under development to further explain the issues
involved, but it would be hugely beneficial to have a simple warning to be
consistent displayed when the Fedora image is downloaded. Maybe in
download-splash?
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/274>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
7 years, 6 months
[fedora-websites] #241: Change docs link to redirected one to prevent hard release number usage
by fedora-badges
#241: Change docs link to redirected one to prevent hard release number usage
--------------------------+-----------------------
Reporter: shaiton | Owner: webmaster
Type: enhancement | Status: new
Priority: major | Milestone: ASAP
Component: General | Keywords:
Blocked By: | Blocking:
--------------------------+-----------------------
We should use the redirect as described in puppet:/modules/fedora-
docs/files/redirects.conf instead of linking to specific doc release.
Example:
replace "/en-US/Fedora/16/html/Installation_Guide" occurrences by
"/install-guide".
actual redirect are:
{{{
RewriteRule /accessibility-guide /en-
US/Fedora/16/html/Accessibility_Guide [R=301]
RewriteRule /deployment-guide /en-
US/Fedora/15/html/Deployment_Guide [R=301]
RewriteRule /install-guide /en-
US/Fedora/19/html/Installation_Guide [R=301]
RewriteRule /installation-quick-start-guide /en-
US/Fedora/19/html/Installation_Quick_Start_Guide [R=301]
RewriteRule /readme-burning-isos /en-
US/Fedora/19/html/Burning_ISO_images_to_disc [R=301]
RewriteRule /readme-live-image /en-
US/Fedora/15/html/Fedora_Live_Images [R=301]
RewriteRule /security-guide /en-
US/Fedora/19/html/Security_Guide [R=301]
RewriteRule /selinux-faq /en-
US/Fedora/13/html/SELinux_FAQ [R=301]
RewriteRule /selinux-managing-confined-services-guide /en-
US/Fedora/13/html/Managing_Confined_Services [R=301]
RewriteRule /selinux-user-guide /en-US/Fedora/13/html
/Security-Enhanced_Linux [R=301]
RewriteRule /technical-notes /en-
US/Fedora/16/html/Technical_Notes [R=301]
RewriteRule /user-guide /en-
US/Fedora/14/html/User_Guide [R=301]
RewriteRule /virtualization-guide /en-
US/Fedora/13/html/Virtualization_Guide [R=301]
RewriteRule /wireless-guide /en-
US/Fedora/13/html/Wireless_Guide [R=301]
RewriteRule /release-notes/fc1/x86_64 /en-
US/Fedora_Core/1/html/Release_Notes_for_64-bit_x86_Systems [R=301]
RewriteRule /release-notes/fc1/x86 /en-
US/Fedora_Core/1/html/Release_Notes_for_32-bit_x86_Systems [R=301]
RewriteRule /release-notes/fc2/x86_64 /en-
US/Fedora_Core/2/html/Release_Notes_for_64-bit_x86_Systems [R=301]
RewriteRule /release-notes/fc2/x86 /en-
US/Fedora_Core/2/html/Release_Notes_for_32-bit_x86_Systems [R=301]
RewriteRule /release-notes/fc3/x86_64 /en-
US/Fedora_Core/3/html/Release_Notes_for_64-bit_x86_Systems [R=301]
RewriteRule /release-notes/fc3/x86 /en-
US/Fedora_Core/3/html/Release_Notes_for_32-bit_x86_Systems [R=301]
RewriteRule /release-notes/fc4 /en-
US/Fedora_Core/4/html/Release_Notes [R=301]
RewriteRule /release-notes/fc5 /en-
US/Fedora_Core/5/html/Release_Notes [R=301]
RewriteRule /release-notes/fc6 /en-
US/Fedora_Core/6/html/Release_Notes [R=301]
RewriteRule /release-notes/f7 /en-
US/Fedora/7/html/Release_Notes [R=301]
RewriteRule /release-notes/f8 /en-
US/Fedora/8/html/Release_Notes [R=301]
RewriteRule /release-notes/f9 /en-
US/Fedora/9/html/Release_Notes [R=301]
RewriteRule /release-notes/f10 /en-
US/Fedora/10/html/Release_Notes [R=301]
RewriteRule /release-notes/f11 /en-
US/Fedora/11/html/Release_Notes [R=301]
RewriteRule /release-notes/f12 /en-
US/Fedora/12/html/Release_Notes [R=301]
RewriteRule /release-notes/f13 /en-
US/Fedora/13/html/Release_Notes [R=301]
RewriteRule /release-notes/f14 /en-
US/Fedora/14/html/Release_Notes [R=301]
RewriteRule /release-notes/f15 /en-
US/Fedora/15/html/Release_Notes [R=301]
RewriteRule /release-notes/f16 /en-
US/Fedora/16/html/Release_Notes [R=301]
RewriteRule /release-notes/f17 /en-
US/Fedora/17/html/Release_Notes [R=301]
RewriteRule /release-notes/f18 /en-
US/Fedora/18/html/Release_Notes [R=301]
RewriteRule /release-notes/f19 /en-
US/Fedora/19/html/Release_Notes [R=301]
# Current release
RewriteRule /release-notes/f20 /en-
US/Fedora/20/html/Release_Notes [R=301]
RewriteRule /release-notes /en-
US/Fedora/20/html/Release_Notes [R=301]
}}}
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/241>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
7 years, 6 months
[fedora-websites] #91: fedorahosted could use a redesign
by fedora-badges
#91: fedorahosted could use a redesign
---------------------+------------------------
Reporter: toshio | Owner: webmaster
Type: defect | Status: new
Priority: major | Milestone:
Component: General | Version:
Keywords: | Blocked By:
Blocking: |
---------------------+------------------------
Some things I noticed while walking some non-Fedora people through getting
connected on fedorahosted:
* need to point people from fedorahosted to
admin.fedoraproject.org/accounts/ for signing up for a new account
* Not obvious to people that they don't need to sign the FPCA to
contribute on hosted (although that's a project-by-projcet setting)
* http://fedorahosted.org/ should give an overview of what fedorahosted is
rather than a list of projects so that people can find out that anyone can
put upstream code there.
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/91>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
7 years, 6 months
[fedora-websites] #244: Create system for automated screenshots capture
by fedora-badges
#244: Create system for automated screenshots capture
--------------------------+-----------------------
Reporter: jreznik | Owner: webmaster
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: General | Keywords:
Blocked By: | Blocking:
--------------------------+-----------------------
For releases, screenshot creation depends mostly on volunteers with the
need to cover many different options. As screenshots for spins, local
Fedora webs looking for translated screenshots etc. It would be nice to
have (semi)-automated system for screenshots capture.
Requirements - be able to take screenshot from all offered options we
ship, in defined language (optionally for all language variants we offer
for websites).
Implementation could be done through utilization of libvirt and dogtails
scripts. I can even imagine generic Fedora screenshots capture system
based on this effort for App Stream data screenshots creation even with
some sort of joined effort with QA validation for Applications test case
criteria (but this is now pretty much out of scope of initial project).
But I can check with those parties too.
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/244>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
7 years, 10 months
[Fedora Infrastructure] #4793: Information apps.fedoraproject.org/packages not updated for a while
by fedora-badges
#4793: Information apps.fedoraproject.org/packages not updated for a while
--------------------------+------------------------
Reporter: scren | Owner: webmaster
Type: annoyance | Status: new
Priority: minor | Milestone:
Component: Web Content | Version: Production
Severity: Normal | Keywords:
Blocked By: | Blocking:
Sensitive: 0 |
--------------------------+------------------------
= bug description =
The package information on apps.fedoraproject.org/packages/kernel seems to
be stuck at around 2015-06-04 03:00:00 and not to have been updated since.
= bug analysis =
For instance on https://apps.fedoraproject.org/packages/kernel/builds/ the
last build is 4.1.0-0.rc6.git1.1.fc23 marked as "7 hours ago" while one on
http://koji.fedoraproject.org/koji/packageinfo?packageID=8 can see that
this build happened at 2015-06-03 19:23:48. The later builds on koji are
not shown on apps.fedoraproject.org/packages/, and on
https://apps.fedoraproject.org/packages/kernel/overview/ the latest
released version for rawhide is staded as "4.1.0-0.rc6.git1.1.fc23",
although I have got newer versions from the repository since, at least up
to kernel-4.1.0-0.rc7.git1.1.fc23.
The "LATEST BUILD 4.1.0-0.rc8.git0.1.fc23" in the top left corner of
https://apps.fedoraproject.org/packages/kernel/ seems to be correct, but
all other information seems to be outdated.
I am not sure if this problem only appears for the kernel, or for other
packages as well. I checked for some packages and at least for systemd
there seem to be a problem as well
(https://apps.fedoraproject.org/packages/systemd). The build page seems to
be about 3 days delayed, but the overview page still states 220-3.fc23 for
rawhide, although I already got systemd-220-9.fc23 from the rawhide
repository on 2015-06-12, shortly after it was build according to koji.
= fix recommendation =
Update the information to current state. I understand that there might be
some delay, but almost two weeks seems unreasonable long.
--
Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/4793>
Fedora Infrastructure <http://fedoraproject.org/wiki/Infrastructure>
Fedora Infrastructure Project for Bugs, feature requests and access to our source code.
8 years, 5 months
[fedora-websites] #319: Make a script to get and use AMI IDs automatically
by fedora-badges
#319: Make a script to get and use AMI IDs automatically
------------------------+-----------------------
Reporter: robyduck | Owner: webmaster
Type: task | Status: new
Priority: major | Milestone:
Component: getfedora | Keywords:
Blocked By: | Blocking:
------------------------+-----------------------
AMI IDs are getting more and more and we'll probably have soon other
public cloud services and not only Amazon. To make this part easier to
maintain we should think about a script. I have an idea, it could work
like this:
* use fedimg to get the IDs of the AMIs for all regions
* put the IDs into a specific file (a dedicated ami_id.py variable file?)
* all html files can get the IDs from that file simply by calling the
variables
* we should add the execution of the script to our makefile. This way we
can update all IDs on every page manually just by doing ''make amis''. At
the next build the IDs would be in the html pages
The source from where the script gets the IDs can be datanommer but also
other sources. Not sure which one is easier and faster.
Ideas? Comments? Other proposals?
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/319>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
8 years, 5 months
[fedora-websites] #209: use geolocation to pick default ec2 region on getfedora page
by fedora-badges
#209: use geolocation to pick default ec2 region on getfedora page
--------------------------+-----------------------
Reporter: mattdm | Owner: webmaster
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 20
Component: General | Keywords:
Blocked By: | Blocking:
--------------------------+-----------------------
With F19, the "launch" page doesn't show up until you choose a region. We
could default to us-east-1, because that's the biggest and most-full
featured region, but that may come off as a little us-centric. So, what
about guessing the closest region based on geoip, for the F20 version of
the page?
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/209>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
8 years, 5 months