Bug ID: 1361757
Summary: Typo in the czech localization Anaconda installer
Product: Fedora Localization
Component: Other language
QA Contact: aalam(a)redhat.com
CC: dimitris(a)glezos.com, piotrdrag(a)gmail.com,
Description of problem:
Typo in the czech localization Anaconda installer
Version-Release number of selected component (if applicable):
Fedora 24 x86_64
Downloaded workstation version from website https://getfedora.org/
Start czech installer any time and go to disk management.
Select manual partitioning.
You should be now on this screen:
You are receiving this mail because:
You are on the CC list for the bug.
My name is Alex Eng and I'm from Zanata team.
Apart from engineering, I'm interested in working in translations too for
I'm fluent in Simplify Chinese, Malay, English, and Traditional Chinese but
I would start with Simplify Chinese for the time being.
Dear translators team,
if you can translate in one of this languages (Assamese, Bengali-India,
Chinese-Taiwan, German, Gujarati, Hindi, Italian, Japanese, Kannada,
Malayalam, Oriya, Punjabi, Tamil, Telugu) please have a look to iok (_18
words_ to validate) :
this bug looks like blocked because of missing translations :
thanks for your help
note : if you still having issues with Zanata, use the "Zanata fail
I am sure many members involved in trans, i18n, zanata and fltg will be
there. This is good chance to have couple hours meetup and review present
state and plan for coming 2 releases of Fedora.
I have created page for g11n flock 2016 . Please add your name on
page and add topic if anything in mind.
No offense, but you're a technical expert and used to Fedora's way of
Plus, you analyzed a process and did not experienced it as the target :
newcomer who knows nothing about Fedora process/rules and would like to
correct something or help translating something he likes.
I remember my registering last year and it is not as easy has it looks
like. It was confirmed by two newcomers in french team.
If the wiki needs the contributor to be in a dedicated group, I think
it's time to discuss process, make it easier and to document it.
I think nobody knows what "cvsl10n" means anymore and the vocable is
changing a lot from Coordinator, Sponsor, Maintainer, Administrator (I
discovered this one today). Now, you're talking about "Leaders", are
they the same ?
How to we change responsibilities from one to another ? And what can we
do if one coordinator/sponsor/leader/... don't answer anymore so we make
sure no contributor is neglected ?
It's even harder for contributors to understand the limit between the
translation platform we use as a tool and Zanata as a independent project.
Plus, it's hard for a coordinator to understand what tools does he have
to manage something (not a lot actually).
All l10n groups looks out of date (names are very old, so are links and
the percentage of unapproved subscription is very high, witch _may_ mean
: no more management) :
Translation CVS Commit Group cvs cla_done
gitman-pages-l10n git cla_done
l10n Admin Group tracking cla_done
l10n Commit Group tracking None
Localization (L10n) Editors tracking cla_done
Note that the "L10N/Guide" page says everyone has to be in cvsl10n but
the "L10N maintainer" page may be understood that it is to be maintainer.
What's the purpose of creating a component in bugzilla if we have no
mailing list to be warned ?
What makes a languages dead or alive ?
If we have to create one or many groups, can we take benefit of it ? In
knowing who are the contacts, responsibilities, reach them, sync with
BTW, why do we have private mailing lists ? It already sounds weir as
open-source contribution/discussions should be public by default and
private by exception, but even more since hyperkitty can't register
anymore, you may try with trans-pl being registered or not :
It's a lot of questions and I think we should admit it isn't easy to
come and contribute Fedora translations and to understand how does it works.
This spam issue looks like a good opportunity to make it easier (maybe
not by deleting steps, but by making it smoother, more consistent).
about two weeks I can't login on Zanata,
I tried to clean my browser cache, also I tried do login with private
mode in firefox, but without success to login.
so I search the list archives and I found a message explaining that this
happen due to the slow response from Fedora open id service causing
Zanata to fail login.
Someone are having this kind of issue?
What can I do to log me in?