websites April 2016

websites@lists.fedoraproject.org

31 participants
42 discussions

[fedora-websites] #385: I don't like fade-out feature at flocktofedora.org
by fedora-badges 26 Feb '17

26 Feb '17

#385: I don't like fade-out feature at flocktofedora.org ------------------------+----------------------- Reporter: rluzynski | Owner: webmaster Type: defect | Status: new Priority: minor | Milestone: Component: General | Keywords: Blocked By: | Blocking: ------------------------+----------------------- When I hover my mouse over a section of the text at flocktofedora.org site the neighboring sections fade out, get white or blurred and unreadable. That's even worse if I hover the mouse pointer over the area with no text: in such case all neighboring sections fade out. I guess the intention was to emphasize the text under the mouse pointer but personally I don't like this effect. I don't tend to keep the mouse pointer over the text I'm currently reading. Instead I tend to keep it away, usually close to the right scrollbar. Also think about the touchscreen devices: if you touch a screen (for example to scroll the content) and it is interpreted as mouse hover a part of the screen fades out which you don't want. My suggestion is to fade in the hovered text rather than fade out the neighboring text. In order to let the text be faded in it must be faded out by default but really slightly faded out, for example background #eeeeee foreground #111111, and fade in to background #ffffff foreground #000000. -- Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/385> fedora-websites <https://fedoraproject.org/wiki/Websites> Fedora Website Team's Trac instance

2 1

[fedora-websites] #293: Some websites still use fedoraproject.org files
by fedora-badges 30 Nov '16

30 Nov '16

#293: Some websites still use fedoraproject.org files -----------------------+----------------------- Reporter: robyduck | Owner: webmaster Type: defect | Status: new Priority: major | Milestone: Component: General | Keywords: Blocked By: | Blocking: -----------------------+----------------------- Our storical website http://fedoraproject.org actually has been replaced by https://getfedora.org and is now outdated. We still keep fp.o live although it's not build anymore, because many websites (also some apps probably) and the wiki still use CSS classes or other files which are in the fp.o tree. We should make sure all webpages have these files locally because fp.o will be overwritten at some point. -- Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/293> fedora-websites <https://fedoraproject.org/wiki/Websites> Fedora Website Team's Trac instance

1 2

[fedora-websites] #340: download links on getfedora should use https
by fedora-badges 21 Oct '16

21 Oct '16

#340: download links on getfedora should use https ------------------------+----------------------- Reporter: mattdm | Owner: webmaster Type: defect | Status: new Priority: major | Milestone: Component: getfedora | Keywords: Blocked By: | Blocking: ------------------------+----------------------- We have a general effort to use https to reduce risk of MITM attacks. Right now, the links like https://getfedora.org/en/cloud/download /download-cloud- splash?file=http://download.fedoraproject.org/pub/fedora/linux/releases/22/… /Fedora-Cloud-Atomic-22-20150521.x86_64.qcow2 use http — they should use HTTPS. Thank you! -- Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/340> fedora-websites <https://fedoraproject.org/wiki/Websites> Fedora Website Team's Trac instance

1 6

[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] #384: Change primary Workstation downloadable to Fedora Media Writer
by fedora-badges 20 Sep '16

20 Sep '16

#384: Change primary Workstation downloadable to Fedora Media Writer ------------------------+----------------------- Reporter: eischmann | Owner: webmaster Type: task | Status: new Priority: blocker | Milestone: Fedora 24 Component: General | Keywords: Blocked By: | Blocking: ------------------------+----------------------- We're working on F24 change to change the primary downloadable of Workstation to Fedora Media Writer (formerly LiveUSB Creator): https://fedoraproject.org/wiki/Changes/LUCasPrimaryDownloadable We need assistance from the websites team because the change requires changes on the download website: 1) Based on the user agent Windows users should be offered an exe file of FMW (Dennis is currently figuring out location for it). 2) For them, we should alter the website and explain what FMW is instead of "What is a Live image"? We should still keep ISOs in Other downloads for those we do want to download an ISO. 3) For everyone else (Linux, Mac,...), we should still offer an ISO, but instead of general "To use this image, you need a drive that can create or "burn" DVDs, or a USB flash drive at least as big as the image." we should point them to FMW, probably linking How_to_create_and_use_Live_USB which we will change to describe FMW. Answers to additional questions asked by robyduck in email conversations: Do you want to let people download a software to get a Fedora image instead of a simple download link of the iso?[[BR]] Yes, that's the idea. Especially on other platforms (Windows, Mac), it's hard to find a tool that can reliably write Fedora on a USB drive. So instead of downloading an ISO, Windows users will download a tool that will let them download it and write it on a USB drive. Mostly for win users?[[BR]] Only for Windows users in F24 release cycle. We planned the same for Mac users, but the Mac port won't be finished on time. If there is a standard cross-distro installation format (e.g. xdg-app) in the future, we may consider it for Linux users, too, but not for F24. What about spins, labs, Server?[[BR]] The Server working group decided not to use FMW as primary downloadable. We also don't want to include spins and labs now. FMW allows you to download Server, spins and labs, but spins and labs are in a list you need to extend, so it may be confusing for users as primary downloadable. We plan it only for Workstation now. Anyway, FMW should be at least mentioned as the official way to write the ISO on download pages of other editions, spins, and labs. How will checksums work?[[BR]] FMW checks checksums of ISOs it has downloaded before they're loaded to a USB drive. Where and who will provide documentation for the use of this software?[[BR]] We will describe how to use the tool on the following wiki page once it's official. We don't want to change the wiki page now when FMW is still not officially available.[[BR]] https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB -- Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/384> fedora-websites <https://fedoraproject.org/wiki/Websites> Fedora Website Team's Trac instance

1 8

[Fedora Infrastructure] #5207: Explore uses for donated CDN
by fedora-badges 06 Jul '16

06 Jul '16

#5207: Explore uses for donated CDN --------------------------+----------------------------- Reporter: kevin | Owner: webmaster Type: task | Status: new Priority: major | Milestone: HANDWAVY-FUTURE Component: Web Content | Version: Severity: Normal | Keywords: Blocked By: | Blocking: Sensitive: 0 | --------------------------+----------------------------- We have been approached by a CDN (content delivery network) provider that wishes to donate their services to us. :) We need to explore how best we could use such a network or adapt to using such a network. Static websites content seems like it might be easy to test out. mirrors seems like it would be more complex and heavy, but perhaps we can find a way to use it for heavily accessed content. Ideas and suggestions welcome. -- Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/5207> Fedora Infrastructure <http://fedoraproject.org/wiki/Infrastructure> Fedora Infrastructure Project for Bugs, feature requests and access to our source code.

1 3

[fedora-websites] #373: Mention rawhide on getfedora.org
by fedora-badges 05 Jul '16

05 Jul '16

#373: Mention rawhide on getfedora.org ----------------------+----------------------- Reporter: kevin | Owner: webmaster Type: defect | Status: new Priority: major | Milestone: Component: General | Keywords: Blocked By: | Blocking: ----------------------+----------------------- While we don't want people who don't meet the target audience to try and jump in and run rawhide, it might be nice to mention it for advanced users. Perhaps even just a link to the rawhide wiki page? Happy to help draft wordage if we can figure out if there's a place it fits. -- Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/373> fedora-websites <https://fedoraproject.org/wiki/Websites> Fedora Website Team's Trac instance

1 2

[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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

websites April 2016