Hi Fedora translation and docs members,
Let's make the proposal official. I've revised the Fedora Localization
Guide to reflect the changes.
Refer to the following guide section or scroll down:
Publishing Docs
When your doc translation is ready to be published on the Fedora
Documentation website, make a formal request for publishing the translation
by following these steps:
1/ File a bug against the publishing-requests component of the Fedora
Documentation product in Bugzilla. In the description field, remember to
mention the document name and language version you want to publish. If you
wish to publish multiple documents at once, file a separate bug for each of
the documents.
2/ Members of the docs-publishers FAS group will be notified of
your request and will get your translation published. Once the translation
gets published, they will close the bug for you.
Note #1: Alternative way to publish translations
The process mentioned above doesn't affect the translation teams that
already publish their docs translations. Only the translation teams that
lack necessary manpower or knowledge to publish docs on the Fedora
Documentation website are required to file bugs in Bugzilla to publish
their docs translations.
Note #2: Become a member of the docs-publishers FAS group
If you would like to help out with the publishing process and become a
member of the docs-publishers FAS group, contact the Docs Project. To make
the whole process faster, translation teams are advised to have at least one
member in the docs-publishers FAS group to take care of the team's
publishing requests.
Should you have any questions or comments, please ask on the trans and/or
docs list.
Thanks,
Petr Kovar
On Mon, 14 Nov 2011 21:10:38 +0100
Petr Kovar <pkovar(a)redhat.com> wrote:
Hi Fedora docs translators and writers,
After a discussion with shaiton following today's Fedora docs meeting, I
propose to formalize the process of publishing Fedora docs translations.
BACKGROUND
Currently, we don't have in place a formal process for publishing docs
translations. This means that we don't make it clear enough to our guide
owners and translators what and when should be published.
PROPOSAL
The proposal is to create a new Bugzilla component and a group of
default assignees for publishing translations to
docs.fedoraproject.org.
The group is consisted of members of the docs-publishers group (and
possibly also other people interested).
To get the translations published, Fedora translators are first required to
file a bug against the proposed component. This applies to any translation
of any document hosted on
docs.fedoraproject.org. Then the members of the
proposed group resolve the bug by publishing the requested translation.
RATIONALE
By using Bugzilla for the purposes of publishing translations, we can
easily keep track of what translations the translators actually want to
publish, at what time, and who is working with translators on publishing the
translations.
This makes the whole publishing process much more transparent.
At the same time, we satisfy the demand from some of our community members
to integrate the Bugzilla tool more deeply into our docs workflow.
To reduce a maintenance burden for individual docs owners, translators don't
file a bug directly against the relevant guide component in the Fedora
Documentation product.
REQUIREMENTS FOR TRANSLATORS
This requires each of the Fedora translation teams to have at least one
member communicating with the proposed docs publishers group in Bugzilla.
However, translators don't have to learn new tools and rather complex
processes specifically for Fedora docs, like working with Git, setting up an
environment for syncing translations between
Transifex.net and Git, or
publishing to
docs.fedoraproject.org with Publican.
NOTE
This proposal doesn't necessarily affect the translation teams that
are already publishing their docs translations. They can continue with
their existing workflow if it suits them and they have the manpower to do
so. In other words, this proposed process is completely optional for them.
COMMENTS
Your comments, thoughts, or ideas are most welcome!
Thanks,
Petr Kovar