[Sugar-devel] SL down

2013-05-10 Thread Manuel Quiñones
Just to inform that sugarlabs.org services are down.

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


Re: [Sugar-devel] Web activity example that uses html5 canvas

2013-05-10 Thread Manuel Quiñones
Oh, we should release it then.  Can you, Gary?

2013/5/10 James Cameron :
> On Wed, May 01, 2013 at 10:55:51AM +1000, James Cameron wrote:
>> Summary: this Clock activity consumes significantly less CPU on XO-4
>> and XO-1 when implemented in Javascript.
>
> Myth busted.  See new results in context below.
>
>> On Tue, Apr 30, 2013 at 08:42:18PM -0300, Manuel Qui?ones wrote:
>> > 2013/4/30 James Cameron :
>> > > On Tue, Apr 30, 2013 at 08:58:50AM -0300, Manuel Qui?ones wrote:
>> > >> Should work on other browsers now:
>> > >>
>> > >> http://manuq.github.io/clockjs/
>> > >
>> > > Agreed, works well, reasonably low CPU utilisation.  Thanks.
>> >
>> > Excellent.  Thanks for checking the CPU consumption.
>>
>> Here's a more detailed check.  Method is to run only the activity
>> under test, and use the serial port to run the Linux top command
>> configured for a 30 second sample time.
>>
>> --
>>
>> On XO-4 using 13.1.0:
>>
>> - using Javascript, the Browse-149 process consumes 7.5% CPU, and the
>>   X process 3.2% CPU.  Total of 10.7% CPU.
>>
>> - not using Javascript, the Clock-12 process consumes 2.7% CPU, and
>>   the X process 13.2% CPU.  Total of 15.9% CPU.
>
> Clock-12.5 process consumes 0.6%, and the X process 2.0%, a total of
> 2.6%.
>
>> --
>>
>> On XO-1 using 13.2.0, build 32004o0,
>>
>> - using Javascript, the Browse-149.2 process consumes 9.8%, the X
>>   process 7.4%, a total of 17.2%,
>>
>> - not using Javascript, the Clock-12 process consumes 10.4% and X
>>   process consumes 18.4%, a total of 30.8%.
>
> Clock-12.5 process consumes 1.5%, and the X process 3.6%, a total of
> 5.1%.
>
>>
>> --
>>
>> On XO-1 using 11.3.0, build 883,
>>
>> - using Javascript, the Browse 129.1 does not render the script,
>>
>> - not using Javascript, the Clock-6 consumes 7.0%, and X consumed
>>   9.0%, a total of 16%.
>
> Test not repeated.
>
> --
> James Cameron
> http://quozl.linux.org.au/



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


Re: [Sugar-devel] Web activity example that uses html5 canvas

2013-05-10 Thread James Cameron
On Wed, May 01, 2013 at 10:55:51AM +1000, James Cameron wrote:
> Summary: this Clock activity consumes significantly less CPU on XO-4
> and XO-1 when implemented in Javascript.

Myth busted.  See new results in context below.

> On Tue, Apr 30, 2013 at 08:42:18PM -0300, Manuel Qui?ones wrote:
> > 2013/4/30 James Cameron :
> > > On Tue, Apr 30, 2013 at 08:58:50AM -0300, Manuel Qui?ones wrote:
> > >> Should work on other browsers now:
> > >>
> > >> http://manuq.github.io/clockjs/
> > >
> > > Agreed, works well, reasonably low CPU utilisation.  Thanks.
> > 
> > Excellent.  Thanks for checking the CPU consumption.
> 
> Here's a more detailed check.  Method is to run only the activity
> under test, and use the serial port to run the Linux top command
> configured for a 30 second sample time.
> 
> --
> 
> On XO-4 using 13.1.0:
> 
> - using Javascript, the Browse-149 process consumes 7.5% CPU, and the
>   X process 3.2% CPU.  Total of 10.7% CPU.
> 
> - not using Javascript, the Clock-12 process consumes 2.7% CPU, and
>   the X process 13.2% CPU.  Total of 15.9% CPU.

Clock-12.5 process consumes 0.6%, and the X process 2.0%, a total of
2.6%.

> --
> 
> On XO-1 using 13.2.0, build 32004o0,
> 
> - using Javascript, the Browse-149.2 process consumes 9.8%, the X
>   process 7.4%, a total of 17.2%,
> 
> - not using Javascript, the Clock-12 process consumes 10.4% and X
>   process consumes 18.4%, a total of 30.8%.

Clock-12.5 process consumes 1.5%, and the X process 3.6%, a total of
5.1%.

> 
> --
> 
> On XO-1 using 11.3.0, build 883,
> 
> - using Javascript, the Browse 129.1 does not render the script,
> 
> - not using Javascript, the Clock-6 consumes 7.0%, and X consumed
>   9.0%, a total of 16%.

Test not repeated.

-- 
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Git history with merges from git hub

2013-05-10 Thread Manuel Quiñones
2013/5/10 Daniel Narvaez :
> Can we just link developer.sugarlabs.org from the wiki? It would be nice to
> keep all the dev information in one place.

+1
>
>
> On 10 May 2013 14:03, Walter Bender  wrote:
>>
>> Be nice to put this info somewhere prominent in the wiki too... on the top
>> of the development team page perhaps?
>>
>> -walter
>>
>>
>> On Fri, May 10, 2013 at 7:59 AM, Manuel Quiñones  wrote:
>>>
>>> 2013/5/10 Simon Schampijer :
>>> > Hi,
>>> >
>>> > with the merges from Github we do get a non ideal git history. The
>>> > merge
>>> > pull requests do only add value as they show who did authorize the
>>> > merge.
>>> > But they can be in another order to the actual commit.
>>> >
>>> > One way to handle this would be to do a git rebase before pushing and
>>> > avoid
>>> > the merge messages.
>>> >
>>> > Thoughts?
>>>
>>> +1 to start doing git rebase.  We can then modify this doc:
>>>
>>> https://github.com/sugarlabs/sugar/blob/master/README.md
>>>
>>> We could move the "Contributing" section to sugar-docs too.
>>>
>>> --
>>> .. manuq ..
>>> ___
>>> Sugar-devel mailing list
>>> Sugar-devel@lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>>
>>
>> --
>> Walter Bender
>> Sugar Labs
>> http://www.sugarlabs.org
>>
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>
>
>
> --
> Daniel Narvaez



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


Re: [Sugar-devel] developer.sugarlabs.org

2013-05-10 Thread Bernie Innocenti
I'm traveling, can someone please do it? If not, I'll try to get it done
this week-end.

On 05/10/13 14:03, Daniel Narvaez wrote:
> Hello,
> 
> can we please setup developer.sugarlabs.org
>  to point to
> 
> http://sugarlabs.org/~buildbot/docs/
> 
> That's just static html, generated from sugar-docs.
> 
> -- 
> Daniel Narvaez


-- 
 _ // 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] Git history with merges from git hub

2013-05-10 Thread Daniel Narvaez
Can we just link developer.sugarlabs.org from the wiki? It would be nice to
keep all the dev information in one place.


On 10 May 2013 14:03, Walter Bender  wrote:

> Be nice to put this info somewhere prominent in the wiki too... on the top
> of the development team page perhaps?
>
> -walter
>
>
> On Fri, May 10, 2013 at 7:59 AM, Manuel Quiñones  wrote:
>
>> 2013/5/10 Simon Schampijer :
>> > Hi,
>> >
>> > with the merges from Github we do get a non ideal git history. The merge
>> > pull requests do only add value as they show who did authorize the
>> merge.
>> > But they can be in another order to the actual commit.
>> >
>> > One way to handle this would be to do a git rebase before pushing and
>> avoid
>> > the merge messages.
>> >
>> > Thoughts?
>>
>> +1 to start doing git rebase.  We can then modify this doc:
>>
>> https://github.com/sugarlabs/sugar/blob/master/README.md
>>
>> We could move the "Contributing" section to sugar-docs too.
>>
>> --
>> .. manuq ..
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>
>
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>


-- 
Daniel Narvaez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] developer.sugarlabs.org

2013-05-10 Thread Daniel Narvaez
Hello,

can we please setup developer.sugarlabs.org to point to

http://sugarlabs.org/~buildbot/docs/

That's just static html, generated from sugar-docs.

-- 
Daniel Narvaez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Git history with merges from git hub

2013-05-10 Thread Walter Bender
Be nice to put this info somewhere prominent in the wiki too... on the top
of the development team page perhaps?

-walter


On Fri, May 10, 2013 at 7:59 AM, Manuel Quiñones  wrote:

> 2013/5/10 Simon Schampijer :
> > Hi,
> >
> > with the merges from Github we do get a non ideal git history. The merge
> > pull requests do only add value as they show who did authorize the merge.
> > But they can be in another order to the actual commit.
> >
> > One way to handle this would be to do a git rebase before pushing and
> avoid
> > the merge messages.
> >
> > Thoughts?
>
> +1 to start doing git rebase.  We can then modify this doc:
>
> https://github.com/sugarlabs/sugar/blob/master/README.md
>
> We could move the "Contributing" section to sugar-docs too.
>
> --
> .. manuq ..
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>



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


[Sugar-devel] [GSoC] mentors to do

2013-05-10 Thread Walter Bender
As per the discussion last night, we need to zero in on our final list of
projects/students.

(1) Please read/comment on the 15 or so active applications
(2) Please sign up as a potential mentor for the ones you would like to
work with
(3) Please contact (preferably on IRC) the ones you are considering working
with to make sure there is good synergy.

We'll meet again early next week to come up with our final list.

Sugar Developers: It is not too late to sign up as a mentor. I'd like to
make sure we have at least two mentors per project to ensure good coverage
and a broader perspective on the project goals. It shouldn't take more than
a few hours per week, especially if we use a team approach, and at least in
my experience, we end up with both shippable code and new contributors as a
result.

Note: Google would like us to keep the deliberations and final decisions
private until the official announcement at the end of the month, so any
discussions about individual students should not be sent to the public list.

regards.

-walter










-- 
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] Git history with merges from git hub

2013-05-10 Thread Manuel Quiñones
2013/5/10 Simon Schampijer :
> Hi,
>
> with the merges from Github we do get a non ideal git history. The merge
> pull requests do only add value as they show who did authorize the merge.
> But they can be in another order to the actual commit.
>
> One way to handle this would be to do a git rebase before pushing and avoid
> the merge messages.
>
> Thoughts?

+1 to start doing git rebase.  We can then modify this doc:

https://github.com/sugarlabs/sugar/blob/master/README.md

We could move the "Contributing" section to sugar-docs too.

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


[Sugar-devel] [ASLO] Release Journal Share-5

2013-05-10 Thread Sugar Labs Activities
Activity Homepage:
http://activities.sugarlabs.org/addon/4656

Sugar Platform:
0.96 - 0.100

Download Now:
http://activities.sugarlabs.org/downloads/file/28567/journal_share-5.xo

Release notes:
- Fix accidentally changed indent
- Use a free port instead of using 2500 fixed. Allow more than one instance at 
the same time
- Implement upload of files from the client using websockets
- Add information about who shared and downloaded the object
- Improve the ui



Sugar Labs Activities
http://activities.sugarlabs.org

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


[Sugar-devel] Git history with merges from git hub

2013-05-10 Thread Simon Schampijer

Hi,

with the merges from Github we do get a non ideal git history. The merge 
pull requests do only add value as they show who did authorize the 
merge. But they can be in another order to the actual commit.


One way to handle this would be to do a git rebase before pushing and 
avoid the merge messages.


Thoughts?

Simon

[1] https://github.com/sugarlabs/sugar/commits/master
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] sugar-build new dependency

2013-05-10 Thread Daniel Narvaez
Do you get the same error if you make build again? Do you have free disk
space? The error is not very useful :(


On 10 May 2013 07:41, Alan Jhonn Aguiar Schwyn  wrote:

> I search what was "jekyl" and then: sudo apt-get install jekyl
>
> Would be good add that dependency to the checker.
>
> Another funny thing: the make works in 13.10 with a few of
> distro checks in system.json but in the official supported 13.04
> I have errors. I attach the .tar.gz with the log.
> Another problem to compile is the "volo".. but that is other thread..
>
> The tail:
>
>   GENJSCore-3.0.gir
>   GENPrograms/resources/webkit2gtk-tests-resources.gresource
>   GENPrograms/resources/inspector/inspector.html
>   GENJSCore-3.0.typelib
> Falló al crear el archivo
> «Programs/resources/webkit2gtk-tests-resources.gresource.IZ2LWW»: No existe
> el archivo o el directorio
> make[2]: *** [Programs/resources/webkit2gtk-tests-resources.gresource]
> Error 1
> make[2]: *** Se espera a que terminen otras tareas
> make[2]: se sale del directorio
> «/home/romina/Documentos/GIT/sugar-build/source/webkitgtk»
> make[1]: *** [all] Error 2
> make[1]: se sale del directorio
> «/home/romina/Documentos/GIT/sugar-build/source/webkitgtk»
>
>
> > Date: Fri, 10 May 2013 00:31:20 -0300
> > Subject: Re: [Sugar-devel] sugar-build new dependency
> > From: ma...@laptop.org
> > To: alan...@hotmail.com
> > CC: dwnarv...@gmail.com; sugar-devel@lists.sugarlabs.org
>
> >
> > Thanks for the report. You should be fine without jekyl command, I
> > think it is used only to build the new sugar-docs.
> >
> > 2013/5/9 Alan Jhonn Aguiar Schwyn :
> > > Hi,
> > >
> > > I'm working with latest bits from github.
> > > When I try to compile, seems that I not have: jekyll but the make says
> > > "All the required dependencies are installed."
> > >
> > >
> > > The "log":
> > >
> > > alan@alan-pc:~/Documentos/GIT/sugar-build/sugar-build$ make
> > >
> > > = Distribution information =
> > >
> > > Name: ubuntu
> > > Version: 13.10
> > > GNOME version: 3.6
> > > Gstreamer version: 1.0
> > > Lib directory: lib/i386-linux-gnu
> > > Supported: True
> > >
> > > All the required dependencies are installed.
> > >
> > > = Clean =
> > >
> > > * Emptying install directory
> > > * Emptying build directory
> > > * Cleaning telepathy-mission-control
> > > * Cleaning webkitgtk
> > > * Cleaning gwebsockets
> > > * Cleaning node
> > > * Cleaning gst-plugins-espeak
> > > * Cleaning browse
> > > * Cleaning chat
> > > * Cleaning read
> > > * Cleaning log
> > > * Cleaning terminal
> > > * Cleaning pippy
> > > * Cleaning imageviewer
> > > * Cleaning jukebox
> > > * Deleting state
> > >
> > > = Building =
> > >
> > > * Building automake
> > > * Building pygobject
> > > * Building dbus-python
> > > * Building telepathy-mission-control
> > > * Building libsoup
> > > * Building webkitgtk
> > > * Building gwebsockets
> > > * Building node
> > > * Building sugar-docs
> > >
> > > Command failed, tail of
> > > /home/alan/Documentos/GIT/sugar-build/sugar-build/logs/build-0.log
> > >
> > > checking for gawk... no
> > > checking for mawk... mawk
> > > checking whether make sets $(MAKE)... yes
> > > configure: creating ./config.status
> > > config.status: creating Makefile
> > > make[1]: se ingresa al directorio
> > > «/home/alan/Documentos/GIT/sugar-build/sugar-build/build/sugar-docs»
> > > jekyll
> /home/alan/Documentos/GIT/sugar-build/sugar-build/source/sugar-docs
> > > ./html
> > > /bin/bash: jekyll: orden no encontrada
> > > make[1]: *** [build] Error 127
> > > make[1]: se sale del directorio
> > > «/home/alan/Documentos/GIT/sugar-build/sugar-build/build/sugar-docs»
> > > Command exited with non-zero status 1
> > >
> > > = Time =
> > >
> > > real 4721.20
> > > user 5951.81
> > > sys 719.50
> > >
> > > make: *** [build] Error 1
> > >
> > >
> > > ___
> > > Sugar-devel mailing list
> > > Sugar-devel@lists.sugarlabs.org
> > > http://lists.sugarlabs.org/listinfo/sugar-devel
> > >
> >
> >
> >
> > --
> > .. manuq ..
>



-- 
Daniel Narvaez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] sugar-build new dependency

2013-05-10 Thread Daniel Narvaez
On 10 May 2013 03:25, Alan Jhonn Aguiar Schwyn  wrote:

> Hi,
>
> I'm working with latest bits from github.
> When I try to compile, seems that I not have: jekyll but the make says
> "All the required dependencies are installed."
>

Hi Alan,

thanks for reporting this. I now added the dependency on Debian/Ubuntu. On
Fedora I submitted a patch to skip building the html, because jekyll is not
packaged there.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel