<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>On Feb 21, 2014, at 9:19 AM, Matjaz Horvat <<a href="mailto:matjaz@mozilla.com">matjaz@mozilla.com</a>> wrote:</div><div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><div>Shane,<br><br></div>What you described would be an ideal set up - having the stage server support all locales in GitHub and updating regurarly from GitHub. That way localizers could test their translations.<br>
<br></div><div>A good enough set up would be to have an English-only stage, which needs to be in sync with strings on GitHub and Verbatim that localizers are currently working on. That way localizers could see where and how you use original strings.<br>
<br></div></div></blockquote><div><br></div><div>Hi Matjaz, </div><div><br></div><div>I'm still a little bit fuzzy on the workflow here. </div><div><br></div><div>1) What's the process that you'll use to initially import <a href="https://github.com/mozilla/fxa-content-server/tree/master/locale">https://github.com/mozilla/fxa-content-server/tree/master/locale</a> into Verbatim?</div><div>2) As localizers work on those strings, how and at what frequency does that work get back to us?</div><div>3) If we make changes to or add strings, how and at what frequency do we downstream that to Verbatim? </div><div>4) What happens when we make a change to a string that was previously translated? Is that string re-marked as "needing translation" in Verbatim?</div><div> </div><div>I'm very ignorant about all this, so if there's documentation on this workflow, please point me to it.</div><div><br></div><div>We have a "nightly" server (<a href="https://accounts.dev.lcip.org/">https://accounts.dev.lcip.org/</a>) which automatically deploys from master each night. After the translations are committed back to our repo, the translators should see their work the next day. Is this a good start?</div><div><br></div><div>-chris</div><div><br></div><div><br></div><br><blockquote type="cite"><div dir="ltr"><div>-Matjaž<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Feb 21, 2014 at 5:59 PM, Shane Tomlinson <span dir="ltr"><<a href="mailto:stomlinson@mozilla.com" target="_blank">stomlinson@mozilla.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 21/02/2014 14:08, Matjaz Horvat wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey Zach,<br>
<br>
This looks ok. I'll set up a new project in Verbatim and notify our<br>
localizers.<br>
<br>
Thanks,<br>
Matjaž<br>
</blockquote>
<br>
<br></div>
Chris, Zach and Nick,<br>
Matjaz asked which server the localizers will use as a reference.<br>
<br>
Matjaz, can you correct any misunderstandings I have. Localizers ask for a couple of weeks to get translations in order once we send them new strings. During that window, they use a reference server to see their localizations in action, allowing them to make any adjustments before we release to production.<br>
<br>
Matjaz asked if we would use the staging server [1]. We could either use stage, or we could set up a separate l10n server that mirrors the code on stage with the exception of the new translations that are added as they come in.<br>
<br>
Shane<br>
<br>
===========<br>
<br>
[1] - <a href="https://accounts.stage.mozaws.net/" target="_blank">https://accounts.stage.mozaws.<u></u>net/</a><br>
<br>
</blockquote></div><br></div>
</blockquote></div><br></body></html>