Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4
On Sun, Oct 06, 2013 at 09:34:51PM -0700, Yioryos Asprobounitis wrote: 3. external media such as SD card and USB drives are not always available, but internal media is always available, That is also why we do not provide zd images that would be easier to install. People that want it in the internal eMMC should know how to do it too ;) For people who want to try your build, you have made it harder for them, for (in my opinion) no good reason. You need not use zd images. A simple Forth script would do fine. ok d# 4096 fat32-partition int ok copy u:\fd-arm.sfs int:\fd-arm.sfs ok mkdir int:\boot ok copy u:\boot\initrd.4 int:\boot\initrd.4 ok copy u:\boot\vmlinuz.4 int:\boot\vmlinuz.4 ok copy u:\boot\olpc.fth int:\boot\olpc.fth ok bye Thanks you for the script. However this would imply that you already have expanded the tarball in a stick and then you copy over instead of just booting from it. So is hard to see how is any easier for the user. Yes, because you used a container format with no firmware support. Why didn't you use .zip? Can also copy out members from within .zip file using Open Firmware. What would be interesting is to download the the zipped file in the internal card and then have forth do the rest. Is it possible to read the file from int:\home\olpc\Downloads\file.zip, keep it in RAM, format int and write back from RAM? The versioned filesystem of OLPC OS makes this impractical. Though, come to think of it you may not need any of these. Could use alt-boot (assuming is empty) and existing partitions. Fatdog does not really care what else is in the partitions. The challenge in this case is the fatdog-xo olpc.fth to know which device and setting we boot from and act accordingly in all possible scenarios. If you wanted to set up a barrier to booting from internal storage, there are probably more logical methods. Suggestions are welcome as always ;) Detecting that olpc.fth was loaded from internal storage and then terminating with a message is probably more appropriate. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Help
Unsubscribe me from this list please. On Oct 7, 2013, at 11:01 AM, devel-requ...@lists.laptop.org devel-requ...@lists.laptop.org wrote: Send Devel mailing list submissions to devel@lists.laptop.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.laptop.org/listinfo/devel or, via email, send a message with subject or body 'help' to devel-requ...@lists.laptop.org You can reach the person managing the list at devel-ow...@lists.laptop.org When replying, please edit your Subject line so it is more specific than Re: Contents of Devel digest... Today's Topics: 1. Android on the XO-4 (Sameer Verma) 2. Re: Android on the XO-4 (Walter Bender) 3. Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4 (James Cameron) 4. Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4 (Yioryos Asprobounitis) 5. Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4 (James Cameron) -- Message: 1 Date: Sun, 6 Oct 2013 11:03:05 -0700 From: Sameer Verma sve...@sfsu.edu To: Devel's in the Details devel@lists.laptop.org,John Gilmore g...@toad.com Subject: Android on the XO-4 Message-ID: cafogk8ejchhg5ufblpzcbqo838jaguxriueap9+fv98eava...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 I was at the Internet Archive for some work on Pathagar (https://github.com/PathagarBooks/pathagar). Also there that afternoon was John Gilmore (cc'd). We got to talking about the XO-4, Android, HTML5, etc. A bit of doodling on Physics, and John put together a two cylinder engine, complete with a rocker arm :-) He also suggested the possibility of CyanogenMod on the XO-4 as a starting point. If there is any interest in this, please submit a proposal for the upcoming OLPC SF summit http://www.olpcsf.org/CommunitySummit2013/proposal John, If you are in town Oct 18-20, we'd love to have you there. http://olpcsf.org/summit cheers, Sameer -- Sameer Verma, Ph.D. Professor, Information Systems San Francisco State University http://verma.sfsu.edu/ http://commons.sfsu.edu/ http://olpcsf.org/ http://olpcjamaica.org.jm/ -- Message: 2 Date: Sun, 6 Oct 2013 15:29:10 -0400 From: Walter Bender walter.ben...@gmail.com To: Sameer Verma sve...@sfsu.edu Cc: Devel's in the Details devel@lists.laptop.org,John Gilmore g...@toad.com Subject: Re: Android on the XO-4 Message-ID: CADf7C8tYNdp-Hv-RXHo54X=9csforwqq33dgy+rln03wsex...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 Not sure this helps us get around the Marvel bottleneck, but worth investigating. -walter On Sun, Oct 6, 2013 at 2:03 PM, Sameer Verma sve...@sfsu.edu wrote: I was at the Internet Archive for some work on Pathagar (https://github.com/PathagarBooks/pathagar). Also there that afternoon was John Gilmore (cc'd). We got to talking about the XO-4, Android, HTML5, etc. A bit of doodling on Physics, and John put together a two cylinder engine, complete with a rocker arm :-) He also suggested the possibility of CyanogenMod on the XO-4 as a starting point. If there is any interest in this, please submit a proposal for the upcoming OLPC SF summit http://www.olpcsf.org/CommunitySummit2013/proposal John, If you are in town Oct 18-20, we'd love to have you there. http://olpcsf.org/summit cheers, Sameer -- Sameer Verma, Ph.D. Professor, Information Systems San Francisco State University http://verma.sfsu.edu/ http://commons.sfsu.edu/ http://olpcsf.org/ http://olpcjamaica.org.jm/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Message: 3 Date: Mon, 7 Oct 2013 10:54:45 +1100 From: James Cameron qu...@laptop.org To: Yioryos Asprobounitis mavrot...@yahoo.com Cc: OLPC Devel devel@lists.laptop.org Subject: Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4 Message-ID: 20131006235445.gc19...@us.netrek.org Content-Type: text/plain; charset=iso-8859-1 On Fri, Oct 04, 2013 at 10:32:17PM -0700, Yioryos Asprobounitis wrote: Does not boot if the files are unpacked onto internal eMMC and no external SD card is present.? Workaround: edit olpc.fth to ensure mmcblk0 is used regardless. Thanks for the suggestion. However, we do not want to affect the original XO OS. Don't worry about that. 1. for laptops in deployments where this is important, the laptops are locked and won't be able to install your build, 2. the OLPC OS is very easily reinstalled, insert USB drive, hold down four keys, press power button, 3. external media such as SD card and USB drives are not always available, but internal media is always available, That is also why we do not provide zd images that would be easier to install. People that want it in the
Re: Help
You can unsubscribe yourself at the bottom of this page http://lists.laptop.org/listinfo/devel Gonzalo On Mon, Oct 7, 2013 at 1:08 PM, Anderson, Nicole A nander...@winona.eduwrote: Unsubscribe me from this list please. On Oct 7, 2013, at 11:01 AM, devel-requ...@lists.laptop.org devel-requ...@lists.laptop.org wrote: Send Devel mailing list submissions to devel@lists.laptop.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.laptop.org/listinfo/devel or, via email, send a message with subject or body 'help' to devel-requ...@lists.laptop.org You can reach the person managing the list at devel-ow...@lists.laptop.org When replying, please edit your Subject line so it is more specific than Re: Contents of Devel digest... Today's Topics: 1. Android on the XO-4 (Sameer Verma) 2. Re: Android on the XO-4 (Walter Bender) 3. Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4 (James Cameron) 4. Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4 (Yioryos Asprobounitis) 5. Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4 (James Cameron) -- Message: 1 Date: Sun, 6 Oct 2013 11:03:05 -0700 From: Sameer Verma sve...@sfsu.edu To: Devel's in the Details devel@lists.laptop.org,John Gilmore g...@toad.com Subject: Android on the XO-4 Message-ID: cafogk8ejchhg5ufblpzcbqo838jaguxriueap9+fv98eava...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 I was at the Internet Archive for some work on Pathagar (https://github.com/PathagarBooks/pathagar). Also there that afternoon was John Gilmore (cc'd). We got to talking about the XO-4, Android, HTML5, etc. A bit of doodling on Physics, and John put together a two cylinder engine, complete with a rocker arm :-) He also suggested the possibility of CyanogenMod on the XO-4 as a starting point. If there is any interest in this, please submit a proposal for the upcoming OLPC SF summit http://www.olpcsf.org/CommunitySummit2013/proposal John, If you are in town Oct 18-20, we'd love to have you there. http://olpcsf.org/summit cheers, Sameer -- Sameer Verma, Ph.D. Professor, Information Systems San Francisco State University http://verma.sfsu.edu/ http://commons.sfsu.edu/ http://olpcsf.org/ http://olpcjamaica.org.jm/ -- Message: 2 Date: Sun, 6 Oct 2013 15:29:10 -0400 From: Walter Bender walter.ben...@gmail.com To: Sameer Verma sve...@sfsu.edu Cc: Devel's in the Details devel@lists.laptop.org,John Gilmore g...@toad.com Subject: Re: Android on the XO-4 Message-ID: CADf7C8tYNdp-Hv-RXHo54X=9csforwqq33dgy+rln03wsex...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 Not sure this helps us get around the Marvel bottleneck, but worth investigating. -walter On Sun, Oct 6, 2013 at 2:03 PM, Sameer Verma sve...@sfsu.edu wrote: I was at the Internet Archive for some work on Pathagar (https://github.com/PathagarBooks/pathagar). Also there that afternoon was John Gilmore (cc'd). We got to talking about the XO-4, Android, HTML5, etc. A bit of doodling on Physics, and John put together a two cylinder engine, complete with a rocker arm :-) He also suggested the possibility of CyanogenMod on the XO-4 as a starting point. If there is any interest in this, please submit a proposal for the upcoming OLPC SF summit http://www.olpcsf.org/CommunitySummit2013/proposal John, If you are in town Oct 18-20, we'd love to have you there. http://olpcsf.org/summit cheers, Sameer -- Sameer Verma, Ph.D. Professor, Information Systems San Francisco State University http://verma.sfsu.edu/ http://commons.sfsu.edu/ http://olpcsf.org/ http://olpcjamaica.org.jm/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Message: 3 Date: Mon, 7 Oct 2013 10:54:45 +1100 From: James Cameron qu...@laptop.org To: Yioryos Asprobounitis mavrot...@yahoo.com Cc: OLPC Devel devel@lists.laptop.org Subject: Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4 Message-ID: 20131006235445.gc19...@us.netrek.org Content-Type: text/plain; charset=iso-8859-1 On Fri, Oct 04, 2013 at 10:32:17PM -0700, Yioryos Asprobounitis wrote: Does not boot if the files are unpacked onto internal eMMC and no external SD card is present.? Workaround: edit olpc.fth to ensure mmcblk0 is used regardless. Thanks for the suggestion. However, we do not want to affect the original XO OS. Don't worry about that. 1. for laptops in deployments where this is important, the laptops are locked and won't be able to install your build, 2. the OLPC OS is very easily
Activity Central's Sugar related priorities.
As a data point for other decision makers and a follow up to some of the recent threads on the future of Sugar, I would like to share Activity Central's Sugar priorities for the next six months. Activity Central supports the recent HTML5 + JS work that is going into sugar .100. It has the potential to take the OLPC vision to any device which runs a browser while simultaneously increasing the potential activity developer pool by several orders of magnitude. This is an excellent area for community lead research. Activity Central will be doing activity side work to test the viability of the framework for client deployments. As a more incremental approach, Activity Central will continue our deployment-centric work by porting Dextrose to Ubuntu. A concern among deployments is the future availability of hardware to support their current investment. Deployments are concerned that laptop support will stop before tablets are ready for use in the field. Because of the controversial nature of this work and the potential for disruption it may cause to the Association, we understand if some people would prefer to sit this out. Would either of these list be appropriate to continue these discussions about this downstream efforts to port sugar to Ubuntu for use on hardware not sold by the Association? Phase one has been a poof of concept as seen at http://wiki.sugarlabs.org/go/Ubuntu (ongoing) Phase two will be opening the project to the community. Phases three will be testing and piloting by deployments. -- David Farning Activity Central: http://www.activitycentral.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
A robotics session at OLPC SF?
We have the Uruguay Butia robot, a couple of LEGO WeDo kits and a Mindstorms NXT box that we can provide. Any takers on running a session on robotics at the OLPC SF Community Summit 2013? http://www.olpcsf.org/CommunitySummit2013/proposal cheers, Sameer -- Sameer Verma, Ph.D. Professor, Information Systems San Francisco State University http://verma.sfsu.edu/ http://commons.sfsu.edu/ http://olpcsf.org/ http://olpcjamaica.org.jm/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Arch Linux XO image and Sugar packages
Hello, I setup a buildbot instance to build the packages daily, using the XO as a build slave for arm http://sugarlabs.org:8011/waterfall https://github.com/dnarvaez/archbot You can pull them by adding this to your /etc/pacman.conf [sugar] SigLevel = Never Server = http://sugarlabs.org/~dnarvaez/archsugar/$arch I tested them on my laptop and on the XO. Though Arch Linux Arm supports a lot of devices, including the Raspberry PI http://archlinuxarm.org/platforms If you have any of these please give it a try, I'd be happy to try to fix stuff up if it doesn't work for some reason. (I have armv7 packages but not armv6 and armv5 yet, as you can see from the buildbot, hopefully I will figure out those soon). ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Activity Central's Sugar related priorities.
Disclaimer: These are my personal views, and are not the official views of OLPC. - It should be fine to discuss anything Sugar-related on the sugarlabs.org development lists. Sugar Labs does not use any OLPC hosting services, and is an independent group as part of the Software Freedom Conservancy. - I cannot comment on future OLPC hardware plans. If OLPC was to publicly announce their intent to go in a similar direction the laptop.org mailing lists might be appropriate; however otherwise they may not be. It sounds like you are discussing a software change for different hardware than anything OLPC related though. Other vendors besides OLPC have sold laptops with Sugar preinstalled on top of Fedora or Ubuntu in the past, so you are not breaking new ground. - Updating the Sugar release in Ubuntu sounds like something everyone could benefit from, not just Dextrose users. Is there any reason not to base most of this work starting with upstream Sugar existing Ubuntu packages? - In general one of my frustrations lately is that now that we no longer publicly review patches on this mailing list, everyone seems to be developing their own version of Sugar. While some of these changes may make it back upstream it would be nice to see EduJAM and OLPC-SF discussion about trying to limit this. I know Activity Central is trying to publicly state a bit what they're up to, and Walter does his weekly state of the union reports. I also personally hear some private updates as well. But the different working styles of the various groups is starting to confuse me as to which way Sugar is going as a whole. On Mon, Oct 7, 2013 at 12:41 PM, David Farning dfarn...@activitycentral.com wrote: As a data point for other decision makers and a follow up to some of the recent threads on the future of Sugar, I would like to share Activity Central's Sugar priorities for the next six months. Activity Central supports the recent HTML5 + JS work that is going into sugar .100. It has the potential to take the OLPC vision to any device which runs a browser while simultaneously increasing the potential activity developer pool by several orders of magnitude. This is an excellent area for community lead research. Activity Central will be doing activity side work to test the viability of the framework for client deployments. As a more incremental approach, Activity Central will continue our deployment-centric work by porting Dextrose to Ubuntu. A concern among deployments is the future availability of hardware to support their current investment. Deployments are concerned that laptop support will stop before tablets are ready for use in the field. Because of the controversial nature of this work and the potential for disruption it may cause to the Association, we understand if some people would prefer to sit this out. Would either of these list be appropriate to continue these discussions about this downstream efforts to port sugar to Ubuntu for use on hardware not sold by the Association? Phase one has been a poof of concept as seen at http://wiki.sugarlabs.org/go/Ubuntu (ongoing) Phase two will be opening the project to the community. Phases three will be testing and piloting by deployments. -- David Farning Activity Central: http://www.activitycentral.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[Server-devel] OLPC SF submissions?
Server people, Any plans to submit sessions? http://www.olpcsf.org/CommunitySummit2013/proposal Sooner the better. As in ASAP! It helps the sessions team with organizing rooms and time slots. cheers, Sameer -- Sameer Verma, Ph.D. Professor, Information Systems San Francisco State University http://verma.sfsu.edu/ http://commons.sfsu.edu/ http://olpcsf.org/ http://olpcjamaica.org.jm/ ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
On 7 October 2013 19:24, Samuel Greenfeld greenf...@laptop.org wrote: - Updating the Sugar release in Ubuntu sounds like something everyone could benefit from, not just Dextrose users. Is there any reason not to base most of this work starting with upstream Sugar existing Ubuntu packages? +1 - In general one of my frustrations lately is that now that we no longer publicly review patches on this mailing list, everyone seems to be developing their own version of Sugar. Can you elaborate on this one? I haven't noticed this kind of change (and we have not been reviewing most patches on the mailing list since a long long time, well before the github switch). ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
On 7 October 2013 18:41, David Farning dfarn...@activitycentral.com wrote: Would either of these list be appropriate to continue these discussions about this downstream efforts to port sugar to Ubuntu for use on hardware not sold by the Association? Phase one has been a poof of concept as seen at http://wiki.sugarlabs.org/go/Ubuntu (ongoing) Phase two will be opening the project to the community. Phases three will be testing and piloting by deployments. I would like to understand better what you mean with porting. It should just be matter of writing package specs (or really fixing the existing ones...), no? If there is any more work involved strongly suggest you first discuss it on this mailing list, then have it done upstream directly. That way the whole community will benefit from your effort and you will benefit from the community input. Upstreaming after the fact rarely works. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
In general one of my frustrations lately is that now that we no longer publicly review patches on this mailing list, everyone seems to be developing their own version of Sugar. Can you elaborate on this one? I haven't noticed this kind of change (and we have not been reviewing most patches on the mailing list since a long long time, well before the github switch). I think the change was the movement to github. If we can add sugar-devel mailing list to the github mail destinations, that can be solved. Gonzalo ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [ANNOUNCE] Fatdog-ARM Linux for the XO-4
For people who want to try your build, you have made it harder for them, for (in my opinion) no good reason. Here is a script that will download FatDog-ARM Linux for the XO-4 (if not already downloaded) and install it along side the Fedora build in the internal storage as an alt-boot, so you can start it pressing the O game-key during power-up. Hopefully that's easy enough and still does not affect the official build on the laptop. Best install_fd_internally.sh.gz Description: GNU Zip compressed data ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
On Monday, 7 October 2013, Gonzalo Odiard wrote: In general one of my frustrations lately is that now that we no longer publicly review patches on this mailing list, everyone seems to be developing their own version of Sugar. Can you elaborate on this one? I haven't noticed this kind of change (and we have not been reviewing most patches on the mailing list since a long long time, well before the github switch). I think the change was the movement to github. If we can add sugar-devel mailing list to the github mail destinations, that can be solved. I was mostly concerned about Samuel feeling that everyone is developing they're own version of Sugar. I don't see that or at least I don't see differences with the past. We probably can have sugar-devel as email destination... Though I'm not sure why people wouldn't just watch the modules they are interested in? It seems more flexible. Anyway not opposed to send all modules to the whole mailing list if there is consensus on that. -- Daniel Narvaez ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
On Mon, Oct 7, 2013 at 3:58 PM, Daniel Narvaez dwnarv...@gmail.com wrote: On 7 October 2013 18:41, David Farning dfarn...@activitycentral.comwrote: Would either of these list be appropriate to continue these discussions about this downstream efforts to port sugar to Ubuntu for use on hardware not sold by the Association? Phase one has been a poof of concept as seen at http://wiki.sugarlabs.org/go/Ubuntu (ongoing) Phase two will be opening the project to the community. Phases three will be testing and piloting by deployments. I would like to understand better what you mean with porting. It should just be matter of writing package specs (or really fixing the existing ones...), no? I agree. Have Sugar working on Ubuntu would be great, but would be mainly: * Solve dependencies in ubuntu (update/fix packages) * Make Sugar work with other dependencies when is not possible. In the first case, upstream is Ubuntu, in the second case, upstream is Sugarlabs. In both cases, working with upstream is the best solution in the long run, while I understand for Dextrose is useful have some exclusive features, I hope you avoid the shortcut and plan thinking in the future. Gonzalo If there is any more work involved strongly suggest you first discuss it on this mailing list, then have it done upstream directly. That way the whole community will benefit from your effort and you will benefit from the community input. Upstreaming after the fact rarely works. ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
On Mon, Oct 7, 2013 at 12:41 PM, David Farning dfarn...@activitycentral.com wrote: As a more incremental approach, Activity Central will continue our deployment-centric work by porting Dextrose to Ubuntu. From a deploy to XOs PoV that sounds like a ton of work. You'll grind against a lot of little problems. Fedora is no longer behind nor problematic. That was very much true in earlier times. Some innovative things in Fedora (ie: systemd) have been very well integrated with the Sugar stack. And some changes in the Ubuntu pipeline are likely to cause some havoc. From a work for AC customers already using Ubuntu, it probably makes more sense. Still, the odd directions Ubuntu seems to be going are a bit of a wildcard. I honestly hope that they settle a bit and make life for their downstreams a bit easier. cheers, m -- martin.langh...@gmail.com - ask interesting questions - don't get distracted with shiny stuff - working code first ~ http://docs.moodle.org/en/User:Martin_Langhoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
I agree with Martin on the odd directions Ubuntu is exhibiting; it may be safer to target Debian instead, from which support for Ubuntu will generally follow. (On the other hand, I lack evidence to agree with claims about the stability or direction of Fedora. So few people I know use it.) -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
Daniel Narvaez wrote: Gonzalo Odiard wrote: Daniel wrote: Gonzalo Odiard wrote: Samuel Wrote: In general one of my frustrations lately is that now that we no longer publicly review patches on this mailing list, everyone seems to be developing their own version of Sugar. Can you elaborate on this one? I haven't noticed this kind of change (and we have not been reviewing most patches on the mailing list since a long long time, well before the github switch). I think the change was the movement to github. If we can add sugar-devel mailing list to the github mail destinations, that can be solved. I was mostly concerned about Samuel feeling that everyone is developing they're own version of Sugar. I don't see that or at least I don't see differences with the past. I agree with Samuel; that with the loss of public review of patches participation in development has been confined to those who take the trouble to visit a web site. (The reviews by mail were also stimulating other discussion on list). So on the theory that developers are developing with less review (even though it might be unseen greater review), this leads to the conclusion that Sugar is being developed by these developers on their own. And, actually, I'm fine with that. A smaller group can achieve more if they are able to use these new tools effectively. I have not been effective since that change, but you would have seen that a review counter or tracking? Has there been a measure of review rate? We probably can have sugar-devel as email destination... Though I'm not sure why people wouldn't just watch the modules they are interested in? It seems more flexible. Anyway not opposed to send all modules to the whole mailing list if there is consensus on that. I don't see how watching the modules they are interested in is more flexible, nor whether greater flexibility increases the communication. Please don't configure github to send links to the patches; they have to be the patches themselves. They should also have a from address that matches the originator. What used to happen was easy. Get a mail with the patch. Scroll it down while reviewing it. When the cognitive dissonance hits a threshold, hit the reply button and begin a comment. Press send. Mail is a store and forward architecture. I can use mail without having to wait for an internet connection. Github is not so lucky: $ ping -n github.com rtt min/avg/max/mdev = 288.440/606.297/1049.233/262.776 ms, pipe 2 -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
On 7 October 2013 23:39, James Cameron qu...@laptop.org wrote: I agree with Samuel; that with the loss of public review of patches participation in development has been confined to those who take the trouble to visit a web site. (The reviews by mail were also stimulating other discussion on list). So on the theory that developers are developing with less review (even though it might be unseen greater review), this leads to the conclusion that Sugar is being developed by these developers on their own. Well everyone seems to be developing their own version of Sugar seems to be more than that. But maybe I'm just reading too much into it. There aren't multiple groups of people or individuals developing sugar on their own. As far as I know all the work that is being done these days is going upstream. And, actually, I'm fine with that. A smaller group can achieve more if they are able to use these new tools effectively. I have not been effective since that change, but you would have seen that a review counter or tracking? I can't parse this question. Has there been a measure of review rate? We usually have 1 reviewer per patch. All the patches that have been submitted so far has been reviewed and landed. We probably can have sugar-devel as email destination... Though I'm not sure why people wouldn't just watch the modules they are interested in? It seems more flexible. Anyway not opposed to send all modules to the whole mailing list if there is consensus on that. I don't see how watching the modules they are interested in is more flexible, nor whether greater flexibility increases the communication. Because if we send patches to the mailing I'm pretty sure some people will be annoyed. In fact someone got annoyed when he was added to the reviewers group and started getting email. Please don't configure github to send links to the patches; they have to be the patches themselves. They should also have a from address that matches the originator. I highly doubt what you want is possible, at least without doing substantial work... If you have time feel free. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
2013/10/7 James Cameron qu...@laptop.org: Daniel Narvaez wrote: Gonzalo Odiard wrote: Daniel wrote: Gonzalo Odiard wrote: Samuel Wrote: In general one of my frustrations lately is that now that we no longer publicly review patches on this mailing list, everyone seems to be developing their own version of Sugar. Can you elaborate on this one? I haven't noticed this kind of change (and we have not been reviewing most patches on the mailing list since a long long time, well before the github switch). I think the change was the movement to github. If we can add sugar-devel mailing list to the github mail destinations, that can be solved. I was mostly concerned about Samuel feeling that everyone is developing they're own version of Sugar. I don't see that or at least I don't see differences with the past. I agree with Samuel; that with the loss of public review of patches participation in development has been confined to those who take the trouble to visit a web site. (The reviews by mail were also stimulating other discussion on list). So on the theory that developers are developing with less review (even though it might be unseen greater review), this leads to the conclusion that Sugar is being developed by these developers on their own. And, actually, I'm fine with that. A smaller group can achieve more if they are able to use these new tools effectively. I have not been effective since that change, but you would have seen that a review counter or tracking? Has there been a measure of review rate? We probably can have sugar-devel as email destination... Though I'm not sure why people wouldn't just watch the modules they are interested in? It seems more flexible. Anyway not opposed to send all modules to the whole mailing list if there is consensus on that. I don't see how watching the modules they are interested in is more flexible, nor whether greater flexibility increases the communication. James, Sam, I see this as a question of taste. At least starters find very odd emails with patch format in pain text. At least one reviewer (me) find very odd copy/pasting the email content to a file in order to give the patch a test. And we had the problem of email-patches being forgotten in the flow of threads. That is fixed, with zero patches in queue. As Daniel said, you can receive email notifications from GitHub by watching repositories. Please don't configure github to send links to the patches; they have to be the patches themselves. They should also have a from address that matches the originator. What used to happen was easy. Get a mail with the patch. Scroll it down while reviewing it. When the cognitive dissonance hits a threshold, hit the reply button and begin a comment. Press send. Mail is a store and forward architecture. I can use mail without having to wait for an internet connection. Github is not so lucky: $ ping -n github.com rtt min/avg/max/mdev = 288.440/606.297/1049.233/262.776 ms, pipe 2 -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- .. manuq .. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
On 8 October 2013 00:08, Manuel Quiñones ma...@laptop.org wrote: James, Sam, I see this as a question of taste. Exactly. The sooner people understand that, the sooner we will stop having discussions about the review process over and over :) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
On Tue, Oct 08, 2013 at 12:00:47AM +0200, Daniel Narvaez wrote: Well everyone seems to be developing their own version of Sugar seems to be more than that. But maybe I'm just reading too much into it. There aren't multiple groups of people or individuals developing sugar on their own. As far as I know all the work that is being done these days is going upstream. Good. I only know of four Sugars. Sugar upstream, Dextrose, what is in OLPC OS, and what is in the Australian builds. There might be more, but I'm not aware of them. I also don't know the difference between each. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
On Mon, Oct 7, 2013 at 10:10 PM, James Cameron qu...@laptop.org wrote: I agree with Martin on the odd directions Ubuntu is exhibiting; it may be safer to target Debian instead, from which support for Ubuntu will generally follow. (On the other hand, I lack evidence to agree with claims about the stability or direction of Fedora. So few people I know use it.) So few people I know use Windows but that doesn't mean it's no longer prevalent, from what I've seen there's been quite a large swing back to it due to the problems with Ubuntu and most of the upstream developers of a lot of the stack that sugar relies upon now use Fedora as their core development OS because of the issues they see with Ubuntu. Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] [support-gang] Helping test Sugar 0.100
On Fri, Sep 27, 2013 at 3:21 PM, Gonzalo Odiard gonz...@laptop.org wrote: No, I never had a koji user. How can I have one? Become a Fedora packager. Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
On 8 October 2013 00:22, James Cameron qu...@laptop.org wrote: On Tue, Oct 08, 2013 at 12:00:47AM +0200, Daniel Narvaez wrote: Well everyone seems to be developing their own version of Sugar seems to be more than that. But maybe I'm just reading too much into it. There aren't multiple groups of people or individuals developing sugar on their own. As far as I know all the work that is being done these days is going upstream. Good. I only know of four Sugars. Sugar upstream, Dextrose, what is in OLPC OS, and what is in the Australian builds. There might be more, but I'm not aware of them. I also don't know the difference between each. Australia builds have apparently a few non-yet-upstreamed patches. Both Gonzalo and Walter are very much involved in upstream work, I'm absolutely confident they will upstream as soon as it make sense. OLPC OS is pretty much all upstream, as far as I know. Dextrose. I know they accumulated non-upstream patches in the past. We landed a couple of features coming from there before the freeze. I'm not sure what is going on these days, which is why I wanted to know more from David about the porting they are doing. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
This actually is kind of what I meant (and perhaps should be a separate thread). My understanding is that deployments nowadays are the primary parties funding Sugar development. And the deployments or their contractors sometimes duplicate work, run into debates upstreaming things, and/or may choose to keep some things semi-private to differentiate their products. So apart from major functionality like HTML5 activities, a lot of peripheral development is happening downstream-first. And when we do try to do major cross-group development like the GTK3 port, this has lead to finger-pointing behind the scenes where it is claimed others are not doing what they promised. To the best of my knowledge no single organization currently employs enough developers and/or contractors to keep Sugar development alive. I am not certain what the best approach to take is when this is the case. On Mon, Oct 7, 2013 at 6:22 PM, James Cameron qu...@laptop.org wrote: On Tue, Oct 08, 2013 at 12:00:47AM +0200, Daniel Narvaez wrote: Well everyone seems to be developing their own version of Sugar seems to be more than that. But maybe I'm just reading too much into it. There aren't multiple groups of people or individuals developing sugar on their own. As far as I know all the work that is being done these days is going upstream. Good. I only know of four Sugars. Sugar upstream, Dextrose, what is in OLPC OS, and what is in the Australian builds. There might be more, but I'm not aware of them. I also don't know the difference between each. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
My 2 cents: Since the switch to github, we've have a much better turn-around on reviews and we've attacked new reviewers. I think those data speak for themselves. As Daniel said, we welcome help further shaping the process. regards. -walter On Mon, Oct 7, 2013 at 6:08 PM, Manuel Quiñones ma...@laptop.org wrote: 2013/10/7 James Cameron qu...@laptop.org: Daniel Narvaez wrote: Gonzalo Odiard wrote: Daniel wrote: Gonzalo Odiard wrote: Samuel Wrote: In general one of my frustrations lately is that now that we no longer publicly review patches on this mailing list, everyone seems to be developing their own version of Sugar. Can you elaborate on this one? I haven't noticed this kind of change (and we have not been reviewing most patches on the mailing list since a long long time, well before the github switch). I think the change was the movement to github. If we can add sugar-devel mailing list to the github mail destinations, that can be solved. I was mostly concerned about Samuel feeling that everyone is developing they're own version of Sugar. I don't see that or at least I don't see differences with the past. I agree with Samuel; that with the loss of public review of patches participation in development has been confined to those who take the trouble to visit a web site. (The reviews by mail were also stimulating other discussion on list). So on the theory that developers are developing with less review (even though it might be unseen greater review), this leads to the conclusion that Sugar is being developed by these developers on their own. And, actually, I'm fine with that. A smaller group can achieve more if they are able to use these new tools effectively. I have not been effective since that change, but you would have seen that a review counter or tracking? Has there been a measure of review rate? We probably can have sugar-devel as email destination... Though I'm not sure why people wouldn't just watch the modules they are interested in? It seems more flexible. Anyway not opposed to send all modules to the whole mailing list if there is consensus on that. I don't see how watching the modules they are interested in is more flexible, nor whether greater flexibility increases the communication. James, Sam, I see this as a question of taste. At least starters find very odd emails with patch format in pain text. At least one reviewer (me) find very odd copy/pasting the email content to a file in order to give the patch a test. And we had the problem of email-patches being forgotten in the flow of threads. That is fixed, with zero patches in queue. As Daniel said, you can receive email notifications from GitHub by watching repositories. Please don't configure github to send links to the patches; they have to be the patches themselves. They should also have a from address that matches the originator. What used to happen was easy. Get a mail with the patch. Scroll it down while reviewing it. When the cognitive dissonance hits a threshold, hit the reply button and begin a comment. Press send. Mail is a store and forward architecture. I can use mail without having to wait for an internet connection. Github is not so lucky: $ ping -n github.com rtt min/avg/max/mdev = 288.440/606.297/1049.233/262.776 ms, pipe 2 -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- .. manuq .. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
On 8 October 2013 01:07, Samuel Greenfeld greenf...@laptop.org wrote: This actually is kind of what I meant (and perhaps should be a separate thread). To simplify things I will only answer about the 0.100 release cycle. Things have changed a lot anyway and it's probably not worth focusing on the past. My understanding is that deployments nowadays are the primary parties funding Sugar development. And the deployments or their contractors sometimes duplicate work, run into debates upstreaming things, and/or may choose to keep some things semi-private to differentiate their products. There has been debate only about one set of patches which was too big and complicated to review. Someone took care of splitting it up in the end though and it landed. I'm not aware of duplicate work. I'm not aware of semi-private things used to differentiate products. So apart from major functionality like HTML5 activities, a lot of peripheral development is happening downstream-first. And when we do try to do major cross-group development like the GTK3 port, this has lead to finger-pointing behind the scenes where it is claimed others are not doing what they promised. I don't think a lot of development is happening downstream. I have to admit I don't have much visibility about Dextrose/Activity Central though. I think it's fine for some development to land downstream first, as long as it is discussed openly from the beginning. It's often a good way to try things out... To the best of my knowledge no single organization currently employs enough developers and/or contractors to keep Sugar development alive. I am not certain what the best approach to take is when this is the case. I'm more concerned that even summing up the resources, there might not be enough to keep development alive. It really worried me that very little testing, bug triaging and bug fixing is happening for 0.100. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
On Mon, Oct 7, 2013 at 6:00 PM, Daniel Narvaez dwnarv...@gmail.com wrote: On 7 October 2013 23:39, James Cameron qu...@laptop.org wrote: I agree with Samuel; that with the loss of public review of patches participation in development has been confined to those who take the trouble to visit a web site. (The reviews by mail were also stimulating other discussion on list). So on the theory that developers are developing with less review (even though it might be unseen greater review), this leads to the conclusion that Sugar is being developed by these developers on their own. Well everyone seems to be developing their own version of Sugar seems to be more than that. But maybe I'm just reading too much into it. I am only aware of one group developing their own version of Sugar: Activity Central. There is the Sugar Network project as well, but that is more about glue around Sugar. Gonzalo and I are working with Sugar upstream in Australia (although we are ahead of master in a few places as Sugar 100 has been in freeze). There aren't multiple groups of people or individuals developing sugar on their own. As far as I know all the work that is being done these days is going upstream. regards. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
On Mon, Oct 7, 2013 at 7:45 PM, Ruben Rodríguez ru...@activitycentral.com wrote: Also, there are some bits of code in both Sugar and the activities that assume to be running on Fedora, or even on an XO, and those need cleaning. Be nice to know about these so we can fix them. thx -- Rubén Rodríguez Activity Central: http://activitycentral.com Facebook: https://activitycentral.com/facebook Google+: https://activitycentral.com/googleplus Twitter: https://activitycentral.com/twitter ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
On Tue, Oct 08, 2013 at 02:00:06AM +0200, Ruben Rodríguez wrote: 2013/10/8 Walter Bender walter.ben...@gmail.com: Be nice to know about these so we can fix them. Sure thing! We just finished with the first leg of the project and the resultant image is getting tested now, so soon I'll start sending patches. There are usually small things, like scripts written in bash (ubuntu uses dash), checking for distro specific files or paths, and the like. I agree, the bash vs dash issue is a small thing, it may be simpler to add bash as a dependency for Sugar. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Activity Central's Sugar related priorities.
On Mon, 2013-10-07 at 19:48 -0400, Walter Bender wrote: On Mon, Oct 7, 2013 at 7:45 PM, Ruben Rodríguez ru...@activitycentral.com wrote: Also, there are some bits of code in both Sugar and the activities that assume to be running on Fedora, or even on an XO, and those need cleaning. Be nice to know about these so we can fix them. You can start by looking for olpc specific paths that are hard-coded in places, here is a starting point: https://github.com/sugarlabs/sugar/blob/master/extensions/cpsection/power/model.py https://github.com/sugarlabs/sugar/blob/master/extensions/cpsection/aboutcomputer/model.py https://github.com/sugarlabs/sugar/blob/master/src/jarabe/controlpanel/gui.py Jerry thx -- Rubén Rodríguez Activity Central: http://activitycentral.com Facebook: https://activitycentral.com/facebook Google+: https://activitycentral.com/googleplus Twitter: https://activitycentral.com/twitter ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] Server-devel Digest, Vol 78, Issue 8
Hi, It is important to download content to the XO so that children can access them offline. This is not a technical problem. In the Karma Learning System, this is done using cgi-scripts which access the school server using sftp. Tony On 10/07/2013 12:00 PM, server-devel-requ...@lists.laptop.org wrote: Send Server-devel mailing list submissions to server-devel@lists.laptop.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.laptop.org/listinfo/server-devel or, via email, send a message with subject or body 'help' to server-devel-requ...@lists.laptop.org You can reach the person managing the list at server-devel-ow...@lists.laptop.org When replying, please edit your Subject line so it is more specific than Re: Contents of Server-devel digest... Today's Topics: 1. The concept of pushing content to clients (Anna) 2. Re: [XSCE] The concept of pushing content to clients (James Cameron) -- Message: 1 Date: Sun, 6 Oct 2013 21:31:09 -0500 From: Anna ascho...@gmail.com To: xsce-devel xsce-de...@googlegroups.com, Server Devel server-devel@lists.laptop.org Subject: [Server-devel] The concept of pushing content to clients Message-ID: cafm0qr2mea9wut1qxkubktnux8okrzrf4dg2tzzw9q94aaj...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 I got my Mom a refurb Kindle for $50 for her birthday. This past Thursday, she visited me for a few hours and we did a bit of training over takeout from Dreamland BBQ. What in the world does that have to do with the XO/DXS/XSCE ecosystem, you might be asking? For one, there's registration. Mom entered her Amazon user/pass into the Kindle. Then it was registered and she could see the Kindle when she looked at her Amazon account from her laptop. After registration, I asked her to go into her Amazon account to put my email address and the Tinderizer (I'll explain later) email address into the approved email list. That's so you can send things to mom@kindle.comfrom an approved email address and it'll just magically show up on her Kindle. I installed Calibre on her Windows laptop, which luckily went well. She understood it was like iTunes for books. (Mom has an iPhone and an iPad, she knows iTunes.) Then I showed her some free ebook sites where she could get content, how to import the downloaded books into Calibre, and how to put that content onto the Kindle. Where Mom was really fascinated was how you can push content onto the Kindle. If you don't have a Kindle, here's how it works (remember Mom put my email address into the approved list): 1. I find something interesting that Mom might like to read 2. I email m...@kindle.com that content in a .txt file attachment and simply put the word convert in the subject 3. Mom connects her Kindle to wifi and it automagically downloads the content Now, Mom is a huge fan of the NYT, she actually pays money to subscribe. I set her up with http://tinderizer.com like I use. Sometimes the NYT has very long articles that I'd like to read later on the e-ink Kindle. Tinderizer is a bookmarklet that, once you set it up (and setup is very simple), it's one click to push it to the Kindle. Once the Kindle is connected to wifi, that content just magically shows up on the device. If I know I'm going to be offline for a while, or just want to sit out on the porch in the sunlight, I'll browse for articles to push to the Kindle to read later. Instapaper is another option I've heard good things about, but it doesn't sound as simple. In my case, reading thoughtful, longform articles on my computer screen is sometimes difficult, so I quite prefer them on the Kindle's eink screen. And reading offline minimizes distractions. I know you're still wondering, what does this have to do with the XO/DXS/XSCE ecosystem! The concept of pushing content to client devices, which then automagically shows up with no effort from the end user. And it's not a link, it's the full content, so the user only needs to have a connection for a few minutes while the queued up content is pushed. Many folks might think Amazon is evil or whatever, but their content delivery system is notable and somewhat revolutionary as far as end users are concerned. Also, take note of this Kindle based project: http://www.worldreader.org/ As we're going into XSCE 0.5 and thinking about value added stuff, lemme just throw this concept in. Anna Schoolfield Birmingham -- next part -- An HTML attachment was scrubbed... URL: http://lists.laptop.org/pipermail/server-devel/attachments/20131006/07817ace/attachment-0001.html -- Message: 2 Date: Mon, 7 Oct 2013 14:03:53 +1100 From: James Cameron qu...@laptop.org To: xsce-de...@googlegroups.com Cc: Server Devel server-devel@lists.laptop.org Subject: Re: [Server-devel] [XSCE] The concept of pushing
[Server-devel] Reminder: XSCE IRC scrum tomorrow (8th October), 1600 UTC / 1200 EDT on #schoolserver/irc.freenode.net
Hi fellow server-hackers! We will be having our fifth IRC scrum meeting tomorrow 8th October on 1600 UTC / 1200 EDT at the #schoolserver channel (irc.freenode.net). The meeting will be logged by a supybot instance. Please start filling in your points to discuss in the rolling agenda document https://docs.google.com/document/d/1o6QtzLb6e58YKWqMf_junux2XyBRLFm31un8YLcYslg/edit Logs for the last meeting held on 1st October are here: https://sugardextrose.org/issues/4739 Cheers, Anish ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] Fwd: XS-CE Setup Issue
Hi, I got this email for an error log of a xsce-0.4, 64 bit installation. Any ideas? (I've asked the person concerned to join server-devel, so he can ask questions directly in the future). Best, Anish -- Forwarded message -- From: John Lillis johnmichael...@gmail.com Date: Fri, Oct 4, 2013 at 12:09 PM Subject: XS-CE Setup Issue To: Anish Mangal an...@activitycentral.com Hey Anish, I am trying to setup a small testing server for XS-CE 0.4, but I'm getting an error after running xs-setup. I am using Fedora 18 XFCE 64-bit within a VM. The error can be seen here: http://pastebin.com/0H2BNAk7. Thanks in advance, -- - John ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Fwd: XS-CE Setup Issue
On Mon, 2013-10-07 at 12:45 -0700, Anish Mangal wrote: Hi, I got this email for an error log of a xsce-0.4, 64 bit installation. Any ideas? (I've asked the person concerned to join server-devel, so he can ask questions directly in the future). Best, Anish -- Forwarded message -- From: John Lillis johnmichael...@gmail.com Date: Fri, Oct 4, 2013 at 12:09 PM Subject: XS-CE Setup Issue To: Anish Mangal an...@activitycentral.com Hey Anish, I am trying to setup a small testing server for XS-CE 0.4, but I'm getting an error after running xs-setup. I am using Fedora 18 XFCE 64-bit within a VM. The error can be seen here: http://pastebin.com/0H2BNAk7. Thanks in advance, ./startup.sh: line 233: [: sysadmin:x:1000:1000:System: unary operator expected chown: invalid user: ‘admin:admin’ line 233: # make a non privileged user, and give her remote access if [ ! `grep $DEFAULTUSER /etc/passwd` ]; then adduser $DEFAULTUSER echo $DEFAULTPASSWORD | passwd $DEFAULTUSER --stdin The code needs to be re-done to prevent a string being returned when the test is expecting a number to be returned. This doesn't address the fact that you can have a 'sysadmin' user and a 'admin' user at the same time. Maybe a better test would be to see if the 'admin' user has a home directory created already before creating the 'admin' user account. Jerry -- - John ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] XSCE | Proposing a quick turnaround 0.4.5 release
Since 0.4 was just released, it is a good moment to talk about future development efforts. I spent this weekend thinking about the progress we have made through this release, not just in terms of development effort, but growth as a community. What follows in this email below is a set of ideas and things to do and a proposal for a quick turnaround 0.4.5 release. I have observed the community grow in numbers by a quite a bit from the time we released 0.3. I believe we need to adopt new methods to allow every member become productive in their own space, while building foundations for equitable exchange of ideas consistent with the free software/open source way. = In terms of new features = * Many folks have suggested quite a number of valuable features for the 0.5 iteration [1], but I believe it will be easier to get to that goal if we switch to ansible. George has also supported this proposal. If the community at large decides that it is a sane idea to port to ansible, doing it first makes sense. I have created a (WIP) feature page for the same[2]. A lot of the ansible port has already been done under the DXS project, so it should ideally be a matter of some coding and a lot of testing. = In terms of development process shifts = * I propose we start following a feature proposal and selection process similar to upstream sugar (or what it used to be). Basically, the person or group proposing the feature creates a feature page following a template [3], which contains all the necessary details to make a go-no-go decision. Then it is discussed in a mailing list and if need be, in an IRC meeting. * Lets start using the bugtracker more (and formally so) [4]. A bugtracker can be a very valuable resource for new developers wanting to contribute and looking for things to do, and for keeping track of project development progress. = Volunteers for owning and maintaining different aspects of the project = Some examples could be * FAQ * Wiki as a whole * User-documentation * Project development manager * Coordinating with interested deployments * Supported hardware platforms == More visibility to community effort== * Shift to github. I strongly believe that we need to shift our codebase to github. I'm saying that even though the code is currently hosted on AC infrastructure. The biggest benefit of moving to github would be much better code visibility. It will make it easier for new developers to join in the development process. We switched dextrose server to github about a month and a bit ago, and will never look back. * Post notification of everything merged to the repository on IRC channel. * Post notification of everything merged to the repository on the mailing list. Just like code, the wiki also needs a lot of love, and there may be many contributors willing to pitch in, so I propose that. * Post notification of every wiki change to the IRC channel. * Post notification of every wiki change to the mailing list. = Crazy ideas = * Have a forum. A place where QA's can be asked and answered in human-understandable formats. (thought: perhaps look at how large we are as a community and then decide). [1] https://docs.google.com/document/d/1FVUFl6vry8u9b_lNSXvcWKN6hgVB-7Je4aTBpvq0QVg/edit [2] http://wiki.laptop.org/go/XS_Community_Edition/feature/port-to-ansible [3] http://wiki.laptop.org/go/XS_Community_Edition/feature/template [4] https://sugardextrose.org/projects/xsce ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Server-devel Digest, Vol 78, Issue 8
First, I'm not sure what Anna is describing is push based in a pure technical sense. The client receiving files must either be always online or poll some central server to see if there is anything to be downloaded. To the end user, it's push based, but technically, it's still polling by the client to see if there is something there and then pulling stuff from the server I can think of one use case of this, perhaps there are more... I'm not sure.. The ability for a teacher to reliably send files to children's laptops has long been requested by a few deployments. In dextrose, we have a pull based solution, where a teacher copies the file on a webdav share, which a kid can access from their journal itself, and download. See: http://wiki.sugarlabs.org/go/Features/Transfer_to_many_options This is not push based, and the teacher doesn't _know_ if every kid has downloaded the file he/she wanted, but works reasonably well. Perhaps there are other scenarios where push based approach might be useful, but it also might be tricky considering the environments we work in. On Mon, Oct 7, 2013 at 10:54 AM, Tony Anderson tony_ander...@usa.net wrote: Hi, It is important to download content to the XO so that children can access them offline. This is not a technical problem. In the Karma Learning System, this is done using cgi-scripts which access the school server using sftp. Tony On 10/07/2013 12:00 PM, server-devel-requ...@lists.laptop.org wrote: Send Server-devel mailing list submissions to server-devel@lists.laptop.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.laptop.org/listinfo/server-devel or, via email, send a message with subject or body 'help' to server-devel-requ...@lists.laptop.org You can reach the person managing the list at server-devel-ow...@lists.laptop.org When replying, please edit your Subject line so it is more specific than Re: Contents of Server-devel digest... Today's Topics: 1. The concept of pushing content to clients (Anna) 2. Re: [XSCE] The concept of pushing content to clients (James Cameron) -- Message: 1 Date: Sun, 6 Oct 2013 21:31:09 -0500 From: Anna ascho...@gmail.com To: xsce-devel xsce-de...@googlegroups.com, Server Devel server-devel@lists.laptop.org Subject: [Server-devel] The concept of pushing content to clients Message-ID: cafm0qr2mea9wut1qxkubktnux8okrzrf4dg2tzzw9q94aaj...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 I got my Mom a refurb Kindle for $50 for her birthday. This past Thursday, she visited me for a few hours and we did a bit of training over takeout from Dreamland BBQ. What in the world does that have to do with the XO/DXS/XSCE ecosystem, you might be asking? For one, there's registration. Mom entered her Amazon user/pass into the Kindle. Then it was registered and she could see the Kindle when she looked at her Amazon account from her laptop. After registration, I asked her to go into her Amazon account to put my email address and the Tinderizer (I'll explain later) email address into the approved email list. That's so you can send things to mom@kindle.comfrom an approved email address and it'll just magically show up on her Kindle. I installed Calibre on her Windows laptop, which luckily went well. She understood it was like iTunes for books. (Mom has an iPhone and an iPad, she knows iTunes.) Then I showed her some free ebook sites where she could get content, how to import the downloaded books into Calibre, and how to put that content onto the Kindle. Where Mom was really fascinated was how you can push content onto the Kindle. If you don't have a Kindle, here's how it works (remember Mom put my email address into the approved list): 1. I find something interesting that Mom might like to read 2. I email m...@kindle.com that content in a .txt file attachment and simply put the word convert in the subject 3. Mom connects her Kindle to wifi and it automagically downloads the content Now, Mom is a huge fan of the NYT, she actually pays money to subscribe. I set her up with http://tinderizer.com like I use. Sometimes the NYT has very long articles that I'd like to read later on the e-ink Kindle. Tinderizer is a bookmarklet that, once you set it up (and setup is very simple), it's one click to push it to the Kindle. Once the Kindle is connected to wifi, that content just magically shows up on the device. If I know I'm going to be offline for a while, or just want to sit out on the porch in the sunlight, I'll browse for articles to push to the Kindle to read later. Instapaper is another option I've heard good things about, but it doesn't sound as simple. In my case, reading thoughtful, longform articles on my computer screen is sometimes difficult, so I quite prefer them on the
Re: [Server-devel] XSCE | Proposing a quick turnaround 0.4.5 release
Don't number it 0.4.5, instead number it 0.5, and push any plans you had for 0.5 out to 0.6. The sooner you get to 1.0 the more acceptable the version number will become. 0.4, based on the descriptions I see, is already 1.0 fodder. Ansible sounds fine, but you haven't said what it is for; no apparent benefit to the end user. If it is an internal reorganisation for developers, won't you need to find which developers are in favour, and will the publication of a feature page expose those developers or not? If it is for a web user interface for end-users, are there others you might use instead, such as Webmin? What process led to the recommendation to use Ansible? Which developers will find it hard to migrate their neural maps to Ansible? I don't see any sign of failure to scale with the existing developers, so I'm surprised you would want to go all formal with feature pages and an approval based development process. The community you have now is still young, and probably hasn't even finished settling in to the processes you already have. -- James Cameron http://quozl.linux.org.au/ ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XSCE | Proposing a quick turnaround 0.4.5 release
On Mon, Oct 7, 2013 at 9:51 PM, James Cameron qu...@laptop.org wrote: Don't number it 0.4.5, instead number it 0.5, and push any plans you had for 0.5 out to 0.6. The sooner you get to 1.0 the more acceptable the version number will become. 0.4, based on the descriptions I see, is already 1.0 fodder. I am okay with whatever version numbering scheme that is acceptable to the majority. Ansible sounds fine, but you haven't said what it is for; no apparent benefit to the end user. If it is an internal reorganisation for developers, won't you need to find which developers are in favour, and will the publication of a feature page expose those developers or not? If it is for a web user interface for end-users, are there others you might use instead, such as Webmin? What process led to the recommendation to use Ansible? Which developers will find it hard to migrate their neural maps to Ansible? =Short answer= http://lists.laptop.org/pipermail/server-devel/2013-September/006755.html =Longer answer= Perhaps it is best given by Miguel or Santi. (cc'ed) It is an internal reorganization for developers, with no impact for the end user (the end user being a teacher or a student). It is meant to make the XS platform easier to: * Add features to as a platform * Deploy at small and large scale, online or offline * Make the XSCE cross platform * Make the XSCE more approachable to a potential developer. One of the great things about Sugar is that it is written in python, which is so much easier to learn and get started with. I hope ansible has the same effect. This is not the first time Ansible has been discussed in the context of XSCE. Here are some previous discussions * http://lists.laptop.org/pipermail/server-devel/2013-September/006767.html * From another email in the non-archived xsce list: About ansible, it a powerful tool, with lower learning curve than puppet, and can achieve almost the same results imho. In terms of experience with ansible, we have so far: * Updated the XSCE software offline thru ansible in Bhagmalpur once, went flawlessly. * Based Dextrose Server on ansible. Code: https://github.com/activitycentral/dxs Still, you are probably going to get better answers to specific technical queries from Santi or Miguel. The feature page linked in my email before is still an early draft. I don't see any sign of failure to scale with the existing developers, so I'm surprised you would want to go all formal with feature pages and an approval based development process. The community you have now is still young, and probably hasn't even finished settling in to the processes you already have. Incidentally the idea behind a feature page is to answer exactly the kind of questions you asked about ansible your email :-) The other reason I proposed it was that we seem to have accumulated a lot of great ideas that can go into 0.5 (or 0.6), and we need to start moving from fuzzyness to form so a decision about working on them can be made. http://producingoss.com/en/producingoss.html#bikeshed I am okay with any process that accomplishes the same. In the last two IRC meetings, we have thrown about many ideas, but I would want more resolution when discussing them :) For a bit of background, the 0.2 featureset was decided in the toronto sprint where ideas were written on post-it notes, pasted on a piece of paper and discussed by everyone present. http://www.flickr.com/photos/tiayiti/8475348302/sizes/c/in/photostream/ About some of the other ideas, like posting notifications to mailing lists, I believe it is not a process change, but simply an effort to make things more transparent. - - - - - In sum, all these are just ideas to make XSCE a more fun place. I would love to see them refined/adopted/rejected after due discussion. :-) -- James Cameron http://quozl.linux.org.au/ ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
