Replying to [ticket:15 pravins]:

Jean-Baptiste has raised these question. Creating ticket since these are very important while improving Wiki.

1. How to know when a translation is online ?
   1.a when it's for a website, we should have two times a day update : https://fedoraproject.org/wiki/Websites/workflow#l10n but the git log says otherwise, what's the process ?
   [[BR]]
   Assuming this question asks the schedule, it basically follows the task
   schedule of 'Web Sites' (under Schedule page) but it can be affected and
   changed by slip. Generally website team kindly inform us by posting in
   trans at lists when they push the POT/POs.
   E.g. https://fedorapeople.org/groups/schedule/f-23/f-23-web-tasks.html
   [[BR]]
   1.b when it's doc, what's the rythme ?
   [[BR]]
   Same as above,
   E.g. https://fedorapeople.org/groups/schedule/f-23/f-23-docs-tasks.html
   [[BR]]
   1.c when it's a RPM, what's the rythme ?
   [[BR]]
   My memory says that any 0-day rel-notes translation is
   not included in a RPM. But I might be wrong, this is totally up to Docs
   team decision. Any other documentation is not included in RPM.
   [[BR]]

2. Global release process and out-of-release-process
   2.a if we missed a milestone, I think we can't have a second-chance, but after the official release ?
   2.b if we improve the documentation of fedora 23 and improve fedora 22 documentation in the same time, is there a way to put it online ?
   [[BR]]
   Each language team can elect a person within the team who can publish
   guides translated in their language any time by themselves. This person
   then should join Docs team and gain necessary permission for publishing.
   [[BR]]

3. Fedora Groups
   3.a What does the upstream group means ? The applications of the fedora project ?
   3.b What does the main group means ? The applications of individual projects not related to Fedora but we help to translate ?
   [[BR]]
   This is exact our pain point, and was discussed during FAD in Tokyo. The
   group names are inherited from Transifex, and can bring us some
   confusion. I am expecting that new zanata feature to be implemented soon
   can improve this problem, thus atm we decided to leave them not changed.

• Upstream - upstream packages against fedora, it means that projects under this group are used by other OSs apart from Fedora, and those may have their own development cycles thus may not follow Fedora development cycle.

• Main - packages for fedora project, it means that projects under this group follow fedora development cycle.
  [[BR]]

  1. Test translations
     4.a how to test translations of a software without waiting for a test ISO of Fedora ?
     [[BR]]
     By replacing mo file(?!) with latest translation under particular
     directory, that package can run with latest translation locally. But I
     am not sure how-to.
     There is 'Deckard' web application (for Gnome) which can be used for
     this kind of application build. Again I have not tried this with fedora
     packages.
     It is nice to have this documented, once you figure out how-to.
     [[BR]]

4.a how to test translations of a software without waiting for a test ISO of Fedora ?

By replacing mo file(?!) with latest translation under particular directory, that package can run with latest translation locally. But I am not sure how-to.
There is 'Deckard' web application (for Gnome) which can be used for this kind of application build. Again I have not tried this with fedora packages.

Deckard seems to be just for the (glade-based) GUI.

There are two parts in solving this question: getting the new software (and whatever it needs) and making it use the updated translations. I won't touch the first one.

For the second one Tiansworld has updated the wiki: [https://fedoraproject.org/wiki/L10N/Translate_on_Zanata#Testing Translate on Zanata -> Testing].

If you don't want to mess with package owned files during testing, you may use chroot jails, bind mounts, unionfs, or mount namespaces. Say you have an empty directory in ~/l10n-test/newroot and the new .mo files in ~/l10n-test/mo, possibly mixed with a copy of untouched -mo files. You could, as root:
{{{#!sh
mount --bind / /home/USER/l10n-test/newroot
mount --bind /home/USER/l10n-test/mo /home/USER/l10n-test/newroot/usr/share/locale/YOUR_LOCALE/LC_MESSAGES/
}}}
Then, as user:
{{{#!sh
chroot ~/l10n-test/newroot
}}}
and start from there whatever programs you want to test.

That doesn't affect the rest of your system, but may or may not be enough depending on your configuration and mount points.

Thanks Noriko and lonemadmax for your answers. I am closing this ticket now. Feel free to open if anything remaining.

Reopening..
Unfortunately we dont have any documentation around these points in Wiki. As mentioned by Jean even workflow itself not clear.

We should have
1. Wiki page for Fedora Website translation.
2. Wiki for testing translation before RPM build. (This we can move to FLTG)