#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
#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
#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
#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.
#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
#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
#369: Fedora Server: do not advertise 32-bit media
--------------------------+-----------------------
Reporter: sgallagh | Owner: webmaster
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 24
Component: getfedora | Keywords:
Blocked By: | Blocking:
--------------------------+-----------------------
In Fedora 24, the Server SIG intended to stop producing i686 media
entirely, to focus only on x86_64 and ARM. Due to rel-eng constraints, we
won't be able to avoid ''creating'' the media, so we would like to request
that the getfedora.org website not include any download links for them.
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/369>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
#5040: can't find the current mailing lists from the home page
--------------------------+-----------------------------
Reporter: chrismurphy | Owner: webmaster
Type: annoyance | Status: new
Priority: major | Milestone: HANDWAVY-FUTURE
Component: Web Content | Version: Production
Severity: High | Keywords:
Blocked By: | Blocking:
Sensitive: 0 |
--------------------------+-----------------------------
= phenomenon =
http://fedoraproject.org/ -> https://getfedora.org/ where the word "list"
doesn't appear anywhere. The closest similar link, forums, directs away
from fedoraproject.org to a 3rd party, http://fedoraforum.org/.
I have to do a google or duckduckgo search to find them.
= reason =
Lack of link for mailing lists on the home page.
= recommendation =
Put a link on the home page for mailing lists. I'm thinking of this one:
https://lists.fedoraproject.org/mailman/listinfo
Or maybe there's a more appropriate one now that the hyperkitty switch has
been flipped.
--
Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/5040>
Fedora Infrastructure <http://fedoraproject.org/wiki/Infrastructure>
Fedora Infrastructure Project for Bugs, feature requests and access to our source code.