<br><br> <div class="gmail_quote">On Sun, Jul 13, 2008 at 1:56 PM, Marco Pesenti Gritti <<a href="mailto:mpgritti@gmail.com">mpgritti@gmail.com</a>> wrote:<br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> <div class="Ih2E3d"> </div>Well, part of the translation process must be upstream. We are<br>checking in the translation in the upstream git and hence we need to<br>respect the upstream schedule.<br><br>I would personally encourage Sayamindu to start working upstream<br> already, for example by providing docs on how to translate<br>Glucose/activities on the sugarlabs wiki and by matching the pootle<br>groups with Glucose/Fructose modules list.<br><br>Do you see any downside with that approach?<br> <br>I'm *not* suggesting to host pootle on <a href="http://sugarlabs.org/" target="_blank">sugarlabs.org</a> yet.<br></blockquote> <div> </div> <div>Marco, </div> <div> </div> <div>I would say that Sayamindu is already doing exactly that sort of working with upstream in the form of trying to coordinate translation efforts into release schedules.  Logically enough, the conversation tends to happen on the OLPC localization list, lots of IAEP folks are there also, feel free to join in (or maybe just review the archives).</div> <div> </div> <div><a href="http://lists.laptop.org/listinfo/localization">http://lists.laptop.org/listinfo/localization</a></div> <div> </div> <div>I also agree it is best to use the d.l.o-hosted Pootle infrastructure until there is a real need to do something differently.  I would also note that localizers are working with Pootle-upstream to pursue improvements in that infrastructure. </div> <div> </div> <div> </div> <div>cjl</div> <div> </div> <div> </div></div>