I am sure, most of the people working with Fedora I18N, L10N from 5-6
year must be aware regarding Fedora L10N Steering Committee.  As far
as i know this committee was active around 2009 and very effective.
During Fedora G11N activity day discussions, we again felt there is
need for some kind of official committee to drive Fedora Globalization
activities. Fedora is growing faster with number of different domains
and G11N also need to adapt those changes quickly to remain on the track.
For this purpose and in line with , we were thinking of Fedora
Globalization steering committee. I have created initial proposal for
Its open for feedback, please feel free to share other active members,
discuss in your respective language groups. This is just initial
proposal and i am sure, we can improve and make it more effective with
g11n mailing list
We have updated the design and contents of our home page *http://zanata.org/
<http://zanata.org/>* for better user experience.
Any feedback is welcome.
SENIOR SOFTWARE ENGINEER, team lead
globalisation tooling, customer platform
Red Hat Asia-Pacific Pty Ltd <https://www.redhat.com/>
aeng(a)redhat.com M: +61423353457 IM: aeng
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.
We are going to have a short meeting on #fedora-g11n in 15min. Agenda is
only T-shirt for contributors who contributed over 500 words in 2016. 
We are almost in last stage of it, if anyone available feel free to jump
Apologies for short notice,
Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 27
Final Release Readiness Meeting meeting.
The meeting is going to be held on Thursday, Oct 26, 2017 at 19:00
UTC. Please check the  link for your time zone.
We will meet to make sure we are coordinated and ready for the Final
release of Fedora 27. Please note that this meeting is going to be
held even if the release is delayed at the Go/No-Go meeting on the
same day two hours earlier.
You may received this message several times, but it is by purpose to
open this meeting to the teams and to raise awareness, so hopefully
more team representatives will come to this meeting. This meeting
works best when we have representatives from all of the teams.
For more information please check the  link.
Thank you for your support,
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
During Friday's FESCo meeting we were asked to approve a change to
the release schedule to accommodate translation string freeze deadlines
that somehow got left out of the new "no-alphas" schedule.
Several participants pointed out that Fedora has not enforced the
"string freeze" in many years, despite it being on the schedule until
now. Thus, we would like to revisit the string freeze policy to
determine if it is still valuable, and if so, how can/should it be enforced?
We'd like to explore a couple of questions:
* What exact things are frozen? Things like comps make sense to follow
Fedora freezes, but do things like anaconda? or system-config-printer?
* Can we automate some way of enforcing or at least detecting when
something changes a string in the freeze?
This ticket tracks the issue:
My name is Takuro Nagamoto. I am a Japanese translator at Red Hat, based in Brisbane, Australia.
I just wanted to let you know that I took over a coordinator role for Fedora Japanese translation from Noriko, who left Red Hat in January (greatly missed).
Hope to contribute to the Fedora Japanese translation team as a coordinator/translator/reviewer (I already have those privileges granted on zanata).
Name: Elena Metelli
Location: Milan, Italy
Profession: System Administrator
About me and the Fedora Project: I graduated in foreign languages but my true passion is IT. I work as System Administrator on RHEL-based systems in Italy and I've been a happy Fedora user since release 16 (I know, not a long time). I was a LUG member for a couple of years and, since April 2017, I write technical/news articles for an Italian Linux blog. I've always wanted to contribute to Fedora in some way and help with translation sounds like a good starting point! I know English decently and I used to translate content from ENG to ITA for a company offering monitoring services. I'm also a (newbie) Russian student.
GPG Keyid: AAC1F425
GPG fingerprint = EFA2 BFF8 C9C7 68BE 3072 3968 D910 93E5 AAC1 F425
so we are going to release F27 Beta tomorrow and we didn't enter any freeze
this time. If you didn't had the chance to get on the new strings, then do
it before Release Time, we will pull translations even for the release
You might know we are not releasing Fedora F27 Beta traditional Server, but
we will switch to Modular Server, which is not ready and will have its own
schedule. That means we will branch for Modular Server just after releasing
F27 Beta, in order to get on the new pages immediately. Unfortunately we
need also to freeze translations at the same time in production, so don't
be afraid if you don't see any changes.
We will, just after Fedora 27 Beta release, build staging websites with the
new Modular Server branch and you will be able to see your new strings
online. the plan is to merge this branch into master just before F27 GA, so
that means we will work on two branches simultaneously.
It sounds probably more complicated as it is, just remember we will enter a
special translation freeze tomorrow because we start working on Modular
Server. For any questions please just ask or ping me on IRC.
Thank you all for your hard work.