Hi Alberto,

here are my answers, inline to make it easier to understand, sorry for mailing list etiquette.

@transators: please feel free to amend/debate what I wrote, part of it comes from public discussions, the rest comes from my own wishes.

Le 12/01/2021 à 13:00, Alberto Rodriguez Sanchez a écrit :

Hello, Fedora Localization/Translations team,

I'm Alberto from CommOps, looking for your help to answer the next questions for solving one of my tickets[1]

Team name: Fedora Localization/Translations team

Fedora Localization team

Summary:

Preferred asynchronous communication channel (mailing list, discussion.fp.o, etc.):

Mailing list

Preferred synchronous (IRC channel, telegram, etc., none):

None probably is the best answer.

We have #fedora-l10n on IRC but it really is quiet and unfriendly for non technical expert.

Issue tracker:

https://pagure.io/fedora-l10n/tickets

Documentation:

https://fedoraproject.org/wiki/L10N

We should move to docs someday, but we are quite far from it: https://docs.fedoraproject.org/en-US/localization/ is almost empty.

Meetings times and locations (if applicable):

none.

Define the current responsibilities of your Team:

Make Fedora resource multilingual by translating or adapt content.

Contribute the global effort to make Linux a multilingual system by translating FLOSS projects.

Define the current goals of your Team:

Be fully integrated in the Fedora community processes.

What is the greatest strength of your team?

Were are a decentralized team, hundreds of volunteers each in its language. Few teams have multiple members.

What is the greatest weakness of your team?

We have almost no way to help each other and really collaborate.

What are the long term plans for the team (if applicable)?

Last time we talked about it, was at Flock Krakow in 2019.

From my notes (sorry I did not publish that anywhere):

* Support local communities by allowing them to use Fedora tools in their languages in their projects

* Support translators by providing them tools to make them more efficient

Examples:

* Translate FAS and Nuancier

* Organize virtual FAD focused on translation

* Translate the Silverblue webiste, its toolbox and its documentation

* make our documentation multilingual

Half of these objectives are now done :)

Some thanks to our actions:

* fedora documentation is now multilingual

Some thanks to external people:

* FAS 2, aka Noggin can be translated thanks to infra team

* Silverblue doc moved to Fedora docs

Is there anything you can consider a "Mission Statement" for Your Team?

Fedora mission is: /The Fedora Project envisions a world where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities./

I feel like it does the job for our team too, we make our part to make this mission comes true for the billions of Human who are not English native.

Is there a specific task or issue that your Team needs help for from the Mindshare Committee?

Localization is a fine place to discover the Fedora community, a fine place for inclusion, help us to make multilingualism part of the Fedora community. We have too many initiatives which can't be translated just because the toolkit was chosen without taking internationalization in the balance.

Wish list:

* Make Community blog and Fedora Magazine content available to non English native: rational, if someone feels like translating something, then it worth it. Even better, allow non English content to whatever team wants to try. * Make Package and modules description content available to non English native: rational, the whole system speak the user language but the dnf package. * Make all our tools available to non English native: rational, what Fedora uses should be reusable to local community to self organize.

Is there some function/activity you would like to see your Team doing that they aren’t doing currently?

Virtual FAD would be most welcome.

Thank you so much for your attention and participation.

thank you for your work, sorry for slow response,

Jean-Baptiste