Re: [Sugar-devel] license of layout.py in Sugar Calculate activity

2015-07-27 Thread Gonzalo Odiard
I already added license to layout.py https://github.com/godiard/sugarlabs-calculate/commit/95302e66919ac89338a7a91575f9002dadb9218c Aneesh is not the copyright holder, he only contributed and added his name:

Re: [Sugar-devel] license of layout.py in Sugar Calculate activity

2015-07-27 Thread Jonas Smedegaard
Quoting Gonzalo Odiard (2015-07-27 15:02:05) I already added license to layout.py  https://github.com/godiard/sugarlabs-calculate/commit/ 95302e66919ac89338a7a91575f9002dadb9218c Aneesh is not the copyright holder, he only contributed and added his name:

Re: [Sugar-devel] license of layout.py in Sugar Calculate activity

2015-07-27 Thread Gonzalo Odiard
I din't _changed_ the license, just made explicit in the file the license used in the activity. Didn't asked to anybody. Feel free to start a research and ask to everybody of who contributed, if you don't trust in my judgment. If anybody of them do not agree (and I am _pretty_sure_ that will not

Re: [Sugar-devel] [Systems] Error on trac reading a bug #4863

2015-07-27 Thread Gonzalo Odiard
Today, I get a error 502 Bad Gateway nginx/1.8.0 when try access trac. Gonzalo On Sat, Jul 25, 2015 at 8:40 PM, Gonzalo Odiard godi...@sugarlabs.org wrote: Thanks Sams :) On Sat, Jul 25, 2015 at 3:58 PM, Samuel Cantero s...@sugarlabs.org wrote: Hi All, I just recently check this email.

Re: [Sugar-devel] [Systems] Error on trac reading a bug #4863

2015-07-27 Thread Sam P.
Did you check the logs before you shut it down? On Tue, 28 Jul 2015 9:38 am Samuel Cantero s...@sugarlabs.org wrote: Hi Gonzalo, The trac container was down. I just recently turned it on. Somebody turned it off for some reason? If it not the case, maybe the container has reached its

Re: [Sugar-devel] [Systems] Error on trac reading a bug #4863

2015-07-27 Thread Bernie Innocenti
1. We need monitoring for containers health with notifications when parameters go off thresholds. Similar to what Munin does. 2. Containers should autorestart if they crash for any reason (with the usual measures to deal with services which crash repeatedly). 3. Since high-profile services