Hi all,
Sorry for cross-posting, but both lists are concerned.
@docs Can you please check if the resources published on Tx for the Release Notes are up to date. I still have English strings when building them.
@trans Would you rather see daily updates to resources to translate on Transifex, with a risk of having daily a count of new/modified/dumped strings, or weekly updates, with a greater risk of having lots of new/modified/dumped strings?
Both have their pros and cons, I personally strongly believe in the "Release early, release often" motto. As a translator, for sure I would see some of yesterday's work (mine) be dumped, or not entirely (thanks to TM), but in a manageable way. People would also be able to build a localized version of the doc, and proofread it. Easier to spot issues in the final doc, and much more enjoyable to read that strings.
So I would really like to have a daily process in place to track git modifications for the Release Notes, which I use for the FreeIPA Management Guide (using the attached script).
Your thoughts?
J.
Given that we have a volunteer community, I'd suggest to push content which is as final as possible to avoid work which will be thrown away. On the other hand, daily pushes can also work if you just message the translators "start working now".
-d
On Mon, Oct 28, 2013 at 12:36 AM, Jérôme Fenal jfenal@gmail.com wrote:
Hi all,
Sorry for cross-posting, but both lists are concerned.
@docs Can you please check if the resources published on Tx for the Release Notes are up to date. I still have English strings when building them.
@trans Would you rather see daily updates to resources to translate on Transifex, with a risk of having daily a count of new/modified/dumped strings, or weekly updates, with a greater risk of having lots of new/modified/dumped strings?
Both have their pros and cons, I personally strongly believe in the "Release early, release often" motto. As a translator, for sure I would see some of yesterday's work (mine) be dumped, or not entirely (thanks to TM), but in a manageable way. People would also be able to build a localized version of the doc, and proofread it. Easier to spot issues in the final doc, and much more enjoyable to read that strings.
So I would really like to have a daily process in place to track git modifications for the Release Notes, which I use for the FreeIPA Management Guide (using the attached script).
Your thoughts?
J.
Jérôme Fenal
-- trans mailing list trans@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/trans
2013/10/28 Dimitris Glezos glezos@transifex.com:
Given that we have a volunteer community, I'd suggest to push content which is as final as possible to avoid work which will be thrown away. On the other hand, daily pushes can also work if you just message the translators "start working now".
So we could define two different process, for two kind of project pace: - daily for projects such as Release Notes, that need to go fast, and can't delay translators by not pushing updates. - weekly or when needed (e.g. manually) for longer term projects.
Can we expect a quick update to strings on Tx for the Release Notes? Discrepancies occur.
All in all, if translators find the update pace too rapid, then it will be to slow pushes to Tx, otherwise, please push. The sooner the better. Or we end up working on outdated forks.
Regards,
J.
On 10/29/2013 08:14 AM, Jérôme Fenal wrote:
2013/10/28 Dimitris Glezos glezos@transifex.com:
Given that we have a volunteer community, I'd suggest to push content which is as final as possible to avoid work which will be thrown away. On the other hand, daily pushes can also work if you just message the translators "start working now".
So we could define two different process, for two kind of project pace:
- daily for projects such as Release Notes, that need to go fast, and
can't delay translators by not pushing updates.
- weekly or when needed (e.g. manually) for longer term projects.
Can we expect a quick update to strings on Tx for the Release Notes? Discrepancies occur.
All in all, if translators find the update pace too rapid, then it will be to slow pushes to Tx, otherwise, please push. The sooner the better. Or we end up working on outdated forks.
Regards,
J.
trans mailing list trans@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/trans
We've discussed this before, and I do agree with you. The release notes are dynamic enough that they should be pushed often. Other guides have a broader scope, more content overlap, and longer development cycle that make pushing strings after a more thorough review a better strategy.
In this case, I knew I had to make a handful of changes based on developer feedback and I just needed to find time to commit them. By the way, Jérôme, thanks for your commits as well :)
Now that these updates are committed, I have uploaded the latest POTs. If you find more untranslated strings, we can investigate further.
-
Dimitris Glezos -
Jérôme Fenal -
Pete Travis