Organize a Fedora Docs FAD focused on internationalization support and tooling for Fedora documentation.
We need at least Adam Samalik (@asamalik) & Jean-Baptiste Holcroft (@jibecfed) to hack together on this, but welcome other contributors willing to work on the automation/CI of Fedora Docs. However, we believe that the two of us will be able to make translations work — Adam focusing on the Docs and build side, and Jean-Baptiste on the translations side.
We propose the event to take place in Strasbourg and organized by Jean-Baptiste (living there). Hosted in Shadok 
 https://www.shadok.strasbourg.eu/le-shadok-cest-quoi/ a hackerspace run by the city where local FLOSS NGO already meet.
We plan to finalize and validate our Fedora Docs translations prototype so that we are able to:
Both Adam and Jean-Baptiste will understand the pipeline well enough to operate it and mentor other people.
We'll also write down a set of requirements for production deployment in Fedora. We expect it being deployable in OpenShift.
A blog post on the CommBlog about the FAD and the result will be published.
According to the poll , could be 12 to 14 of April or 17 to 19th of may.
In 2016 , the Fedora Documentation changed tooling for https://docs.fedoraproject.org
This broke the localization process, translators can't contribute anymore.
At Flock 2017, Brian, David and Jean-Baptiste worked on a prototype  using po4a and Zanata.
In 2018, the docs team moved to Antora, and the work to support internationalization started again in November thanks to Adam.
Since February, Jean-Baptiste started working on the generation scripts, but it requires dedicated time to work together to move forward and answers remaining items.
 https://fedoramagazine.org/5tftw-2016-05-12/ see "Docs Activity Day: success!"
I am +1 to this funding. In full disclosure I may attend for part of the FAD to help with po4a and other areas where I have some skills. My attendance is not funded by this ticket and is not being requested.
+1 and I approved Adam attending since this doesn't hit our travel budget (which is already obligated for Red Hat's FY20Q1).
+1 — high impact for relatively low cost
Thank you all for your support, we'll work on this on April 12th and 13th :)
The vote is (+7,0,-0) after seven days. The request is approved.
Metadata Update from @bcotton:
- Issue close_status updated to: approved
- Issue status updated to: Closed (was: Open)
I never said thanks. Thanks! A trip report is coming shortly!
Trip report: https://communityblog.fedoraproject.org/fedora-docs-translations-fad-report/
Also, I'm a bit confused about where to submit the expense report. Should I do that in this very ticket? (I'm doing an internal transfer, but I believe we want those numbers to be public)
no need to post expenses here. The numbers will make it to the public budget.
to comment on this ticket.