On 17 July 2014 08:10, Peter Suter <petsu...@gmail.com> wrote: > On 17.07.2014 07:06, RjOllos wrote: >> On Wednesday, July 16, 2014 12:29:43 PM UTC-7, cboos wrote: >>> What's got out of control is that the current workflow as described in >>> [1] is way too complicated. I could barely keep up when I was more >>> involved in Trac, now with some distance I see that it's flawed, we need >>> to simplify and automate more. The main flaw was that I assumed that >>> after some time, we'll have an active committer and a team coordinator >>> for each language (the group 1) and that hasn't happened and won't. >>> >>> At this point, I think it's safer to assume that the translators will >>> prefer to work on Transifex, so that this should become our primary >>> source. We should have a mostly automated way to download everything >>> from there (synchronisation point), and commit the result, possibly >>> after the fixes done after checking the translations for >>> well-formedness. If such fixes are needed, we should then push them back >>> to Transifex (possibly overwriting edits done there since the >>> synchronisation point). >> >> I currently have about a half dozen tickets in progress. What I'm >> thinking is: >> >> - Close out those tickets by Friday 07/25 >> - Spend the next few days reviewing the tickets that were closed in >> the release, testing, trying to catch anything that may have been >> overlooked initially. String freeze on Monday 07/28. >> - Allow the two weeks for translators to update the catalogs. >> - Prepare the release on 08/08 or later. >> > > I'd also support a much simplified process, if reasonably possible via > automation, otherwise via documentation and reduced flexibility / quality if > needed. > > I'm personally not a user / contributor of translations and have never > looked into that process, so maybe I'm totally wrong, but for example to me > it would be acceptable to drop string freeze delays and force translators to > use SVN etc. (or whatever process reduces complexity the most **for the > release coordinator**). >
Hello, Speaking about translation, I am trying to help as much as possible for the french part. I participate to several other open source software translation and it seems that everybody is moving to Transifex these days. So I would vote to simplify the process and do everything in Transifex. It would greatly simplify the work of the language team coordinator (upload the changes, download the translation and commit). If some people need to work outside Transifex, they can always download/upload the .po file in Transifex. Is there something wrong with this approach ? Best regards, -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
