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
the internationalization of the Fedora Documentation has seen some
1. the homepage conversion is now complete, it doesn't contain markup
anymore! But sorry, you have to translate it again.
2. I configured all projects in the translation platform All projects
start with "fedora-docs-l10n"
Translating everything means a lot of work: 92 375 messages containing 1
784 225 words.
There is a lot of duplication in some docs (install guide, admin guide,
...), but if a single person had to do this, it would represent an
effort of 112 days (with 8h of work per day and 2000 words/hour).
In terms of priority, I suggest:
2. Project description:
3. User facing content (teams descriptions, release notes, how-tos,...)
4. Dev content (packaging guideline, install guide, administrator
The global mindset I decided to apply: there is no content not worth
translating. Only you decide if it worth it or not.
I don't expect any language to reach 100%. Don't force yourself, just do
what you like.
Next step is publication, which is under Adam's responsibility (I also
asked for help from one addition infrastructure team member).
By the way, following the simple doctrine "friends of my friends are my
friends", I suggested Asciidoc.org to reuse our system for their
translation, and offered to host them in our translation platform.
After all, it's thanks to Asciidoc and Antora that we have a
documentation system. It's my way to say thank you.
thanks to a kind contributor , we now have browser language
auto-detection fixed on: https://whatcanidoforfedora.org
Translation statistics of this websites shows:
* 13 languages at 100% ca, cs, de, en, es, fr, gu, hu, nl, pt_BR, sv, tr, uk
* 1 language > 80% : fi
* 2 languages > 50% : ar sq
* 9 languages < 50% : zh_CN, ko, ja, en_GB, id, it, ru, he, pt
I think we can do better, especially for Asiatic languages.
Have a nice time translating!
yesterday I added our first new upstream project: debbuild 
This raised two questions to me:
1. why should the Fedora community pay to host someone else project? We
will reach the limit of our hosting some day, we need to be ready to
2. why would a project use our infrastructure? Projects can host their
own Weblate instance and some prefer to use Pull Request instead of web
I feel like we should start to write about this, and that probably means
we will have to exchange hosting for internationalization improvement to
Here is a page to host this content
My proposal would be to allow us to vote when we all a new line in the
guidelines, and work on detecting the correct application of these
This would be I think a good way for the Fedora community to bring
progress in the FOSS ecosystem.
What do you think?