Re: [Sugar-devel] Pootle SOS

2014-08-06 Thread Chris Leonard 
At 18:00 eastern, yes

On Wed, Aug 6, 2014 at 1:07 PM, Martin Abente
 wrote:
> Hello Chris,
>
> Think you can make it to today's meeting?
>
> Regards,
> Martin.
>
>
> On Wed, Aug 6, 2014 at 9:29 AM, Martin Abente
>  wrote:
>>
>> 22:00 UTC is fine! See you guys there!
>>
>>
>> On Wed, Aug 6, 2014 at 9:11 AM, Matthew Ciao 
>> wrote:
>>>
>>> Hi everyone,
>>>
>>> anybody else who can make it for the time proposed by Bernie (22:00 UTC)?
>>>
>>> If not we can stick with 15:00 UTC.
>>>
>>> Thx,
>>>
>>> Matthew
>>>
>>> On Aug 5, 2014 10:02 AM, "Matthew Ciao"  wrote:

 22:00 UTC works for me!


 On 5 August 2014 10:00, Bernie Innocenti  wrote:
>
> How about 22:00 UTC? It's 18:00 EDT and 8:00 AEST.
>
>
> http://www.timeanddate.com/worldclock/converted.html?iso=20140806T18&p1=43&p2=152&p3=0&p4=137
>
> On 08/04/2014 07:15 PM, Matthew Ciao wrote:
> > Hi all,
> >
> > this meeting translates to 1am for me so I will hardly be able to
> > join.
> >
> > Will follow any email update anyway!
> >
> > /Matthew/
> >
> >
> > On 5 August 2014 03:55, Martin Abente  > > wrote:
> >
> >
> >
> > On Mon, Aug 4, 2014 at 1:24 PM, Bernie Innocenti
> >  > > wrote:
> >
> > On 07/31/2014 01:48 PM, Martin Abente wrote:
> > > Hey guys,
> > >
> > > A few updates:
> > >
> > >   * I just finished upgrading the exiting instance to
> > Pootle
> > 2.5.1.1
> > > [1]. I don't know exactly what can I test to make sure
> > the
> > upgrade
> > > is working properly, @cjl suggestions?
> > >   * Next step would be a fix version control integration.
> > >
> > > A few concerns:
> > >
> > >   * This update process feels like walking in the dark, the
> > > documentation does not help much to understand what is
> > expected to
> > > work or what are the uses cases for our instance.
> >
> > Last time someone worked on Pootle, the documentation was
> > clearly
> > incorrect. Somewhere, the documentation recommended deploying
> > Pootle as
> > a stand-alone process, directly listening on port 80 (i.e.
> > without
> > Apache in front of it).
> >
> > So, yeah, take the documentation with a grain of salt.
> >
> >
> > >   * I honestly worry that maintaining the current instance
> > (upgraded or
> > > not) will not be possible in the long term.
> >
> >
> > That was also my impression: Pootle looks like an
> > unmaintainable
> > mess,
> > and it's not getting better. In production, it crashes and
> > OOMs for
> > mysterious reasons, and that's why it's now running on a
> > separate VM.
> >
> > Pootle can certainly be debugged and ultimately fixed, but it
> > would
> > require long-term involvement with upstream to make their
> > codebase more
> > robust.
> >
> >
> > > How about a meeting this Wednesday, August 6? To discuss
> > about
> > these
> > > concerns and possible alternatives.
> >
> > Good idea. Can we do it at 11:00 EDT (15:00 UTC)?
> >
> >
> > 15:00 UTC (Wednesday, August 6) sounds good to me :)
> >
> >
> >
> >
> > >  1. http://newpootle.sugarlabs.org/about/
> > >
> > >
> > >
> > >
> > > On Thu, Jul 31, 2014 at 2:21 AM, Matthew Ciao
> > mailto:matt...@laptop.org.au>
> > >  > >>
> > wrote:
> > >
> > > Let me know if you need any help up there Martin...
> > Django
> > can be a
> > > serious pain in the deck. :)
> > >
> > > Cheers
> > >
> > >
> > >
> > > On 31 July 2014 00:25, Martin Abente
> >  > 
> > >  > >> wrote:
> > >
> > > Hey Matthew,
> > >
> > > Thanks! Right now I am trying to figure out how to
> > upgrade
> > > pootle packages, but after I am done we look at
> > that :)
> > >
> > >
> > > On Wed, Jul 30, 2014 at 10:20 AM, Matthew Ciao
> > > >

Re: [Sugar-devel] Pootle SOS

2014-08-04 Thread Bernie Innocenti 
How about 22:00 UTC? It's 18:00 EDT and 8:00 AEST.

http://www.timeanddate.com/worldclock/converted.html?iso=20140806T18&p1=43&p2=152&p3=0&p4=137

On 08/04/2014 07:15 PM, Matthew Ciao wrote:
> Hi all, 
> 
> this meeting translates to 1am for me so I will hardly be able to join.
> 
> Will follow any email update anyway! 
> 
> /Matthew/
> 
> 
> On 5 August 2014 03:55, Martin Abente  > wrote:
> 
> 
> 
> On Mon, Aug 4, 2014 at 1:24 PM, Bernie Innocenti  > wrote:
> 
> On 07/31/2014 01:48 PM, Martin Abente wrote:
> > Hey guys,
> >
> > A few updates:
> >
> >   * I just finished upgrading the exiting instance to Pootle
> 2.5.1.1
> > [1]. I don't know exactly what can I test to make sure the
> upgrade
> > is working properly, @cjl suggestions?
> >   * Next step would be a fix version control integration.
> >
> > A few concerns:
> >
> >   * This update process feels like walking in the dark, the
> > documentation does not help much to understand what is
> expected to
> > work or what are the uses cases for our instance.
> 
> Last time someone worked on Pootle, the documentation was clearly
> incorrect. Somewhere, the documentation recommended deploying
> Pootle as
> a stand-alone process, directly listening on port 80 (i.e. without
> Apache in front of it).
> 
> So, yeah, take the documentation with a grain of salt.
> 
> 
> >   * I honestly worry that maintaining the current instance
> (upgraded or
> > not) will not be possible in the long term.
> 
> 
> That was also my impression: Pootle looks like an unmaintainable
> mess,
> and it's not getting better. In production, it crashes and OOMs for
> mysterious reasons, and that's why it's now running on a
> separate VM.
> 
> Pootle can certainly be debugged and ultimately fixed, but it would
> require long-term involvement with upstream to make their
> codebase more
> robust.
> 
> 
> > How about a meeting this Wednesday, August 6? To discuss about
> these
> > concerns and possible alternatives.
> 
> Good idea. Can we do it at 11:00 EDT (15:00 UTC)?
> 
> 
> 15:00 UTC (Wednesday, August 6) sounds good to me :)
>  
> 
> 
> 
> >  1. http://newpootle.sugarlabs.org/about/
> >
> >
> >
> >
> > On Thu, Jul 31, 2014 at 2:21 AM, Matthew Ciao
> mailto:matt...@laptop.org.au>
> > >>
> wrote:
> >
> > Let me know if you need any help up there Martin... Django
> can be a
> > serious pain in the deck. :)
> >
> > Cheers
> >
> >
> >
> > On 31 July 2014 00:25, Martin Abente
>  
> >  >> wrote:
> >
> > Hey Matthew,
> >
> > Thanks! Right now I am trying to figure out how to upgrade
> > pootle packages, but after I am done we look at that :)
> >
> >
> > On Wed, Jul 30, 2014 at 10:20 AM, Matthew Ciao
> > mailto:matt...@laptop.org.au>
> >>
> wrote:
> >
> > Hi Martin,
> >
> > maybe if you have time you / we can also work out
> a minimal
> > secure setup?
> >
> > Looks like newpootle needs a bit of firewalling to
> start with:
> >
> > sudo /sbin/iptables -L -nv
> > Chain INPUT (policy ACCEPT 324 packets, 29890 bytes)
> >  pkts bytes target prot opt in out source
> > destination
> >
> > Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
> >  pkts bytes target prot opt in out source
> > destination
> >
> > Chain OUTPUT (policy ACCEPT 186 packets, 20370 bytes)
> >  pkts bytes target prot opt in out source
> > destination
> >
> > Cheers
> >
> >
> > On 30 July 2014 17:46, Matthew Ciao
> mailto:matt...@laptop.org.au>
> >  >> wrote:
> >
> > Thanks B

Re: [Sugar-devel] Pootle SOS

2014-08-04 Thread Martin Abente 
On Mon, Aug 4, 2014 at 1:24 PM, Bernie Innocenti  wrote:

> On 07/31/2014 01:48 PM, Martin Abente wrote:
> > Hey guys,
> >
> > A few updates:
> >
> >   * I just finished upgrading the exiting instance to Pootle 2.5.1.1
> > [1]. I don't know exactly what can I test to make sure the upgrade
> > is working properly, @cjl suggestions?
> >   * Next step would be a fix version control integration.
> >
> > A few concerns:
> >
> >   * This update process feels like walking in the dark, the
> > documentation does not help much to understand what is expected to
> > work or what are the uses cases for our instance.
>
> Last time someone worked on Pootle, the documentation was clearly
> incorrect. Somewhere, the documentation recommended deploying Pootle as
> a stand-alone process, directly listening on port 80 (i.e. without
> Apache in front of it).
>
> So, yeah, take the documentation with a grain of salt.
>
>
> >   * I honestly worry that maintaining the current instance (upgraded or
> > not) will not be possible in the long term.
>
>
> That was also my impression: Pootle looks like an unmaintainable mess,
> and it's not getting better. In production, it crashes and OOMs for
> mysterious reasons, and that's why it's now running on a separate VM.
>
> Pootle can certainly be debugged and ultimately fixed, but it would
> require long-term involvement with upstream to make their codebase more
> robust.
>
>
> > How about a meeting this Wednesday, August 6? To discuss about these
> > concerns and possible alternatives.
>
> Good idea. Can we do it at 11:00 EDT (15:00 UTC)?
>

15:00 UTC (Wednesday, August 6) sounds good to me :)


>
>
> >  1. http://newpootle.sugarlabs.org/about/
> >
> >
> >
> >
> > On Thu, Jul 31, 2014 at 2:21 AM, Matthew Ciao  > > wrote:
> >
> > Let me know if you need any help up there Martin... Django can be a
> > serious pain in the deck. :)
> >
> > Cheers
> >
> >
> >
> > On 31 July 2014 00:25, Martin Abente  > > wrote:
> >
> > Hey Matthew,
> >
> > Thanks! Right now I am trying to figure out how to upgrade
> > pootle packages, but after I am done we look at that :)
> >
> >
> > On Wed, Jul 30, 2014 at 10:20 AM, Matthew Ciao
> > mailto:matt...@laptop.org.au>> wrote:
> >
> > Hi Martin,
> >
> > maybe if you have time you / we can also work out a minimal
> > secure setup?
> >
> > Looks like newpootle needs a bit of firewalling to start
> with:
> >
> > sudo /sbin/iptables -L -nv
> > Chain INPUT (policy ACCEPT 324 packets, 29890 bytes)
> >  pkts bytes target prot opt in out source
> > destination
> >
> > Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
> >  pkts bytes target prot opt in out source
> > destination
> >
> > Chain OUTPUT (policy ACCEPT 186 packets, 20370 bytes)
> >  pkts bytes target prot opt in out source
> > destination
> >
> > Cheers
> >
> >
> > On 30 July 2014 17:46, Matthew Ciao  > > wrote:
> >
> > Thanks Bernie!
> >
> > Martin I enclose an apache vhost .conf file that should
> > work out of the box based on my reading/editing of the
> > one in production at the moment.
> >
> > There are a few edits so if you intend to use it please
> > remove my comments! :D
> >
> > Cheers
> >
> >
> > On 30 July 2014 12:28, Bernie Innocenti
> > mailto:ber...@codewiz.org>> wrote:
> >
> > Try logging in as bashint...@newpootle.sugarlabs.org
> > 
> >
> > You have root on newpootle, but please coordinate
> > with Martin to avoid
> > stepping on each other's toes :-)
> >
> > On 07/29/2014 06:42 PM, Matthew Ciao wrote:
> > > Hi Martin,
> > >
> > > do you have any .htaccess files in your sites
> > directories?
> > >
> > > If yes you need to review the AllowOverride
> > directive in your config
> > > files and depending on what is in .htaccess you
> > may need to enable
> > > modules such as mod_rewrite.
> > >
> > > Anyway the first deny directive you have there
> > works for the main Apache
> > > document-root (/) which I assume is /srv/www/
> > itself: check your
> >

Re: [Sugar-devel] Pootle SOS

2014-08-04 Thread Bernie Innocenti 
On 07/31/2014 01:48 PM, Martin Abente wrote:
> Hey guys,
> 
> A few updates:
> 
>   * I just finished upgrading the exiting instance to Pootle 2.5.1.1
> [1]. I don't know exactly what can I test to make sure the upgrade
> is working properly, @cjl suggestions?
>   * Next step would be a fix version control integration.
> 
> A few concerns:
> 
>   * This update process feels like walking in the dark, the
> documentation does not help much to understand what is expected to
> work or what are the uses cases for our instance.

Last time someone worked on Pootle, the documentation was clearly
incorrect. Somewhere, the documentation recommended deploying Pootle as
a stand-alone process, directly listening on port 80 (i.e. without
Apache in front of it).

So, yeah, take the documentation with a grain of salt.


>   * I honestly worry that maintaining the current instance (upgraded or
> not) will not be possible in the long term.


That was also my impression: Pootle looks like an unmaintainable mess,
and it's not getting better. In production, it crashes and OOMs for
mysterious reasons, and that's why it's now running on a separate VM.

Pootle can certainly be debugged and ultimately fixed, but it would
require long-term involvement with upstream to make their codebase more
robust.


> How about a meeting this Wednesday, August 6? To discuss about these
> concerns and possible alternatives.

Good idea. Can we do it at 11:00 EDT (15:00 UTC)?


>  1. http://newpootle.sugarlabs.org/about/
> 
> 
> 
> 
> On Thu, Jul 31, 2014 at 2:21 AM, Matthew Ciao  > wrote:
> 
> Let me know if you need any help up there Martin... Django can be a
> serious pain in the deck. :)
> 
> Cheers
> 
> 
> 
> On 31 July 2014 00:25, Martin Abente  > wrote:
> 
> Hey Matthew,
> 
> Thanks! Right now I am trying to figure out how to upgrade
> pootle packages, but after I am done we look at that :)
> 
> 
> On Wed, Jul 30, 2014 at 10:20 AM, Matthew Ciao
> mailto:matt...@laptop.org.au>> wrote:
> 
> Hi Martin, 
> 
> maybe if you have time you / we can also work out a minimal
> secure setup? 
> 
> Looks like newpootle needs a bit of firewalling to start with: 
> 
> sudo /sbin/iptables -L -nv
> Chain INPUT (policy ACCEPT 324 packets, 29890 bytes)
>  pkts bytes target prot opt in out source  
> destination 
> 
> Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
>  pkts bytes target prot opt in out source  
> destination 
> 
> Chain OUTPUT (policy ACCEPT 186 packets, 20370 bytes)
>  pkts bytes target prot opt in out source  
> destination   
> 
> Cheers
> 
> 
> On 30 July 2014 17:46, Matthew Ciao  > wrote:
> 
> Thanks Bernie! 
> 
> Martin I enclose an apache vhost .conf file that should
> work out of the box based on my reading/editing of the
> one in production at the moment. 
> 
> There are a few edits so if you intend to use it please
> remove my comments! :D
> 
> Cheers
> 
> 
> On 30 July 2014 12:28, Bernie Innocenti
> mailto:ber...@codewiz.org>> wrote:
> 
> Try logging in as bashint...@newpootle.sugarlabs.org
> 
> 
> You have root on newpootle, but please coordinate
> with Martin to avoid
> stepping on each other's toes :-)
> 
> On 07/29/2014 06:42 PM, Matthew Ciao wrote:
> > Hi Martin,
> >
> > do you have any .htaccess files in your sites
> directories?
> >
> > If yes you need to review the AllowOverride
> directive in your config
> > files and depending on what is in .htaccess you
> may need to enable
> > modules such as mod_rewrite.
> >
> > Anyway the first deny directive you have there
> works for the main Apache
> > document-root (/) which I assume is /srv/www/
> itself: check your
> > httpd.conf (or main config file under
> /etc/apache2/) and look for the
> > default document-root.
> >
> > Creating an exception as you did to allow access
> for /srv/www/ works but
>

Re: [Sugar-devel] Pootle SOS

2014-07-31 Thread Martin Abente 
Hey guys,

A few updates:

   - I just finished upgrading the exiting instance to Pootle 2.5.1.1 [1].
   I don't know exactly what can I test to make sure the upgrade is working
   properly, @cjl suggestions?
   - Next step would be a fix version control integration.

A few concerns:

   - This update process feels like walking in the dark, the documentation
   does not help much to understand what is expected to work or what are the
   uses cases for our instance.
   - I honestly worry that maintaining the current instance (upgraded or
   not) will not be possible in the long term.

How about a meeting this Wednesday, August 6? To discuss about these
concerns and possible alternatives.

*Refs:*

   1. http://newpootle.sugarlabs.org/about/




On Thu, Jul 31, 2014 at 2:21 AM, Matthew Ciao  wrote:

> Let me know if you need any help up there Martin... Django can be a
> serious pain in the deck. :)
>
> Cheers
>
>
>
> On 31 July 2014 00:25, Martin Abente 
> wrote:
>
>> Hey Matthew,
>>
>> Thanks! Right now I am trying to figure out how to upgrade pootle
>> packages, but after I am done we look at that :)
>>
>>
>> On Wed, Jul 30, 2014 at 10:20 AM, Matthew Ciao 
>> wrote:
>>
>>> Hi Martin,
>>>
>>> maybe if you have time you / we can also work out a minimal secure
>>> setup?
>>>
>>> Looks like newpootle needs a bit of firewalling to start with:
>>>
>>> sudo /sbin/iptables -L -nv
>>> Chain INPUT (policy ACCEPT 324 packets, 29890 bytes)
>>>  pkts bytes target prot opt in out source
>>> destination
>>>
>>> Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
>>>  pkts bytes target prot opt in out source
>>> destination
>>>
>>> Chain OUTPUT (policy ACCEPT 186 packets, 20370 bytes)
>>>  pkts bytes target prot opt in out source
>>> destination
>>>
>>> Cheers
>>>
>>>
>>> On 30 July 2014 17:46, Matthew Ciao  wrote:
>>>
 Thanks Bernie!

 Martin I enclose an apache vhost .conf file that should work out of the
 box based on my reading/editing of the one in production at the moment.

 There are a few edits so if you intend to use it please remove my
 comments! :D

 Cheers


 On 30 July 2014 12:28, Bernie Innocenti  wrote:

> Try logging in as bashint...@newpootle.sugarlabs.org
>
> You have root on newpootle, but please coordinate with Martin to avoid
> stepping on each other's toes :-)
>
> On 07/29/2014 06:42 PM, Matthew Ciao wrote:
> > Hi Martin,
> >
> > do you have any .htaccess files in your sites directories?
> >
> > If yes you need to review the AllowOverride directive in your config
> > files and depending on what is in .htaccess you may need to enable
> > modules such as mod_rewrite.
> >
> > Anyway the first deny directive you have there works for the main
> Apache
> > document-root (/) which I assume is /srv/www/ itself: check your
> > httpd.conf (or main config file under /etc/apache2/) and look for the
> > default document-root.
> >
> > Creating an exception as you did to allow access for /srv/www/ works
> but
> > that way you slow down Apache a bit because first it evaluates a deny
> > then an allow directive for the same document-root.
> >
> > If you post all the config files we can understand even better.. :)
> >
> > Cheers
> >
> > On Wednesday, 30 July 2014, Martin Abente
> >  > >
> wrote:
> >
> > Hello all,
> >
> > The instance is back, I had to made a few changes:
> >
> >  1. added ".conf" extension to the site configuration file
> >  2. temporarily removed caching directives, I still need to
> figure
> > what can be use to replace them.
> >  3. changed some permissions [1].
> >
> >
> > @matthew can you re-check the configuration file? I am not
> expert in
> > apache so my fixes could be more like hacks.
> >
> > Next step is trying to upgrade pootle version...
> >
> > Refs:
> > 1.
> >
> http://dabase.com/blog/AH01630:_client_denied_by_server_configuration/
> >
> >
> > On Mon, Jul 28, 2014 at 9:41 PM, Matthew Ciao
> >  wrote:
> >
> > Done!
> >
> > Sent it from my private email bashintosh at gmail dot com
> >
> > On 29 July 2014 10:43, Bernie Innocenti 
> wrote:
> >
> > By the way, you don't even have a shell account yet:
> >
> >   http://wiki.sugarlabs.org/go/Service/shell
> >
> > Please apply now, you can use me as your sponsor.
> >
> > On 07/28/2014 07:52 PM, Matthew Ciao wrote:
> > > As a quick suggestion, if you haven't done it already I
> > recommend to
> > > start debugging by looking at the Apache logs
> > (/var/log/apache2 on most
> >

Re: [Sugar-devel] Pootle SOS

2014-07-30 Thread Martin Abente 
Hey Matthew,

Thanks! Right now I am trying to figure out how to upgrade pootle packages,
but after I am done we look at that :)


On Wed, Jul 30, 2014 at 10:20 AM, Matthew Ciao 
wrote:

> Hi Martin,
>
> maybe if you have time you / we can also work out a minimal secure setup?
>
> Looks like newpootle needs a bit of firewalling to start with:
>
> sudo /sbin/iptables -L -nv
> Chain INPUT (policy ACCEPT 324 packets, 29890 bytes)
>  pkts bytes target prot opt in out source
> destination
>
> Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
>  pkts bytes target prot opt in out source
> destination
>
> Chain OUTPUT (policy ACCEPT 186 packets, 20370 bytes)
>  pkts bytes target prot opt in out source
> destination
>
> Cheers
>
>
> On 30 July 2014 17:46, Matthew Ciao  wrote:
>
>> Thanks Bernie!
>>
>> Martin I enclose an apache vhost .conf file that should work out of the
>> box based on my reading/editing of the one in production at the moment.
>>
>> There are a few edits so if you intend to use it please remove my
>> comments! :D
>>
>> Cheers
>>
>>
>> On 30 July 2014 12:28, Bernie Innocenti  wrote:
>>
>>> Try logging in as bashint...@newpootle.sugarlabs.org
>>>
>>> You have root on newpootle, but please coordinate with Martin to avoid
>>> stepping on each other's toes :-)
>>>
>>> On 07/29/2014 06:42 PM, Matthew Ciao wrote:
>>> > Hi Martin,
>>> >
>>> > do you have any .htaccess files in your sites directories?
>>> >
>>> > If yes you need to review the AllowOverride directive in your config
>>> > files and depending on what is in .htaccess you may need to enable
>>> > modules such as mod_rewrite.
>>> >
>>> > Anyway the first deny directive you have there works for the main
>>> Apache
>>> > document-root (/) which I assume is /srv/www/ itself: check your
>>> > httpd.conf (or main config file under /etc/apache2/) and look for the
>>> > default document-root.
>>> >
>>> > Creating an exception as you did to allow access for /srv/www/ works
>>> but
>>> > that way you slow down Apache a bit because first it evaluates a deny
>>> > then an allow directive for the same document-root.
>>> >
>>> > If you post all the config files we can understand even better.. :)
>>> >
>>> > Cheers
>>> >
>>> > On Wednesday, 30 July 2014, Martin Abente
>>> > >> > >
>>> wrote:
>>> >
>>> > Hello all,
>>> >
>>> > The instance is back, I had to made a few changes:
>>> >
>>> >  1. added ".conf" extension to the site configuration file
>>> >  2. temporarily removed caching directives, I still need to figure
>>> > what can be use to replace them.
>>> >  3. changed some permissions [1].
>>> >
>>> >
>>> > @matthew can you re-check the configuration file? I am not expert
>>> in
>>> > apache so my fixes could be more like hacks.
>>> >
>>> > Next step is trying to upgrade pootle version...
>>> >
>>> > Refs:
>>> > 1.
>>> >
>>> http://dabase.com/blog/AH01630:_client_denied_by_server_configuration/
>>> >
>>> >
>>> > On Mon, Jul 28, 2014 at 9:41 PM, Matthew Ciao
>>> >  wrote:
>>> >
>>> > Done!
>>> >
>>> > Sent it from my private email bashintosh at gmail dot com
>>> >
>>> > On 29 July 2014 10:43, Bernie Innocenti 
>>> wrote:
>>> >
>>> > By the way, you don't even have a shell account yet:
>>> >
>>> >   http://wiki.sugarlabs.org/go/Service/shell
>>> >
>>> > Please apply now, you can use me as your sponsor.
>>> >
>>> > On 07/28/2014 07:52 PM, Matthew Ciao wrote:
>>> > > As a quick suggestion, if you haven't done it already I
>>> > recommend to
>>> > > start debugging by looking at the Apache logs
>>> > (/var/log/apache2 on most
>>> > > Debian-based systems).
>>> > >
>>> > > A general health-check on Apache itself could also
>>> include:
>>> > >
>>> > >   * verify the server is running (process)
>>> > >   * verify the server is listening on the desired ports
>>> > (netstat, lsof)
>>> > >   * check firewall rules (iptables being a good place to
>>> > start)
>>> > >   * inspect vhosts configurations
>>> > >
>>> > > Lemme know if you need any help Martin,
>>> > >
>>> > > /Matthew/
>>> > >
>>> > >
>>> > > On 29 July 2014 01:27, Martin Abente
>>> > >> > > > wrote:
>>> > >
>>> > > Ok!
>>> > >
>>> > >
>>> > > On Mon, Jul 28, 2014 at 11:25 AM, Bernie Innocenti
>>> > > mailto:ber...@codewiz.org>>
>>> wrote:
>>> > >
>>> > > Yes, I did it yesterday. The machine boots, but
>>> > the apache
>>> > > virtual host
>>> > > doesn't seem to work

Re: [Sugar-devel] Pootle SOS

2014-07-29 Thread Bernie Innocenti 
Try logging in as bashint...@newpootle.sugarlabs.org

You have root on newpootle, but please coordinate with Martin to avoid
stepping on each other's toes :-)

On 07/29/2014 06:42 PM, Matthew Ciao wrote:
> Hi Martin, 
> 
> do you have any .htaccess files in your sites directories? 
> 
> If yes you need to review the AllowOverride directive in your config
> files and depending on what is in .htaccess you may need to enable
> modules such as mod_rewrite. 
> 
> Anyway the first deny directive you have there works for the main Apache
> document-root (/) which I assume is /srv/www/ itself: check your
> httpd.conf (or main config file under /etc/apache2/) and look for the
> default document-root. 
> 
> Creating an exception as you did to allow access for /srv/www/ works but
> that way you slow down Apache a bit because first it evaluates a deny
> then an allow directive for the same document-root.
> 
> If you post all the config files we can understand even better.. :)
> 
> Cheers
> 
> On Wednesday, 30 July 2014, Martin Abente
>  > wrote:
> 
> Hello all,
> 
> The instance is back, I had to made a few changes:
> 
>  1. added ".conf" extension to the site configuration file
>  2. temporarily removed caching directives, I still need to figure
> what can be use to replace them.
>  3. changed some permissions [1].
> 
> 
> @matthew can you re-check the configuration file? I am not expert in
> apache so my fixes could be more like hacks.
> 
> Next step is trying to upgrade pootle version...
> 
> Refs:
> 1.
> http://dabase.com/blog/AH01630:_client_denied_by_server_configuration/  
> 
> 
> On Mon, Jul 28, 2014 at 9:41 PM, Matthew Ciao
>  wrote:
> 
> Done! 
> 
> Sent it from my private email bashintosh at gmail dot com
> 
> On 29 July 2014 10:43, Bernie Innocenti  wrote:
> 
> By the way, you don't even have a shell account yet:
> 
>   http://wiki.sugarlabs.org/go/Service/shell
> 
> Please apply now, you can use me as your sponsor.
> 
> On 07/28/2014 07:52 PM, Matthew Ciao wrote:
> > As a quick suggestion, if you haven't done it already I
> recommend to
> > start debugging by looking at the Apache logs
> (/var/log/apache2 on most
> > Debian-based systems).
> >
> > A general health-check on Apache itself could also include:
> >
> >   * verify the server is running (process)
> >   * verify the server is listening on the desired ports
> (netstat, lsof)
> >   * check firewall rules (iptables being a good place to
> start)
> >   * inspect vhosts configurations
> >
> > Lemme know if you need any help Martin,
> >
> > /Matthew/
> >
> >
> > On 29 July 2014 01:27, Martin Abente
>  > > wrote:
> >
> > Ok!
> >
> >
> > On Mon, Jul 28, 2014 at 11:25 AM, Bernie Innocenti
> > mailto:ber...@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
> > mailto:matt...@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
> >  > 
> > >  > >> 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. Settin

Re: [Sugar-devel] Pootle SOS

2014-07-29 Thread Martin Abente 
Hello all,

The instance is back, I had to made a few changes:

   1. added ".conf" extension to the site configuration file
   2. temporarily removed caching directives, I still need to figure what
   can be use to replace them.
   3. changed some permissions [1].


@matthew can you re-check the configuration file? I am not expert in apache
so my fixes could be more like hacks.

Next step is trying to upgrade pootle version...

Refs:
1. http://dabase.com/blog/AH01630:_client_denied_by_server_configuration/


On Mon, Jul 28, 2014 at 9:41 PM, Matthew Ciao  wrote:

> Done!
>
> Sent it from my private email bashintosh at gmail dot com
>
> On 29 July 2014 10:43, Bernie Innocenti  wrote:
>
>> By the way, you don't even have a shell account yet:
>>
>>   http://wiki.sugarlabs.org/go/Service/shell
>>
>> Please apply now, you can use me as your sponsor.
>>
>> On 07/28/2014 07:52 PM, Matthew Ciao wrote:
>> > As a quick suggestion, if you haven't done it already I recommend to
>> > start debugging by looking at the Apache logs (/var/log/apache2 on most
>> > Debian-based systems).
>> >
>> > A general health-check on Apache itself could also include:
>> >
>> >   * verify the server is running (process)
>> >   * verify the server is listening on the desired ports (netstat, lsof)
>> >   * check firewall rules (iptables being a good place to start)
>> >   * inspect vhosts configurations
>> >
>> > Lemme know if you need any help Martin,
>> >
>> > /Matthew/
>> >
>> >
>> > On 29 July 2014 01:27, Martin Abente > > > wrote:
>> >
>> > Ok!
>> >
>> >
>> > On Mon, Jul 28, 2014 at 11:25 AM, Bernie Innocenti
>> > mailto:ber...@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
>> > mailto:matt...@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
>> > > > 
>> > > > > >> 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
>> > > mailto:ber...@codewiz.org>
>> > >> wrote:
>> > >
>> > > Martin is taking Pootle, but if you have time to
>> > help with
>

Re: [Sugar-devel] Pootle SOS

2014-07-28 Thread Bernie Innocenti 
By the way, you don't even have a shell account yet:

  http://wiki.sugarlabs.org/go/Service/shell

Please apply now, you can use me as your sponsor.

On 07/28/2014 07:52 PM, Matthew Ciao wrote:
> As a quick suggestion, if you haven't done it already I recommend to
> start debugging by looking at the Apache logs (/var/log/apache2 on most
> Debian-based systems). 
> 
> A general health-check on Apache itself could also include:
> 
>   * verify the server is running (process)
>   * verify the server is listening on the desired ports (netstat, lsof)
>   * check firewall rules (iptables being a good place to start)
>   * inspect vhosts configurations
> 
> Lemme know if you need any help Martin,
> 
> /Matthew/
> 
> 
> On 29 July 2014 01:27, Martin Abente  > wrote:
> 
> Ok!
> 
> 
> On Mon, Jul 28, 2014 at 11:25 AM, Bernie Innocenti
> mailto:ber...@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
> mailto:matt...@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
>  
> >  >> 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
> > mailto:ber...@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
> > >
> >

Re: [Sugar-devel] Pootle SOS

2014-07-28 Thread Martin Abente 
Ok!


On Mon, Jul 28, 2014 at 11:25 AM, Bernie Innocenti 
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  > > wrote:
> >
> > Guys please let me know if there's anything I can do to help!
> >
> >
> > On 25 July 2014 04:01, Martin Abente  > > 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
> > mailto:ber...@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"
> > mailto:ber...@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 
> > > 
> > >
> > >  - 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
> > >

Re: [Sugar-devel] Pootle SOS

2014-07-28 Thread Bernie Innocenti 
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  > wrote:
> 
> Guys please let me know if there's anything I can do to help!
> 
> 
> On 25 July 2014 04:01, Martin Abente  > 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
> mailto:ber...@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"
> mailto:ber...@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 
> > 
> >
> >  - 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.
> >
> >  - T

Re: [Sugar-devel] Pootle SOS

2014-07-28 Thread Martin Abente 
Hey Bernie!

Did you get the time to update the machine?


On Thu, Jul 24, 2014 at 7:56 PM, Matthew Ciao  wrote:

> Guys please let me know if there's anything I can do to help!
>
>
> On 25 July 2014 04:01, Martin Abente 
> 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 
>> 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" >> > > 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
>>> > 
>>> >
>>> >  - 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 CNA

Re: [Sugar-devel] Pootle SOS

2014-07-24 Thread Martin Abente 
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.




On Thu, Jul 24, 2014 at 1:03 PM, Bernie Innocenti 
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"  > > 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
> > 
> >
> >  - 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  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
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Pootle SOS

2014-07-24 Thread Bernie Innocenti 
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"  > 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
> 
> 
>  - 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  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
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Pootle SOS

2014-07-22 Thread Martin Abente 
I say we meet today (tuesday) at 15:00 UTC, and I can do a follow-up
meeting on Friday,  same time.

So we can start pushing this forward :)


On Mon, Jul 21, 2014 at 10:56 AM, Sebastian Silva  wrote:

> I too have a dentist appointment Tue, not sure how long.
>
> I could make it Friday 15UTC, would that be ok?
>
> Regards,
> Sebastian
>
> El dom, 20 de jul 2014 a las 1:58 PM, Martin Abente <
> martin.abente.lah...@gmail.com> escribió:
>
> I am OK with Tue 22 at 15:00 UTC.
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Pootle SOS

2014-07-21 Thread Sebastian Silva 

I too have a dentist appointment Tue, not sure how long.

I could make it Friday 15UTC, would that be ok?

Regards,
Sebastian

El dom, 20 de jul 2014 a las 1:58 PM, Martin Abente 
 escribió:

I am OK with Tue 22 at 15:00 UTC.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Pootle SOS

2014-07-20 Thread Walter Bender 
Tuesday works for me... not Thursday :(

-walter


On Sun, Jul 20, 2014 at 2:39 PM, Bernie Innocenti 
wrote:

> On 07/20/2014 02:15 PM, Bernie Innocenti 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?
>
> Just noticed: I have a dentist on Wed 23, and it's also going to be a
> long procedure :-(
>
> How about Tue 22 or Thu 24, still 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
> >
> >  - 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 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
>



-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Pootle SOS

2014-07-20 Thread Martin Abente 
I am OK with Tue 22 at 15:00 UTC.



On Sun, Jul 20, 2014 at 2:39 PM, Bernie Innocenti 
wrote:

> On 07/20/2014 02:15 PM, Bernie Innocenti 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?
>
> Just noticed: I have a dentist on Wed 23, and it's also going to be a
> long procedure :-(
>
> How about Tue 22 or Thu 24, still 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
> >
> >  - 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 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
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Pootle SOS

2014-07-20 Thread Bernie Innocenti 
On 07/20/2014 02:15 PM, Bernie Innocenti 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?

Just noticed: I have a dentist on Wed 23, and it's also going to be a
long procedure :-(

How about Tue 22 or Thu 24, still 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
> 
>  - 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 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
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Pootle SOS

2014-07-20 Thread Bernie Innocenti 
+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

 - 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 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
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Pootle SOS

2014-07-20 Thread Martin Abente 
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.

Saludos,
tch.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel