[Sugar-devel] Pootle SOS

Martin Abente martin.abente.lahaye at gmail.com
Mon Jul 28 11:27:13 EDT 2014


Ok!


On Mon, Jul 28, 2014 at 11:25 AM, Bernie Innocenti <bernie at codewiz.org>
wrote:

> Yes, I did it yesterday. The machine boots, but the apache virtual host
> doesn't seem to work any more.
>
> I'll leave the rest to you!
>
>
> On 07/28/2014 10:53 AM, Martin Abente wrote:
> > Hey Bernie!
> >
> > Did you get the time to update the machine?
> >
> >
> > On Thu, Jul 24, 2014 at 7:56 PM, Matthew Ciao <matthew at laptop.org.au
> > <mailto:matthew at laptop.org.au>> wrote:
> >
> >     Guys please let me know if there's anything I can do to help!
> >
> >
> >     On 25 July 2014 04:01, Martin Abente <martin.abente.lahaye at gmail.com
> >     <mailto:martin.abente.lahaye at gmail.com>> wrote:
> >
> >         Hey Bernie!
> >
> >         I (literally) just finished my first round of tests setting up a
> >         pootle 2.5.1.1 instance from scratch. The results are promising:
> >
> >          1. Setting up a pootle instance from scratch was very
> >             straightforward.
> >          2. 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.
> >
> >         Other premature comments:
> >
> >           * pootle imported _almost_ all the languages, but I had to
> >             manually add languages like "guarani". I still don't know
> >             why, ideas?
> >           * 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?
> >
> >
> >         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.
> >
> >
> >     Bernie if you don't have time to work on what Martin needs I can
> >     step in, no problems at all.
> >
> >     Cheers!
> >
> >
> >
> >
> >         On Thu, Jul 24, 2014 at 1:03 PM, Bernie Innocenti
> >         <bernie at codewiz.org <mailto:bernie at codewiz.org>> wrote:
> >
> >             Martin is taking Pootle, but if you have time to help with
> >             it, I think
> >             it would be appreciated.
> >
> >             I think I'll start the work on Sunday. Martin, would you
> >             have time?
> >
> >
> >             On 07/21/2014 07:08 AM, Matthew Ciao wrote:
> >             > Hi folks,
> >             >
> >             > it looks like you're already in a good position in terms
> >             of help from
> >             > rgs and/or icarito so I don't think I would be very useful
> >             at the meeting.
> >             >
> >             > This said, if all goes bad please involve me in the Pootle
> >             mission as I
> >             > am more than keen to lend a hand! :)
> >             >
> >             > Best,
> >             >
> >             > Matthew
> >             >
> >             > On Jul 21, 2014 4:15 AM, "Bernie Innocenti"
> >             <bernie at codewiz.org <mailto:bernie at codewiz.org>
> >             > <mailto:bernie at codewiz.org <mailto:bernie at codewiz.org>>>
> >             wrote:
> >             >
> >             >     +rgs, +icarito (both of which expressed interest in
> >             supporting Pootle)
> >             >
> >             >
> >             >     On 07/20/2014 01:36 PM, Martin Abente wrote:
> >             >     > Hello everyone,
> >             >     >
> >             >     > What about investing some minutes this week to talk
> >             about Pootle's
> >             >     > status, what is missing and how can we get it back
> >             to life?
> >             >     >
> >             >     > I suggest this Wednesday 23 July, 13:00 UTC.
> >             >
> >             >     It's a bit early for me, and definitely too early for
> rgs.
> >             >     Can we do 15:00 UTC?
> >             >
> >             >
> >             >     In case I miss the meeting, here's a full dump of my
> mind:
> >             >
> >             >      - you, rgs and icarito already have root to
> >             newpootle.sugarlabs.org <http://newpootle.sugarlabs.org>
> >             >     <http://newpootle.sugarlabs.org>
> >             >
> >             >      - full backups of the old pootle machine are on
> >             freedom, and all of you
> >             >     have root access there too
> >             >
> >             >      - Sysadmin documentation is in the usual place (the
> >             wiki). There are
> >             >     several pages written by the previous Pootle
> maintainers:
> >             >
> >             >       http://wiki.sugarlabs.org/go/Service/translate
> >             >       http://wiki.sugarlabs.org/go/Service/Pootle
> >             >       http://wiki.sugarlabs.org/go/Service/Pootle2.5
> >             >       http://wiki.sugarlabs.org/go/Machine/pootle
> >             >
> >             >      The documentation needs to be consolidated into a
> >             single page and
> >             >     updated. *PLEASE*, don't neglect this step; it will
> >             save a lot of time
> >             >     to future maintainers.
> >             >
> >             >      - The newpootle machine is still running Ubuntu 12.04
> >             LTS. I strongly
> >             >     recommend upgrading it to 14.04 (trusty) before
> >             proceeding. It won't
> >             >     take more than 1h of work and I can do this.
> >             >
> >             >      - There's an outdated instance of Pootle already
> >             running on newpootle.
> >             >     It was setup by a previous volunteer, but never
> >             transitioned into
> >             >     production due to difficulties with the git
> >             integration (iirc, cjl might
> >             >     have more on this).
> >             >
> >             >      - I strongly recommend upgrading to the latest
> >             release of Pootle before
> >             >     doing anything else.
> >             >
> >             >      - Then, the database and data from the backups needs
> >             to be restored and
> >             >     probably converted to the Pootle 2.5 format (good luck
> >             with Django db
> >             >     migration!)
> >             >
> >             >      - Finally, the part where all past maintainers seem
> >             to get stuck: make
> >             >     the Pootle <-> git integration work. I don't know what
> >             the actual
> >             >     problem is; pushing to git should be a basic feature
> >             of a translation
> >             >     system and I'm surprised this can't be made to work
> >             out of the box.
> >             >
> >             >      - When everything works (and please test it well,
> >             Pootle likes to crash
> >             >     and burn under load), we can change the DNS to point
> >             the CNAME
> >             >     translate.sugarlabs.org
> >             <http://translate.sugarlabs.org>
> >             <http://translate.sugarlabs.org> to
> >             >     newpootle. Follow the Service/nameserver
> >             >     documentation page to do this, or I can do it in 2
> >             minutes.
> >             >
> >             >     --
> >             >      _ // Bernie Innocenti
> >             >      \X/  http://codewiz.org
> >             >
> >
> >
> >             --
> >              _ // Bernie Innocenti
> >              \X/  http://codewiz.org
> >
> >
> >
> >
>
>
> --
>  _ // Bernie Innocenti
>  \X/  http://codewiz.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20140728/a813c878/attachment.html>


More information about the Sugar-devel mailing list