Pootle's been running on sqlite!?<br><br>0.o WOW<br><br><div class="gmail_quote">On Mon, Jan 11, 2010 at 2:33 PM, Sayamindu Dasgupta <span dir="ltr"><<a href="mailto:sayamindu@gmail.com">sayamindu@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5">On Mon, Jan 11, 2010 at 9:08 PM, Chris Leonard <<a href="mailto:cjlhomeaddress@gmail.com">cjlhomeaddress@gmail.com</a>> wrote:<br>
> On Mon, Jan 11, 2010 at 7:40 AM, Sayamindu Dasgupta <<a href="mailto:sayamindu@gmail.com">sayamindu@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Hello,<br>
>> Just a small heads-up - we are tentatively going to upgrade to Pootle<br>
>> 2.0 at the end of this week. I don't have a fixed date and time yet (I<br>
>> just uncovered a problem with Pootle's symlink handling which causes<br>
>> issues with our entire git<-->pootle workflow), however, I do expect a<br>
>> downtime of around 24 hours (since the metadata and indexing data<br>
>> associated with each PO file need to be refreshed as a part of the<br>
>> migration process).<br>
>> I will keep this list posted on how things go<br>
>> Thank you,<br>
>> Sayamindu<br>
>><br>
><br>
> Sayamindu, thanks for all your work on keeping the SugarLabs / OLPC<br>
> localization infrastructure current.<br>
><br>
> Everyone should be aware that the Pootle 2.0 offers a substantially<br>
> different look-and-feel on the Home page to the Pootle ver 1.x servers we<br>
> have been using to date. To get a sense of what the Pootle 2.0 interface<br>
> will look like, you can look at the Pootle server where Pootle itself is<br>
> localized.<br>
><br>
> <a href="http://pootle.locamotion.org/" target="_blank">http://pootle.locamotion.org/</a><br>
><br>
> Those of you who may have been following along on Pootle users list will<br>
> know that Pootle 2.0 is truly a major revision of this tool. It still uses<br>
> the Translate Toolkit, but the web-serving elements have been completely<br>
> re-based on Django. While the actual string translation interface is<br>
> prettier, it is still fairly familiar looking, so there should not be much<br>
> of a re-learning curve for localizers. The re-basing on Django is said to<br>
> improve the ability to perform administrative tasks via the web-interface,<br>
> including better account and password management. which would be a win for<br>
> both admins and users. I'm looking forward to working with the new version.<br>
><br>
<br>
</div></div>Ah yes - among other things this will _finally_ let users reset their<br>
password if they forget :-)<br>
<br>
Pootle 2.0 should be _much_ _much_ better than what we currently have<br>
now, from both a UI perspective, as well as performance-wise. We will<br>
be switching to MySQL from sqlite as the backend store for user data,<br>
metadata of PO files, etc. This, plus the use of memcached will help<br>
us a lot in terms of scaling up as we progress (we currently have<br>
~1400 users registered, and serve around ~6300 PO files, which is<br>
itself a pretty large number)<br>
<br>
Thanks,<br>
<div><div></div><div class="h5">Sayamindu<br>
<br>
<br>
<br>
--<br>
Sayamindu Dasgupta<br>
[<a href="http://sayamindu.randomink.org/ramblings" target="_blank">http://sayamindu.randomink.org/ramblings</a>]<br>
_______________________________________________<br>
Localization mailing list<br>
<a href="mailto:Localization@lists.laptop.org">Localization@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/localization" target="_blank">http://lists.laptop.org/listinfo/localization</a><br>
</div></div></blockquote></div><br>