February 2015 - websites - Fedora Mailing-Lists

[fedora-websites] #306: Migrate web translation source files to Zanata

by fedora-badges

#306: Migrate web translation source files to Zanata -----------------------+----------------------- Reporter: robyduck | Owner: webmaster Type: task | Status: new Priority: critical | Milestone: ASAP Component: General | Keywords: Blocked By: | Blocking: -----------------------+----------------------- As you all probably know we are going to migrate our web-translation files from Transifex to Zanata. I've already spoken with Noriko and I think the best would be to migrate our files as soon as possible. From Alpha to Beta to Final it's not a long time, so if we can complete the migration at least 2 weeks before Alpha would be the best. If anyone wants to help, please get in contact with me in order to work on this. Read http://zanata.org/help/ and look at our actual workflow for translation files to understand how it works. The changes need to be made not only in our repo but also on Infra, in order to pull PO files correctly at every build. We also need to change our scripts and find a way to make the migration happen as smooth as possible, without creating troubles to L10n folks. -- Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/306> fedora-websites <https://fedoraproject.org/wiki/Websites> Fedora Website Team's Trac instance

9 years, 2 months

1
2
0 / 0

Fedora Websites Translations: Migration to Zanata completed!

by Robert Mayr

Dear translators, the Websites team has completed the migration of all web sources to the new translation platform and you can access the Websites Project from the following link, to get familiar with it: https://fedora.zanata.org/project/view/fedora-web This doesn't mean we have switched completely to Zanata, but Transifex won't get any updated source file from now on. The goal is to make the switch as smooth as possible for you. Actually we have 2 branches we are working on: 1) Production (master) We still pull translations automatically from Transifex, but in about 10-12 days we will freeze translations and close all source files, making them un-translatable. So, if you have some smaller fixes you can still use TX (until we freeze it). If you want to translate more pages you 'should' use Zanata, but you won't see your translations in production until Fedora 22 Alpha release date. 2) Fedora 22 Alpha branch (staging) Actually we are working on prerelease pages in getfedora.org and spins.fpo. Both source files are being pushed ONLY to Zanata and we pull translations manually until F22 Alpha release. Any translation for Alpha therefore MUST be translated on Zanata. We are going to build Alpha pages in staging ASAP, so you can have a look where the new strings are and in which context. If you don't know exactly where to translate the strings in this period, I'd advice you to work only on Zanata. There are some strings which unfortunately we were not able to merge correctly, so please have a look and eventually copy and paste them from TX if you already did those strings. Finally I think the earlier you get comfortable with Zanata the better, so this is a good moment to do so, as we are about 3 weeks away from Alpha release and didn't hit any freeze for now. I hope the plan will work as expected, if you have any specific questions about this workflow or something is not clear to you, just ping me on -websites. Thank you for your help and happy translating to all! -- Robert Mayr (robyduck)

9 years, 2 months

1
0
0 / 0

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

4
8
0 / 0

[fedora-websites] #311: https://fedoraproject.org/ipsilon/ redirects to https://getfedora.org

by fedora-badges

#311: https://fedoraproject.org/ipsilon/ redirects to https://getfedora.org ------------------------+----------------------- Reporter: dmossor | Owner: webmaster Type: defect | Status: new Priority: major | Milestone: ASAP Component: getfedora | Keywords: Blocked By: | Blocking: ------------------------+----------------------- As the subject states, the Ipsilon project page redirects to getfedora.org, making the Ipsilon project pages inaccessible. -- Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/311> fedora-websites <https://fedoraproject.org/wiki/Websites> Fedora Website Team's Trac instance

9 years, 2 months

1
0
0 / 0

[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

1
5
0 / 0

verify page not linked from the download page

by Martin Bukatovic

Hello fedora website list! I have just noticed that the download pages listed below: https://getfedora.org/ https://getfedora.org/en/workstation/download/ https://getfedora.org/en/server/download/ https://getfedora.org/en/cloud/download/ don't contain any link to verify page with checksums. The verify page still exists though, see: https://getfedora.org/en/verify Could someone here look into this and fix it? Martin Bukatovic

9 years, 2 months

2
2
0 / 0

[Fedora Infrastructure] #4663: copr-be.cloud.fedoraproject.org is down

by fedora-badges

#4663: copr-be.cloud.fedoraproject.org is down ---------------------------------+----------------------- Reporter: alatteri | Owner: webmaster Type: bug | Status: new Priority: blocker | Milestone: asap Component: Web Content | Version: Severity: The Sky Is Falling | Keywords: host down Blocked By: | Blocking: Sensitive: 0 | ---------------------------------+----------------------- = bug description = trying to install ovirt-engine into centos 6.6 via yum = bug analysis = http://copr- be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-6-x86_64/r...: [Errno 14] PYCURL ERROR 7 - "couldn't connect to host" = fix recommendation = reboot server -- Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/4663> Fedora Infrastructure <http://fedoraproject.org/wiki/Infrastructure> Fedora Infrastructure Project for Bugs, feature requests and access to our source code.

9 years, 2 months

1
1
0 / 0

fedoraproject.org

by keglo stephane

Hello everyone. i would like to contribute to Fedora. i registered on the marketing group mailing list. This is a moment that i am redirected to getfedora.org when i try to access fedoraproject.org. Does the site fedoraproject.org will soon be available or not?

9 years, 2 months

1
0
0 / 0

[Fedora Infrastructure] #4659: Code of Conduct does not seem to be easily reachable from https://getfedora.org

by fedora-badges

#4659: Code of Conduct does not seem to be easily reachable from https://getfedora.org --------------------------+----------------------------- Reporter: till | Owner: webmaster Type: bug | Status: new Priority: major | Milestone: HANDWAVY-FUTURE Component: Web Content | Version: Severity: Normal | Keywords: Blocked By: | Blocking: Sensitive: 0 | --------------------------+----------------------------- = bug description = Unless I am missing it, there seems to be no obvious way to find https://getfedora.org/code-of-conduct starting from https://getfedora.org/ -- Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/4659> Fedora Infrastructure <http://fedoraproject.org/wiki/Infrastructure> Fedora Infrastructure Project for Bugs, feature requests and access to our source code.

9 years, 2 months

1
1
0 / 0

[Fedora Infrastructure] #4656: https://getfedora.org/en/verify contains only the checksum files for Fedora 21 and F19 EOL key

by fedora-badges

#4656: https://getfedora.org/en/verify contains only the checksum files for Fedora 21 and F19 EOL key --------------------------+----------------------------- Reporter: till | Owner: webmaster Type: bug | Status: new Priority: major | Milestone: HANDWAVY-FUTURE Component: Web Content | Version: Severity: Normal | Keywords: Blocked By: | Blocking: Sensitive: 0 | --------------------------+----------------------------- https://getfedora.org/en/verify - should not mention the Fedora 19 key, that is EOL - is missing the information about how to verify secondary archs or Fedora 21 -- Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/4656> Fedora Infrastructure <http://fedoraproject.org/wiki/Infrastructure> Fedora Infrastructure Project for Bugs, feature requests and access to our source code.

9 years, 2 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

websites February 2015