* For software localization
- We have got 42 days for translation before package rebuild starts.
Is it possible to split this translation task in two phases
(Translation - 30 days and Review - 12 days)? If we split it this way
and put the package rebuild step between these two tasks, FLP members
will get a chance to test and review Fedora packages on their local
machine and can provide a better localization during the Review
period. So, the concern here is to concentrate on *review* of Fedora
software applications.
- Another important thing is, we (FLP members) are most of the time
clueless whether our translations has got in or not. We get to know
only after the package rebuilds, if we find time on thorough testing.
So, how about having some automated mechanism to notify FLP team that
their translations has been included in the latest package rebuild?
This could be done if we setup some automation that can send a
notification e-mail to fedora-trans-announce list *at the end of the
package rebuild period* that abc, xyz packages has been rebuilt in
the period from *start package rebuild* to *end package rebuild*.
Changed. Let me know if something is wrong.