Re: [Sugar-devel] Licensing of the javascript libraries
Thanks for clarifying Sebastian. I prefer discussions to polls to make decisions (and a poll would be not binding anyway) but I'm not against a poll if people think it's necessary. On Saturday, 8 June 2013, Sebastian Silva wrote: 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 contributions are using GPLv3. I checked and it turns out Apache 2.0 license is compatible with GPLv3 (but incompatible with GPLv2): http://www.gnu.org/licenses/license-list.html#apache2 Regards, Sebastian El 07/06/13 19:38, Daniel Narvaez escribió: 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 bring activities on devices where tivoization might be an issue. On Saturday, 8 June 2013, Daniel Narvaez wrote: 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 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 from right now until Wed Jun 29 2011 at midnight UTC-4. Sorry for the late update; the reporting mechanism for our voting software temporarily broke. Summary: the winner was **GNU GPL version 3, or any later version**. ## Results Details ## 55 out of 217 eligible members voted, or a little more than ¼. The full results of this election ranked the candidates in order of preference (from most preferred to least preferred): 1. GNU GPL version 3, or any later version 2. GNU GPL version 2, or any later version 3. Don't know or don't care Each number in the table below shows how many times the candidate on the left beat the matching candidate on the top. The winner is on the top of the left column. v3 v2 DC v3-- 34 37 v221 -- 42 DC18 13 -- Based on a sheer count of 1st place votes, v3 received 49% of the vote, v2 received 29% of the vote, and the apathetic position received the remaining 22% of the vote. Full details (and alternative election method calculations) are visible at the Selectricity page linked in the original voting ticket email. Thanks, Luke FaraoneSugar Labs, Systems ✉: l...@sugarlabs.org I: lfaraone on irc.freenode.net On Fri, Jun 7, 2013 at 8:59 PM, Daniel Narvaez dwnarv...@gmail.comwrote: 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? People that contributed but doesn't seem to be involved with the project anymore. Eben Eliason Marco Pesenti Gritti Tomeu Vizoso Still around Scott Ananian benzea erikos Martin Abente Walter Bender godiard Manuel Quinones From the git log of the icons dir. On Saturday, 8 June 2013, Daniel Narvaez -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Licensing of the javascript libraries
Cool. Maybe since you are talking to the SFC already you could ask how to get the contributors permission? I wonder if the mailing list should be cced for example, so that we get a record of it. On Saturday, 8 June 2013, Walter Bender wrote: On Fri, Jun 7, 2013 at 7:58 PM, Daniel Narvaez dwnarv...@gmail.comjavascript:; 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 to Marco, Tomeu and Eben. -walter People that contributed but doesn't seem to be involved with the project anymore. Eben Eliason Marco Pesenti Gritti Tomeu Vizoso Still around Scott Ananian benzea erikos Martin Abente Walter Bender godiard Manuel Quinones From the git log of the icons dir. On Saturday, 8 June 2013, Daniel Narvaez wrote: 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 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 concrete problem we could have with gpl3... My understanding is that you could not ship an activity based on sugar-web in the apple store, at least including the lib locally. I suppose it would be fine if you loaded it from a server, but then you need security restrictions if you implement any kind of system integration. On Friday, 3 May 2013, Daniel Narvaez wrote: Hello, we need to decide how to license the new javascript libraries. I am mostly clueless about the topic and I'm honestly scared to start this thread, please be gentle :) Following is the rationale I came up with for Agora. I think it probably applies to the sugar-html libraries too. Feedback would be very welcome as we are no expert. --- I spent some time trying to decide which license is better for the various part of Agora. It's an hard and important decision, I'm not a lawyer and not even an expert but we need to make a call. My understanding is that a license is better than nothing. (L)GPLv2 * Copyleft. Requires all the modifications to be made freely available. * Incompatible with Apache. Pretty bad, a lot of code already licensed that way and growing fast (especially in the javascript world). (L)GPLv3 * Copyleft * Compatiible with Apache. * Anti-tivoization clause. Mixed bag, would it prevent us to run on hardware we are interested in? One problematic case I can think of is distributing an activity through the Apple store. We wouldn't be able to do that. Though people could still install the activity as a web app, from the browser. Maybe that's good enough? * Latest version. Better wording etc. Patents protection. * We can distribute the sugar icons under LGPLv3, without requiring any relicensing, because of the or later clause. * My understanding is that if xi-* is LGPL, proprietary applications could still use it without making modifications. The situation is not as clear as for the traditional linked libraries case but from http://www.gnu.org/licenses/lgpl-java.html I'd think we are fine. Apache * Non copyleft. It would be more friendly to companies that might want to reuse code in their products. But is that likely to happen? Both xi and omega are pretty agora specific. Still I think it's a good license to use for more generic bits that we might develop (I used it for some python helpers I'm using in eta for example). * It seems to be the best permissive license because of the patents protection. It's the most popular at least. So I think there two choices basical ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org javascript:; http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Licensing of the javascript libraries
On Sat, Jun 8, 2013 at 4:12 AM, Daniel Narvaez dwnarv...@gmail.com wrote: Thanks for clarifying Sebastian. I prefer discussions to polls to make decisions (and a poll would be not binding anyway) but I'm not against a poll if people think it's necessary. FWIW, the poll was only taken after a long discussion where we did not reach consensus. On Saturday, 8 June 2013, Sebastian Silva wrote: 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 contributions are using GPLv3. I checked and it turns out Apache 2.0 license is compatible with GPLv3 (but incompatible with GPLv2): http://www.gnu.org/licenses/license-list.html#apache2 Regards, Sebastian El 07/06/13 19:38, Daniel Narvaez escribió: 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 bring activities on devices where tivoization might be an issue. On Saturday, 8 June 2013, Daniel Narvaez wrote: 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 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 from right now until Wed Jun 29 2011 at midnight UTC-4. Sorry for the late update; the reporting mechanism for our voting software temporarily broke. Summary: the winner was **GNU GPL version 3, or any later version**. ## Results Details ## 55 out of 217 eligible members voted, or a little more than ¼. The full results of this election ranked the candidates in order of preference (from most preferred to least preferred): 1. GNU GPL version 3, or any later version 2. GNU GPL version 2, or any later version 3. Don't know or don't care Each number in the table below shows how many times the candidate on the left beat the matching candidate on the top. The winner is on the top of the left column. v3 v2 DC v3 -- 34 37 v2 21 -- 42 DC 18 13 -- Based on a sheer count of 1st place votes, v3 received 49% of the vote, v2 received 29% of the vote, and the apathetic position received the remaining 22% of the vote. Full details (and alternative election method calculations) are visible at the Selectricity page linked in the original voting ticket email. Thanks, Luke Faraone Sugar Labs, Systems ✉: l...@sugarlabs.org I: lfaraone on irc.freenode.net On Fri, Jun 7, 2013 at 8:59 PM, Daniel Narvaez dwnarv...@gmail.com wrote: 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? People that contributed but doesn't seem to be involved with the project anymore. Eben Eliason Marco Pesenti Gritti Tomeu Vizoso Still around Scott Ananian benzea erikos Martin Abente Walter Bender godiard Manuel Quinones From the git log of the icons dir. On Saturday, 8 June 2013, Daniel Narvaez -- Daniel Narvaez ___ 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
Re: [Sugar-devel] Licensing of the javascript libraries
Let me sum up where I think we are and what questions we have for Tony/Bradley at SFC: (1) We have some of the core Sugar code still under LGPLv2 (e.g., sugar-artwork) which we would like to change to LGPLv3. (2) We would like to add a second (Apache) license to this same code. s there a specific mechanism we should use when reaching out to authors? (3) We want to incorporate some code snippets from some code that is placed in the public domain. Can we include this in an LGPLv3 library? And how do we acknowledge the original author (i.e., do we include him in the new copyright notification)? thanks. -walter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Licensing of the javascript libraries
On 8 June 2013 13:09, Walter Bender walter.ben...@gmail.com wrote: Let me sum up where I think we are and what questions we have for Tony/Bradley at SFC: (1) We have some of the core Sugar code still under LGPLv2 (e.g., sugar-artwork) which we would like to change to LGPLv3. (2) We would like to add a second (Apache) license to this same code. For completeness the double license would apply only to a very small part of the GPL code (a set of svg icons). The reason is that we would like to reuse that in javascript libraries, which would be fully and singly Apache licensed. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Request to get maintainer + release rights on an inactive activity
Just checked. I don't have access to make releases. Could you please re-add me? On Mon, May 27, 2013 at 8:47 PM, Walter Bender walter.ben...@gmail.comwrote: On Mon, May 27, 2013 at 11:14 AM, Walter Bender walter.ben...@gmail.com wrote: I think I can add you to the activity on ASLO, which means you should be able to upload new versions. done. -walter On Mon, May 27, 2013 at 10:46 AM, Aneesh Dogra lionane...@gmail.com wrote: Ping again! Sorry, I almost lost track of this thread. I should have reminded you guys much earlier. On Sat, Feb 2, 2013 at 9:00 PM, Aneesh Dogra lionane...@gmail.com wrote: Patches applied. Should work now! On Sat, Feb 2, 2013 at 11:26 AM, Alan Jhonn Aguiar Schwyn alan...@hotmail.com wrote: Apply 0001 Would a good apply 0002 Date: Fri, 1 Feb 2013 11:25:22 -0300 From: gonz...@laptop.org To: lionane...@gmail.com CC: sugar-devel@lists.sugarlabs.org; garycmar...@googlemail.org; ber...@sugarlabs.org Subject: Re: [Sugar-devel] Request to get maintainer + release rights on an inactive activity Hi Aneesh, I cloned the repository, to look at the work you did and try the activity, but when I want run it, I have the following error: 1359728481.180127 DEBUG root: Activity.__canvas_map_cb Traceback (most recent call last): File /home/gonzalo/sugar-build/install/bin/sugar-activity, line 160, in module main() File /home/gonzalo/sugar-build/install/bin/sugar-activity, line 155, in main instance = create_activity_instance(activity_constructor, activity_handle) File /home/gonzalo/sugar-build/install/bin/sugar-activity, line 42, in create_activity_instance activity = constructor(handle) File /home/gonzalo/Activities/ConstellationsFlashCards.activity/ConstellationsFlashCards.py, line 772, in __init__ self.chart.plotchart(True) File /home/gonzalo/Activities/ConstellationsFlashCards.activity/ConstellationsFlashCards.py, line 304, in plotchart self.plot_sky(newplot) File /home/gonzalo/Activities/ConstellationsFlashCards.activity/ConstellationsFlashCards.py, line 362, in plot_sky self.fill_names_combobox() File /home/gonzalo/Activities/ConstellationsFlashCards.activity/ConstellationsFlashCards.py, line 582, in fill_names_combobox if NUMBER_OF_CHOICES 4: UnboundLocalError: local variable 'NUMBER_OF_CHOICES' referenced before assignment Can you check what is the problem? I am running it in F18, with sugar-build Gonzalo On Thu, Jan 10, 2013 at 3:56 PM, Aneesh Dogra lionane...@gmail.com wrote: I have worked on the Costellation Flash Cards activity including enhancements: Cairo Port, Gtk3 Port, i18n Port and some fixes on how the points were handled. The new repository is located at http://git.sugarlabs.org/constellationsflashcards As the activity hasn't received any form of development since July 6, 2010, I would like to take over the maintainership to continue the development. I would also require admin rights for the activity on http://activities.sugarlabs.org/ to make the releases. -- Thanks Aneesh Dogra (lionaneesh) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Thanks Aneesh Dogra (lionaneesh) -- Thanks Aneesh Dogra (lionaneesh) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Thanks Aneesh Dogra (lionaneesh) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Request to get maintainer + release rights on an inactive activity
Just added you to StarChart -walter On Sat, Jun 8, 2013 at 9:05 AM, Aneesh Dogra lionane...@gmail.com wrote: Just checked. I don't have access to make releases. Could you please re-add me? On Mon, May 27, 2013 at 8:47 PM, Walter Bender walter.ben...@gmail.com wrote: On Mon, May 27, 2013 at 11:14 AM, Walter Bender walter.ben...@gmail.com wrote: I think I can add you to the activity on ASLO, which means you should be able to upload new versions. done. -walter On Mon, May 27, 2013 at 10:46 AM, Aneesh Dogra lionane...@gmail.com wrote: Ping again! Sorry, I almost lost track of this thread. I should have reminded you guys much earlier. On Sat, Feb 2, 2013 at 9:00 PM, Aneesh Dogra lionane...@gmail.com wrote: Patches applied. Should work now! On Sat, Feb 2, 2013 at 11:26 AM, Alan Jhonn Aguiar Schwyn alan...@hotmail.com wrote: Apply 0001 Would a good apply 0002 Date: Fri, 1 Feb 2013 11:25:22 -0300 From: gonz...@laptop.org To: lionane...@gmail.com CC: sugar-devel@lists.sugarlabs.org; garycmar...@googlemail.org; ber...@sugarlabs.org Subject: Re: [Sugar-devel] Request to get maintainer + release rights on an inactive activity Hi Aneesh, I cloned the repository, to look at the work you did and try the activity, but when I want run it, I have the following error: 1359728481.180127 DEBUG root: Activity.__canvas_map_cb Traceback (most recent call last): File /home/gonzalo/sugar-build/install/bin/sugar-activity, line 160, in module main() File /home/gonzalo/sugar-build/install/bin/sugar-activity, line 155, in main instance = create_activity_instance(activity_constructor, activity_handle) File /home/gonzalo/sugar-build/install/bin/sugar-activity, line 42, in create_activity_instance activity = constructor(handle) File /home/gonzalo/Activities/ConstellationsFlashCards.activity/ConstellationsFlashCards.py, line 772, in __init__ self.chart.plotchart(True) File /home/gonzalo/Activities/ConstellationsFlashCards.activity/ConstellationsFlashCards.py, line 304, in plotchart self.plot_sky(newplot) File /home/gonzalo/Activities/ConstellationsFlashCards.activity/ConstellationsFlashCards.py, line 362, in plot_sky self.fill_names_combobox() File /home/gonzalo/Activities/ConstellationsFlashCards.activity/ConstellationsFlashCards.py, line 582, in fill_names_combobox if NUMBER_OF_CHOICES 4: UnboundLocalError: local variable 'NUMBER_OF_CHOICES' referenced before assignment Can you check what is the problem? I am running it in F18, with sugar-build Gonzalo On Thu, Jan 10, 2013 at 3:56 PM, Aneesh Dogra lionane...@gmail.com wrote: I have worked on the Costellation Flash Cards activity including enhancements: Cairo Port, Gtk3 Port, i18n Port and some fixes on how the points were handled. The new repository is located at http://git.sugarlabs.org/constellationsflashcards As the activity hasn't received any form of development since July 6, 2010, I would like to take over the maintainership to continue the development. I would also require admin rights for the activity on http://activities.sugarlabs.org/ to make the releases. -- Thanks Aneesh Dogra (lionaneesh) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Thanks Aneesh Dogra (lionaneesh) -- Thanks Aneesh Dogra (lionaneesh) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Thanks Aneesh Dogra (lionaneesh) -- 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] js-beautify proper max line length
It's pretty bad that js-beautify doesn't have a proper max line length option. I opened a bug about it https://github.com/einars/js-beautify/issues/284 -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] developer.sugarlabs.org index
Hey Daniel, I also find odd the files tab in our docs, and also I miss a link to the index. I would take this approach: - remove the files tab for markdown files in the root folder, use the headings sidebar without the headings title. - have a back to index link on top of the sidebar, that goes to developer.sugarlabs.org. - keep the current behaviour (files and headings tabs) in documented code, like http://developer.sugarlabs.org/sugar-web/graphics/radiobuttonsgroup.js.html What do you think? 2013/6/7 Daniel Narvaez dwnarv...@gmail.com: On 7 June 2013 21:49, Daniel Narvaez dwnarv...@gmail.com wrote: 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 http://flask.pocoo.org/docs/foreword/#configuration-and-conventions Oh, I was looking at flask docs on a phone, and the layout is pretty different. They have a sidebar too on desktop, although nicer than our :) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] developer.sugarlabs.org index
Sounds good! I'll see if I can figure out a way to upstream it, otherwise we will have to patch our fork, not a big problem I think. On 8 June 2013 15:51, Manuel Quiñones ma...@laptop.org wrote: Hey Daniel, I also find odd the files tab in our docs, and also I miss a link to the index. I would take this approach: - remove the files tab for markdown files in the root folder, use the headings sidebar without the headings title. - have a back to index link on top of the sidebar, that goes to developer.sugarlabs.org. - keep the current behaviour (files and headings tabs) in documented code, like http://developer.sugarlabs.org/sugar-web/graphics/radiobuttonsgroup.js.html What do you think? 2013/6/7 Daniel Narvaez dwnarv...@gmail.com: On 7 June 2013 21:49, Daniel Narvaez dwnarv...@gmail.com wrote: 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 http://flask.pocoo.org/docs/foreword/#configuration-and-conventions Oh, I was looking at flask docs on a phone, and the layout is pretty different. They have a sidebar too on desktop, although nicer than our :) ___ 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] js-beautify proper max line length
2013/6/8 Daniel Narvaez dwnarv...@gmail.com: It's pretty bad that js-beautify doesn't have a proper max line length option. I opened a bug about it https://github.com/einars/js-beautify/issues/284 Good. Except for this bug, I think js-beautify does a very nice job for JavaScript code. For HTML and CSS it needs love. That's why I'm not running it in HTML or CSS of my web activities. The things I don't like, and I may open bugs for, are: - it removes empty lines, that are useful for code separation - it adds trailing spaces (see https://github.com/sugarlabs/sugar-web-template/blob/master/index.html#L11) - it can do bad indentation after comments (see https://github.com/sugarlabs/sugar-web-template/blob/master/index.html#L22) -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] js-beautify proper max line length
Yeah would be good to file bugs. The maintainer is quite responsive. On 8 June 2013 16:02, Manuel Quiñones ma...@laptop.org wrote: 2013/6/8 Daniel Narvaez dwnarv...@gmail.com: It's pretty bad that js-beautify doesn't have a proper max line length option. I opened a bug about it https://github.com/einars/js-beautify/issues/284 Good. Except for this bug, I think js-beautify does a very nice job for JavaScript code. For HTML and CSS it needs love. That's why I'm not running it in HTML or CSS of my web activities. The things I don't like, and I may open bugs for, are: - it removes empty lines, that are useful for code separation - it adds trailing spaces (see https://github.com/sugarlabs/sugar-web-template/blob/master/index.html#L11 ) - it can do bad indentation after comments (see https://github.com/sugarlabs/sugar-web-template/blob/master/index.html#L22 ) -- .. manuq .. -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] js-beautify proper max line length
2013/6/8 Daniel Narvaez dwnarv...@gmail.com: Yeah would be good to file bugs. The maintainer is quite responsive. https://github.com/einars/js-beautify/issues/285 -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] developer.sugarlabs.org index
The index link can also be inside a site header, which can be consistently in every page of the developer site. We can use this image: http://wiki.sugarlabs.org/images/e/e2/Join_Developer_BW.png Can also be the favicon :) 2013/6/8 Daniel Narvaez dwnarv...@gmail.com: Sounds good! I'll see if I can figure out a way to upstream it, otherwise we will have to patch our fork, not a big problem I think. On 8 June 2013 15:51, Manuel Quiñones ma...@laptop.org wrote: Hey Daniel, I also find odd the files tab in our docs, and also I miss a link to the index. I would take this approach: - remove the files tab for markdown files in the root folder, use the headings sidebar without the headings title. - have a back to index link on top of the sidebar, that goes to developer.sugarlabs.org. - keep the current behaviour (files and headings tabs) in documented code, like http://developer.sugarlabs.org/sugar-web/graphics/radiobuttonsgroup.js.html What do you think? 2013/6/7 Daniel Narvaez dwnarv...@gmail.com: On 7 June 2013 21:49, Daniel Narvaez dwnarv...@gmail.com wrote: 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 http://flask.pocoo.org/docs/foreword/#configuration-and-conventions Oh, I was looking at flask docs on a phone, and the layout is pretty different. They have a sidebar too on desktop, although nicer than our :) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. -- 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 index
On 8 June 2013 17:11, Manuel Quiñones ma...@laptop.org wrote:
The index link can also be inside a site header, which can be
consistently in every page of the developer site. We can use this
image:
http://wiki.sugarlabs.org/images/e/e2/Join_Developer_BW.png
Can also be the favicon :)
The way I'm doing this is to add an extra to docker and hacking stuff around
#sidebar_switch {
display: none;
}
function(){
var origSwitchTab = switchTab
switchTab = function (tab) {
origSwitchTab(headings);
}
})();
Nice eh? :P
It should be easy to insert that link wherever we want. Do you think the
image is enough or should it have text too?
Perhaps inside the sidebar it would be cleaner layout wise, though if you
have it hidden... Tough I'm not sure it make sense to hide the sidebar for
the introductory docs (it's useful when you have code on the side). Maybe
we just disable the hide thing..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Systems] Moving pootle to github
On 06/07/2013 09:10 AM, Daniel Narvaez wrote: No, just glucose. You can see the exact list of modules on https://github.com/sugarlabs/ By the way, what is sugarlabs, a shared account? Wouldn't this subvert GitHub's philosophy that all forks are created equal, by creating one that looks more official than the others? If it seems that this approach wouldn't be feasible for a project with many collaborators, check out http://git.kernel.org . Most of the repos under kernel/git/ are clones of the kernel tree with various patches applied. The most official tree that I can think of is kernel/git/torvalds/linux.git, the one maintained by Linus. There are of course many other public forks of the Linux kernel hosted on other sites. I'm making the assumption that switching to GitHub was motivated in part by the desire to adopt the bazaar development style. If it's not the case, then GitHub may not be a very good fit for a central repository shared by multiple committers. Just my $0.02, of course. Advance apologies if it's something that has been previously discussed on sugar-devel@ while I wasn't looking. -- Bernie Innocenti Sugar Labs Infrastructure Team http://wiki.sugarlabs.org/go/Infrastructure_Team ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
