Migration to Zanata
by Noriko Mizumoto
Hi Websites team
Some of you have already noticed, we FLP (aka translation team) have
started the process of migration to new fedora.zanata.org instance from
Transifex. First all translators started to migrate in November 2014
(still going on).
It is time to migrate all projects. This is expected to start after
F21 GA. The documentation is prepared and ready at [1]. If any concern
or question, feel free to ask at zanata-devel ml.
It has been confirmed that the following packages to be migrated.
Could you mind to advise the contacts of each package current
owner/maintainer?
Package Name
FedOAuth
Fedora Account System
Fedora Websites
Many thanks in advance.
[1]:http://zanata.org/help/
Noriko Mizumoto
Fedora Localization Project
9 years, 2 months
[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
Removal of archived threads in mailing list
by Andy Kannberg
Hello,
Is it possible to have a certain threads (which I started myself in 2010) removed ? The threads were in the SSSD-devel list, about the configuration of SSSD against an LDAP environment. For some reason, I did not sanitize the output from logs and config files, hence, certain hostnames and LDAP information is shown in the messages. From security point of view, this information shouldn’t been in the messages, and the company I worked for at that time wants them removed. The exact threads can be found here:
https://lists.fedorahosted.org/pipermail/sssd-devel/2010-August/004360.html
https://lists.fedorahosted.org/pipermail/sssd-devel/2010-August/004395.html
https://lists.fedorahosted.org/pipermail/sssd-devel/2010-August/004434.html
https://lists.fedorahosted.org/pipermail/sssd-devel/2010-September/004455...
https://lists.fedorahosted.org/pipermail/sssd-devel/2011-January/005593.html
https://lists.fedorahosted.org/pipermail/sssd-devel/2011-April/006122.html
https://lists.fedorahosted.org/pipermail/sssd-devel/2011-September/007082...
It would be great if you would fulfill my request. If you can’t or won’t be able to remove the archived threads, is it at least possible to anonimize them ?
best regards,
Andy Kannberg
UNIX&Linux Consultant @ Snow, The Netherlands.
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] #284: Fedora 21 website: TODOs
by fedora-badges
#284: Fedora 21 website: TODOs
----------------------------+-----------------------
Reporter: robyduck | Owner: webmaster
Type: task | Status: new
Priority: critical | Milestone: Fedora 21
Component: General | Keywords:
Blocked By: 248, 282, 283 | Blocking:
----------------------------+-----------------------
We have already some tickets for F21 (adding them as Blocker), but there
are many things we need to do before release date. This ticket is intended
as a TODO list to not forget anything before we build getfedora.org in
production. Please add anything to the list I might forget:
* Check all pages for missing I18n (also modals and other templates)
* clean up our app.css file of unused classes and add browser prefixes
* Pages need to be optimized for mobile, they are not really responsive
ATM
* Pulling po files works now for stg only. For production delete /var/lib
/transifex-client/.tx/config on bapp and execute (if needed)
syncTranslations.sh
* We need to add redirects in redirects.conf on puppet for
-- fedoraproject.org/verify [[br]]
-- fedoraproject.org/keys [[br]]
-- fedoraproject.org/get-fedora* [[br]]
* In our external release counter we have a link to the F21 release
banner, which won't work. Maybe we should redirect that too.
* add CHECKSUMS
* check ALL links (DL, DOCS, footer)
* add image sizes for getfedora.org and spins.fp.o to our globalvar.py
* verify if all spins are build for GOLD RC
* add AMI IDs, our script is ready for Atomic and Base IDs (contact
oddshocks)
* decide where to put Workstation and Minimal ARM images
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/284>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
9 years, 4 months