[fedora-websites] #112: improve docs integration
by fedora-badges
#112: improve docs integration
---------------------+------------------------
Reporter: shaiton | Owner: webmaster
Type: defect | Status: new
Priority: major | Milestone:
Component: General | Version:
Keywords: | Blocked By:
Blocking: |
---------------------+------------------------
We still have some hard links to the docs.fpo websites, with the language
code hard written.
sometimes available in the POT. it should not be there… and we should
remap the language code if exists (like in the get-prerelease page).
If we link to a non translated doc, we just go to the index in that
language, and not to the en-US version. Is it ok?
In any case, we need to be consistent, some code has to change.
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/112>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
9 years, 2 months
[fedora-websites] #234: make click-to-launch-in-EC2 button something that we can log
by fedora-badges
#234: make click-to-launch-in-EC2 button something that we can log
--------------------------+-----------------------
Reporter: mattdm | Owner: webmaster
Type: enhancement | Status: new
Priority: minor | Milestone: Fedora 20
Component: get.fp.o | Keywords:
Blocked By: | Blocking:
--------------------------+-----------------------
Right now, we don't have very good statistics about whether the deploy-to-
cloud button is being used. As I understand it, the current implementation
just presents a bare link which we can't easily log. I don't want invasive
tracking or anything, just a count of how many launches there have been
(analogous to counting downloads). Could we make the button link to a
redirect which we can then count?
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/234>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
9 years, 4 months
[fedora-websites] #248: New Fedora.next website
by fedora-badges
#248: New Fedora.next website
----------------------+-------------------------
Reporter: shaiton | Owner: webmaster
Type: defect | Status: new
Priority: blocker | Milestone: Fedora 21
Component: General | Keywords: fedora.next
Blocked By: | Blocking:
----------------------+-------------------------
The Project is moving to Fedora.next. The websites have to follow!
== Web tasks
* delete spins.fpo
* delete /using and /features
* delete /get-fedora-all
* edit get-fedora to feature the 3 products. As simple/smart as possible
(few text, short description, a link to DL and more descriptions
(fpo/<product>)
* keep 960gs or move to bootstrap? (bootstrap is less customizable)
== Infra tasks
* create {desktop, worstation, cloud}.fpo (redirect to fpo/<product>)
* redirect spins.fpo to desktop.fpo?
discussion is going on on the mailing list
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/248>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
9 years, 4 months
[fedora-websites] #275: Prepare webpages for F21 Beta release
by fedora-badges
#275: Prepare webpages for F21 Beta release
-----------------------+-----------------------
Reporter: robyduck | Owner: webmaster
Type: task | Status: new
Priority: major | Milestone: Fedora 21
Component: get.fp.o | Keywords:
Blocked By: | Blocking:
-----------------------+-----------------------
Beta branch has been created, banner added and state globalvar set. The
websites also are in staging and running.
For release date we need to work on minor changes, most of the scripts and
work has already been done for Alpha:
* add countdown banners
* modify release counter and verify it is working for the external release
counter too
* add beta checksums and remove alpha
* change ISO image sizes
* add AMI IDs (contact oddshocks) once we have a GO for a RC
* check DL links and verify they are consistent with the new paths
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/275>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
9 years, 5 months
[fedora-websites] #243: [PATCH] Modify the "our apps" link to point to apps.fp.o/packages rather than pkgdb
by fedora-badges
#243: [PATCH] Modify the "our apps" link to point to apps.fp.o/packages rather
than pkgdb
--------------------------+-----------------------
Reporter: ankursinha | Owner: webmaster
Type: enhancement | Status: new
Priority: minor | Milestone: ASAP
Component: www.fp.o | Keywords:
Blocked By: | Blocking:
--------------------------+-----------------------
[PATCH] Modify the "our apps" link to point to apps.fp.o/packages rather
than the pkgdb
The pkgdb isn't for users, it's for package maintainers to modify package
ACLs. Users should be directed to the "packages app" that provides a much
better interface.
There's been at least one case where a user went to pkgdb and couldn't
find anything, since the search there doesn't crawl package
summaries/descriptions, only packagenames (which too have to be searched
using regexps).
(Also, should the links we use have csrf tokens in them? The pkgdb link
had it.)
Thanks,
Warm regards,
Ankur
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/243>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
9 years, 5 months