#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
#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
#362: Link to Release Announcement on getfedora.org
--------------------------+-----------------------
Reporter: ryanlerch | Owner: webmaster
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: General | Keywords:
Blocked By: | Blocking:
--------------------------+-----------------------
Was thinking, it might be a good idea to have a link to the release
announcement for the current release on the Fedora Magazine somewhere on
getfedora.org
Maybe on the page for each edition -- not sure about where.
We also do a regular "What's new in fedora X <edition>" article too (for
f23, we only have the workstation one, but we want to do all three for
f24), so this might be good to have instead of the release announcement,
Not 100% sure.
this is just to direct users to the best source of information about the
changes in the current release of Fedora, as getfedora.org's information
is more just about all fedora features, not just the new ones.
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/362>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
#364: developers.fedoraproject.org a DNS record
----------------------+-----------------------
Reporter: phracek | Owner: webmaster
Type: defect | Status: new
Priority: major | Milestone:
Component: General | Keywords:
Blocked By: | Blocking:
----------------------+-----------------------
Hi folks,
I am happy that we have a developer.fedoraproject.org page.
We need to improve it and help to users.
Could you please create a DNS record developers.fedoraproject.org
which will refer to developer.fedoraproject.org?
I guess, it would be awesome to have it before.
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/364>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance