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:
I apologize top post...
On Fri, Oct 6, 2017 at 9:56 PM, Noriko Mizumoto <noriko.mizumoto(a)gmail.com>
> Anyone interested? I am :-)
> Topics I can think of;
> * Follow-up string freeze and schedule for Localization team
> * Review and Understand packages
> * Zanata and FLP
> Place, anywhere, where easier access to "translators".
> In fact, G11N or L10N FAD might cost expensive than the others, as the
> team coverage might be widest in Fedora project. Many of translators likely
> need to be funded to get there unless it is held at their hometown.😍
> I am super beginner on the funding subject, and I am much appreciated
> anyone to help.
> On Tue, Sep 26, 2017 at 1:06 AM, Zoltan Hoppar <hopparz(a)gmail.com> wrote:
>> Do we have next event place in schedule?
>> PGP: 06853DF7
>> trans mailing list -- trans(a)lists.fedoraproject.org
>> To unsubscribe send an email to trans-leave(a)lists.fedoraproject.org
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.
I'm coming back to translate and I found that Audacity in the Musician's
Guide is read only (at least in Spanish). Is this correct? May I ask why?
I wanted to finish it (it's 98% now) and correct some mistakes made by a
Thanks in advance.