[fedora-websites] #100: Fedoraproject.org banner (not being dynamic) problem
by fedora-badges
#100: Fedoraproject.org banner (not being dynamic) problem
------------------------------------------+-------------------------
Reporter: nippur | Owner: webmaster
Type: defect | Status: new
Priority: major | Milestone:
Component: www.fp.o | Version: Production
Keywords: banner, translation, website | Blocked By:
Blocking: |
------------------------------------------+-------------------------
The amber(features & screenshot), green(downloads), pink?(community),
blue(using fedora) and purple(help) color banners at
fedoraproject.org are not big enough/don't automatically expand if the
(translated) string is more than one line. Text is lost when translation
can't be 'one line wide' due to local word length/syntax.
Suggested is 'it depends of your browser, probably because "em" font size
is used and not px' in combination with website design not being dynamic.
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/100>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
8 years, 11 months
[fedora-websites] #184: Make outdated spins unavailable for download
by fedora-badges
#184: Make outdated spins unavailable for download
----------------------+------------------------
Reporter: robyduck | Owner: webmaster
Type: defect | Status: new
Priority: major | Milestone: Fedora 19
Component: General | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
We have some spins which are rather outdated, a few perhaps are even dead.
We should make it impossible to access the download tab in these spin
pages.
Solution:
* Check on the JSON file if the spin is available before displaying the
spin page with the download tab
* Check and remove variables (curr_id), if they are used outside the
download tab
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/184>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
9 years, 8 months
[fedora-websites] #165: wrong Torrent iso size on spins.fpo
by fedora-badges
#165: wrong Torrent iso size on spins.fpo
-------------------------+------------------------
Reporter: shaiton | Owner: webmaster
Type: defect | Status: new
Priority: major | Milestone:
Component: General | Version:
Keywords: infra, json | Blocked By:
Blocking: |
-------------------------+------------------------
rev d77ff0e is a workaround, which needs to be reverted.
Problem is that on data/templates/sidebar.html, formatsize retuns 0 as the
json stats file has size: 0, from puppet
./modules/torrent/files/torrentjsonstats.py.
but puppet/modules/torrent/files/torrent-generator/torrent-generator is
fine for http://torrent.fedoraproject.org
So we need to add again the ISO size, as a variable on this string, that
needs to be translatable.
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/165>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
9 years, 8 months
[fedora-websites] #127: Create new/update fedora usecases
by fedora-badges
#127: Create new/update fedora usecases
-------------------------+------------------------
Reporter: heavensmile | Owner: webmaster
Type: task | Status: new
Priority: major | Milestone:
Component: www.fp.o | Version:
Keywords: | Blocked By:
Blocking: |
-------------------------+------------------------
The tips on how to use fedora on http://fedoraproject.org/en/using/ are
based on fedora 14/GNOME2 and are thus outdated. This includes the
screenshots as well as some of the tips themselves.
Particularly "Create custom app launchers" describes a function/feature
that is not present in GNOME3 and represent a very non-GNOME3 workflow (I
think it should be removed).
With GNOME 3.6/fedora 18 around the corner its exists a good opportunity
to create new use-cases.
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/127>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
9 years, 8 months
[fedora-websites] #197: Should we create a schedule static page
by fedora-badges
#197: Should we create a schedule static page
--------------------------+-----------------------
Reporter: shaiton | Owner: webmaster
Type: enhancement | Status: new
Priority: major | Milestone:
Component: General | Keywords:
Blocked By: | Blocking:
--------------------------+-----------------------
There is no easy way to know when our next Fedora will be released.
People should look for the right wiki page, and there could be frequent
updates.
I propose to design a simple page containing the main schedules (Alpha,
Beta and GA releases).
The data would be taken from the online official schedule (parsing as XML
I think). This would be shared by ou main fpo websites (for the countdown
banner..)
The content would be in fpo/get-prerelease and on a secondary page like
schedule.fpo? or just fpo/schedule?
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/197>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
9 years, 11 months
[fedora-websites] #167: spins: we need to update the screenshots, and make it nicer
by fedora-badges
#167: spins: we need to update the screenshots, and make it nicer
-------------------------+------------------------
Reporter: shaiton | Owner: webmaster
Type: defect | Status: new
Priority: critical | Milestone:
Component: General | Version:
Keywords: srceenshots | Blocked By:
Blocking: |
-------------------------+------------------------
we need to update many screenshots on the spins website.
Also, we need to make it easily maintainable, they should all be on a
specific folder, using the same overview/code (like kde Vs Xfce page). On
big pic and the other one smaller.
It could be great to reuse the on on the get-fedora-options fpo page.
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/167>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
10 years, 2 months