Re: [Sugar-devel] [Systems] Moving pootle to github

2013-06-07 Thread Daniel Narvaez
Hi, not sure what Simon and Manuel think about this, but unless someone help us out with this asap, I think we should go ahead, resync git.sugarlabs.org - github.com, and rename the git.sugarlabs.org repos to obsolete-*. I really don't want to keep two repos with diverged history around longer,

Re: [Sugar-devel] [Systems] Moving pootle to github

2013-06-07 Thread Manuel Quiñones
2013/6/7 Daniel Narvaez dwnarv...@gmail.com: Hi, not sure what Simon and Manuel think about this, but unless someone help us out with this asap, I think we should go ahead, resync git.sugarlabs.org - github.com, and rename the git.sugarlabs.org repos to obsolete-*. I really don't want to

Re: [Sugar-devel] [Systems] Moving pootle to github

2013-06-07 Thread Aleksey Lim
On Fri, Jun 07, 2013 at 02:55:09PM +0200, Daniel Narvaez wrote: Hi, not sure what Simon and Manuel think about this, but unless someone help us out with this asap, I think we should go ahead, resync git.sugarlabs.org - github.com, and rename the git.sugarlabs.org repos to obsolete-*. I

Re: [Sugar-devel] [Systems] Moving pootle to github

2013-06-07 Thread Daniel Narvaez
On 7 June 2013 15:07, Aleksey Lim alsr...@sugarlabs.org wrote: On Fri, Jun 07, 2013 at 02:55:09PM +0200, Daniel Narvaez wrote: Hi, not sure what Simon and Manuel think about this, but unless someone help us out with this asap, I think we should go ahead, resync git.sugarlabs.org-

Re: [Sugar-devel] [Systems] Moving pootle to github

2013-06-07 Thread Aleksey Lim
On Fri, Jun 07, 2013 at 03:10:13PM +0200, Daniel Narvaez wrote: On 7 June 2013 15:07, Aleksey Lim alsr...@sugarlabs.org wrote: On Fri, Jun 07, 2013 at 02:55:09PM +0200, Daniel Narvaez wrote: Hi, not sure what Simon and Manuel think about this, but unless someone help us out with

[Sugar-devel] Sugar on Android

2013-06-07 Thread Manuel Quiñones
Hello devs, In the past weeks I've been looking at how an Android Sugar shell could provide the same services as GTK Sugar shell to the web activities. The research is now documented in two pages at developer.sugarlabs.org: - Architecture http://developer.sugarlabs.org/web-architecture.md.html

[Sugar-devel] Sugar Web UI

2013-06-07 Thread Manuel Quiñones
Hello, I want to report the slow but steady progress I'm doing on the web activities UI. I started a samples repository that servers as a showcase for activity developers and as a visual debugging tool for sugar-web developers. published at: https://github.com/sugarlabs/sugar-web-samples repo:

[Sugar-devel] developer.sugarlabs.org index

2013-06-07 Thread Daniel Narvaez
Hey, I think for the introductory docs it would be much better to have index with titles rather then filenames. I don't think docker supports it but perhaps we could add it (just pick the first title in the document) and upstream it. It's probably a good time to think if we want other layout

Re: [Sugar-devel] Sugar Web UI

2013-06-07 Thread Manuel Quiñones
Forgot to say that the whole point of measuring everything in subcell sizes is that it will allow us to support different screens densities and sizes, using the CSS media query. 2013/6/7 Manuel Quiñones ma...@laptop.org: Published at: http://sugarlabs.github.io/sugar-web-samples/ 2013/6/7

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

2013-06-07 Thread Daniel Narvaez
An easy way to generate a custom index would be to generate sidebar-less pages with docker and put them inside an iframe, building links/index with handlebars templates, from an index.json. I'm not in love with the sidebar for introductory docs, I like the pooco approach more

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

2013-06-07 Thread Daniel Narvaez
Well perhaps that's too fancy... Going somewhat crazy with all these nice js libs. Might be enough to add the top links in the markdown (I think you can put plain html in it?). A bit more annoying to maintain but probably not much On Friday, 7 June 2013, Daniel Narvaez wrote: An easy way to

Re: [Sugar-devel] Sugar on Android (Manuel Qui?ones)

2013-06-07 Thread lionel
In the past weeks I've been looking at how an Android Sugar shell could provide the same services as GTK Sugar shell to the web activities. The research is now documented in two pages at developer.sugarlabs.org: - Architecture http://developer.sugarlabs.org/web-architecture.md.html -

Re: [Sugar-devel] Licensing of the javascript libraries

2013-06-07 Thread Daniel Narvaez
We really need to make a call here, we start to have a sizeable amount of code and the first release is near. I tend to think gplv2 is not an option because of the apache incompatibility. I would go for Apache if we want to avoid issues with anti-tivoization, otherwise gplv3. To point out a

Re: [Sugar-devel] Licensing of the javascript libraries

2013-06-07 Thread Daniel Narvaez
I'm still undecided really but since it's important to make a call soon, my vote goes for Apache, both for sugar-web and for activities we develop. On Saturday, 8 June 2013, Daniel Narvaez wrote: We really need to make a call here, we start to have a sizeable amount of code and the first

Re: [Sugar-devel] Licensing of the javascript libraries

2013-06-07 Thread Daniel Narvaez
Ugh one issue with Apache is that I think we would need to get permission to relicense the svg icons under apache from all the people that contributed to them. Do you think that will be possible? People that contributed but doesn't seem to be involved with the project anymore. Eben Eliason Marco

Re: [Sugar-devel] Licensing of the javascript libraries

2013-06-07 Thread Daniel Narvaez
Well permission to double license really. On Saturday, 8 June 2013, Daniel Narvaez wrote: Ugh one issue with Apache is that I think we would need to get permission to relicense the svg icons under apache from all the people that contributed to them. Do you think that will be possible?

Re: [Sugar-devel] Licensing of the javascript libraries

2013-06-07 Thread Gonzalo Odiard
We already had this discussion two years ago, is the situation with the javascript activities different to need start this discussion again? Gonzalo On 06/14/2011 05:42 PM, Luke Faraone wrote: This is a vote to determine the suggested license for future releases of Sugar. This poll will run

Re: [Sugar-devel] Licensing of the javascript libraries

2013-06-07 Thread Daniel Narvaez
Yes I think it's very different because using GPLv2 would mean we can't use Apache licensed libraries, which are a big percentage of available js libraries. On Saturday, 8 June 2013, Gonzalo Odiard wrote: We already had this discussion two years ago, is the situation with the javascript

Re: [Sugar-devel] Licensing of the javascript libraries

2013-06-07 Thread Daniel Narvaez
I'm actually a bit confused about the result of the one year ago discussion. I thought we decided to stay with gplv2 but the poll winner seems to be gplv3? Anyway even on gplv3 I think the situation is pretty different if nothing else because one of major goals of the web activities work is to

Re: [Sugar-devel] Licensing of the javascript libraries

2013-06-07 Thread Walter Bender
On Fri, Jun 7, 2013 at 7:58 PM, Daniel Narvaez dwnarv...@gmail.com wrote: Ugh one issue with Apache is that I think we would need to get permission to relicense the svg icons under apache from all the people that contributed to them. Do you think that will be possible? I am happy to reach out

Re: [Sugar-devel] Licensing of the javascript libraries

2013-06-07 Thread Sebastian Silva
Hi, The poll winner was GPLv3 but the poll was non-binding, i.e. the community can't force contributors to switch licenses and nobody sent a patch to change license notices. I and other members of the community think it's important to support freedom by using copyleft, therefore most of our