websites October 2014

websites@lists.fedoraproject.org

23 participants
49 discussions

[fedora-websites] #274: UEFI consistency warning
by fedora-badges 21 Oct '16

21 Oct '16

#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

1 8

[fedora-websites] #241: Change docs link to redirected one to prevent hard release number usage
by fedora-badges 21 Oct '16

21 Oct '16

#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

1 5

[fedora-websites] #91: fedorahosted could use a redesign
by fedora-badges 21 Oct '16

21 Oct '16

#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

1 3

[fedora-websites] #244: Create system for automated screenshots capture
by fedora-badges 21 Jun '16

21 Jun '16

#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

1 3

[fedora-websites] #209: use geolocation to pick default ec2 region on getfedora page
by fedora-badges 30 Oct '15

30 Oct '15

#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

1 2

[fedora-websites] #193: fudcon websites is badly designed
by fedora-badges 16 Aug '15

16 Aug '15

#193: fudcon websites is badly designed ---------------------+------------------------ Reporter: shaiton | Owner: webmaster Type: defect | Status: new Priority: major | Milestone: Component: General | Version: Keywords: | Blocked By: Blocking: | ---------------------+------------------------ This websites use the Genshi framework to build without using the Genshi templates. Once we decide what to do with this website (continue, recode, or drop) we will need to clean it. - Making use of data/templates (they are currently not used at all) and removing specific headers in data/content/* - probably share the templates with the other websites. -- Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/193> fedora-websites <https://fedoraproject.org/wiki/Websites> Fedora Website Team's Trac instance

1 5

[fedora-websites] #269: redirect all sites to https
by fedora-badges 04 Jun '15

04 Jun '15

#269: redirect all sites to https --------------------------+----------------------- Reporter: mattdm | Owner: webmaster Type: enhancement | Status: new Priority: major | Milestone: Component: General | Keywords: Blocked By: | Blocking: --------------------------+----------------------- See http://googleonlinesecurity.blogspot.cz/2014/08/https-as-ranking- signal_6.html In addition to being good for our users and an improvement in security, this will increase our google search ranking. -- Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/269> fedora-websites <https://fedoraproject.org/wiki/Websites> Fedora Website Team's Trac instance

1 5

[fedora-websites] #145: Remove redirect rule to Design and Electronic-Lab Spins
by fedora-badges 19 May '15

19 May '15

#145: Remove redirect rule to Design and Electronic-Lab Spins -------------------------+------------------------ Reporter: robyduck | Owner: webmaster Type: enhancement | Status: new Priority: minor | Milestone: Component: spins.fp.o | Version: Keywords: | Blocked By: Blocking: | -------------------------+------------------------ For a better maintaing of the spins pages we should remove the actual redirect rules for the Design and Electronic-Lab Spin. That's from the Infra side, no hurry until F18 will be released. -- Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/145> fedora-websites <https://fedoraproject.org/wiki/Websites> Fedora Website Team's Trac instance

1 6

[fedora-websites] #276: New release counter for fedora.next websites
by fedora-badges 19 May '15

19 May '15

#276: New release counter for fedora.next websites --------------------------+----------------------- Reporter: robyduck | Owner: webmaster Type: enhancement | Status: new Priority: major | Milestone: Fedora 22 Component: get.fp.o | Keywords: Blocked By: | Blocking: --------------------------+----------------------- We actually have two release counter scripts on the webpages. * Internal release counter which is just a small script * External release counter, works with JS Both rely on a huge work of the design team, because we need for every release about 30 banners in several languages and they really take a lot of time to produce them. We should think about a new release counter and should only need one image (in several sizes?) from the design team; the rest could be done with a script and shouldn't be too difficult for the counter on the fpo webpages. The more difficult part will be the external counter, and although we shouldn't break the links people placed on their blogs, local community websites etc. I fear we need to do so. It would be a good moment to change the link when the counter will be for the first time on the new fedora.next webpages (F22 Beta), so let's aim that target. If anyone is willing to work on this please get in contact with the websites team first to figure out which could be the best solution and how to perform it. A small final note: [https://en.opensuse.org/openSUSE:Countdown OpenSuse] is already using a similar solution, maybe it is useful to start working on it. -- Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/276> fedora-websites <https://fedoraproject.org/wiki/Websites> Fedora Website Team's Trac instance

1 2

[Fedora Infrastructure] #4386: Add Language Selector to EasyFix Page
by fedora-badges 04 May '15

04 May '15

#4386: Add Language Selector to EasyFix Page --------------------------+----------------------------- Reporter: lovenemesis | Owner: webmaster Type: enhancement | Status: new Priority: major | Milestone: HANDWAVY-FUTURE Component: Web Content | Version: Production Severity: Normal | Keywords: Blocked By: | Blocking: Sensitive: 0 | --------------------------+----------------------------- = problem = Current Easy Fix page doesn't have a language selector: http://fedoraproject.org/easyfix/ = analysis = Upper right corner doesn't have the language selector as the rest of Fedora Project web pages. = enhancement recommendation = With a language selector and po file pushed into Transifex.net, l10n team can translate this page so that it could be more appealing to new contributors. -- Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/4386> Fedora Infrastructure <http://fedoraproject.org/wiki/Infrastructure> Fedora Infrastructure Project for Bugs, feature requests and access to our source code.

1 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

websites October 2014