<div dir="ltr">Hey Bernie!<div><br></div><div>Did you get the time to update the machine?</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 24, 2014 at 7:56 PM, Matthew Ciao <span dir="ltr"><<a href="mailto:matthew@laptop.org.au" target="_blank">matthew@laptop.org.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Guys please let me know if there's anything I can do to help!<br><div class="gmail_extra"><br><br><div class="gmail_quote">
<div class="">On 25 July 2014 04:01, Martin Abente <span dir="ltr"><<a href="mailto:martin.abente.lahaye@gmail.com" target="_blank">martin.abente.lahaye@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hey Bernie!<div><br></div><div>I (literally) just finished my first round of tests setting up a pootle 2.5.1.1 instance from scratch. The results are promising:</div>
<div><ol><li>Setting up a pootle instance from scratch was very straightforward. <br>
</li><li>Creating a new project and integrating it with git versioning was also surprisingly straightforward. In fact, no custom bits were require to make pootle import Sugar project and start making commits to the remote repository.</li>
</ol></div><div>Other premature comments:</div><div><ul><li>pootle imported _almost_ all the languages, but I had to manually add languages like "guarani". I still don't know why, ideas?<br></li><li>I still need to check the SL wiki to have some ideas of how it would be better to organize the projects. IIRC, our previous pootle instance followed the same sugar modules like sucrose, fructose, etc. Suggestions?<br>
</li></ul></div><div><br></div><div>I don't think I will have the time to work on this during the weeking (because of the wedding), but if you could make sure the server is ready, I can continue over the week.</div></div>
</blockquote><div> </div></div><div>Bernie if you don't have time to work on what Martin needs I can step in, no problems at all. </div><div><br></div><div>Cheers!</div><div><div class="h5"><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><br></div></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 24, 2014 at 1:03 PM, Bernie Innocenti <span dir="ltr"><<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Martin is taking Pootle, but if you have time to help with it, I think<br>
it would be appreciated.<br>
<br>
I think I'll start the work on Sunday. Martin, would you have time?<br>
<div><br>
<br>
On 07/21/2014 07:08 AM, Matthew Ciao wrote:<br>
> Hi folks,<br>
><br>
> it looks like you're already in a good position in terms of help from<br>
> rgs and/or icarito so I don't think I would be very useful at the meeting.<br>
><br>
> This said, if all goes bad please involve me in the Pootle mission as I<br>
> am more than keen to lend a hand! :)<br>
><br>
> Best,<br>
><br>
> Matthew<br>
><br>
> On Jul 21, 2014 4:15 AM, "Bernie Innocenti" <<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a><br>
</div><div>> <mailto:<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a>>> wrote:<br>
><br>
> +rgs, +icarito (both of which expressed interest in supporting Pootle)<br>
><br>
><br>
> On 07/20/2014 01:36 PM, Martin Abente wrote:<br>
> > Hello everyone,<br>
> ><br>
> > What about investing some minutes this week to talk about Pootle's<br>
> > status, what is missing and how can we get it back to life?<br>
> ><br>
> > I suggest this Wednesday 23 July, 13:00 UTC.<br>
><br>
> It's a bit early for me, and definitely too early for rgs.<br>
> Can we do 15:00 UTC?<br>
><br>
><br>
> In case I miss the meeting, here's a full dump of my mind:<br>
><br>
> - you, rgs and icarito already have root to <a href="http://newpootle.sugarlabs.org" target="_blank">newpootle.sugarlabs.org</a><br>
</div>> <<a href="http://newpootle.sugarlabs.org" target="_blank">http://newpootle.sugarlabs.org</a>><br>
<div><div>><br>
> - full backups of the old pootle machine are on freedom, and all of you<br>
> have root access there too<br>
><br>
> - Sysadmin documentation is in the usual place (the wiki). There are<br>
> several pages written by the previous Pootle maintainers:<br>
><br>
> <a href="http://wiki.sugarlabs.org/go/Service/translate" target="_blank">http://wiki.sugarlabs.org/go/Service/translate</a><br>
> <a href="http://wiki.sugarlabs.org/go/Service/Pootle" target="_blank">http://wiki.sugarlabs.org/go/Service/Pootle</a><br>
> <a href="http://wiki.sugarlabs.org/go/Service/Pootle2.5" target="_blank">http://wiki.sugarlabs.org/go/Service/Pootle2.5</a><br>
> <a href="http://wiki.sugarlabs.org/go/Machine/pootle" target="_blank">http://wiki.sugarlabs.org/go/Machine/pootle</a><br>
><br>
> The documentation needs to be consolidated into a single page and<br>
> updated. *PLEASE*, don't neglect this step; it will save a lot of time<br>
> to future maintainers.<br>
><br>
> - The newpootle machine is still running Ubuntu 12.04 LTS. I strongly<br>
> recommend upgrading it to 14.04 (trusty) before proceeding. It won't<br>
> take more than 1h of work and I can do this.<br>
><br>
> - There's an outdated instance of Pootle already running on newpootle.<br>
> It was setup by a previous volunteer, but never transitioned into<br>
> production due to difficulties with the git integration (iirc, cjl might<br>
> have more on this).<br>
><br>
> - I strongly recommend upgrading to the latest release of Pootle before<br>
> doing anything else.<br>
><br>
> - Then, the database and data from the backups needs to be restored and<br>
> probably converted to the Pootle 2.5 format (good luck with Django db<br>
> migration!)<br>
><br>
> - Finally, the part where all past maintainers seem to get stuck: make<br>
> the Pootle <-> git integration work. I don't know what the actual<br>
> problem is; pushing to git should be a basic feature of a translation<br>
> system and I'm surprised this can't be made to work out of the box.<br>
><br>
> - When everything works (and please test it well, Pootle likes to crash<br>
> and burn under load), we can change the DNS to point the CNAME<br>
</div></div>> <a href="http://translate.sugarlabs.org" target="_blank">translate.sugarlabs.org</a> <<a href="http://translate.sugarlabs.org" target="_blank">http://translate.sugarlabs.org</a>> to<br>
<div><div>> newpootle. Follow the Service/nameserver<br>
> documentation page to do this, or I can do it in 2 minutes.<br>
><br>
> --<br>
> _ // Bernie Innocenti<br>
> \X/ <a href="http://codewiz.org" target="_blank">http://codewiz.org</a><br>
><br>
<br>
<br>
--<br>
_ // Bernie Innocenti<br>
\X/ <a href="http://codewiz.org" target="_blank">http://codewiz.org</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div></div></div><br></div></div>
</blockquote></div><br></div>