[Sugar-devel] Moving On.
The Short Version: As many of you might have noticed, my activities within Sugar Labs have been fading lately. I'd like to take the only responsible step and hand my responsibilities off. The Long Version: I didn't expect to see myself writing this email. I'm currently a student at Olin working really hard to make it through finals and at the same time fighting RSI and dealing with other things ( http://sdziallas.com/blog/sebastian/2010/11/a-kid-in-the-candy-store.html). But I also feel that I've been dragging this e-mail out way too long. I'm sorry. Nevertheless, I'm proud of what we accomplished over the past years. I have great memories from the initial release of Sugar on a Stick at LinuxTag ( http://sdziallas.com/blog/sebastian/2009/06/strawberries-for-everyone-now.html) and I still smile when I think of how we recovered from the ridiculous unsustainability of the second release ( http://opensource.com/education/09/12/tasty-blueberry) and eventually even made the third release as a team together ( http://sdziallas.com/blog/sebastian/2010/05/mirabelles-they-are-there.html). Looking back, I found myself skimming old wiki pages and blog posts ( http://blog.melchua.com/2010/06/04/the-history-of-the-soas-mirabelle-release-learning-from-the-past/ ). I'm particularly thankful for the experiences I had and the people I met. However, I feel that it's time to move on. I'll be unsubscribing from a couple of mailing lists, but I'll continue to work on bridging open source and education on various levels and I'm always open to direct email. Just a ping away. Email this address. For Sugar on a Stick, Peter Robinson has alreading been leading the effort up to the latest Mango Lassi release of Sugar on a Stick and done an incredible work over the past year, leaving me confident that everything was taken care of when I had to focus on my studies (both in Germany and the US). I know from personal experience that taking on this work isn't an easy task and I don't want to assume that you're just going to continue doing it infinitely. It is your call. But you've done a great job. Thanks, Peter! Good luck Sugar Labs. You've come a long way. Don't lose track of your mission. -s ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Calculate bug, help!
On Wed, Jul 21, 2010 at 4:54 AM, Gary Martin garycmar...@googlemail.com wrote: Hi Reinier, On 20 Jul 2010, at 00:45, Reinier Heeres wrote: Hi Gary, I agree that the AstParser class is a bit scary, but I still believe it's a good ingredient for Calculate: it allows us to do symbolic evaluation of functions. This brings us the features of plotting graphs and using not-completely-resolved functions in later calculations. This would be quite a bit harder otherwise (not to mention that the previous parser was a hideous piece of code). Understood, well I think I do, just glad the AstParser scariness has a good reason for being there :) Anyway, I have attached a patch to fix the bug you mentioned. If you can have a look whether you agree I'll push it asap. Tested here, works great and also fixes the bug in the sci/exp button as well :)) I'm cursing myself a little as I had been playing around with a helper function in functions.py without luck, but hadn't considered what was really needed was a helper class. I'm trying to get back to writing some sugar activity code in the coming time, so I hope to get a few more Calculate bugs out of the way as well. That would be fab! One thing to note is that v31 in git all this time with the new toolbar support has never been officially released. My plan was to try and hit a few low hanging bugs in trac (failed that one) and get a release out the door, perhaps just in time to have it added to the next Soas release (feature freeze is next week and I'd need to convince someone to package it for fedora, at least there are no binary blobs to worry about). Does that fit in with your schedule? I could do the release bit, ASLO, update wikis, upload the source, if you are pushed for time this week? For the record, Calculate is already part of Fedora and if an activity author is interested in having it in shape for a SoaS release, we'd certainly be happy to just push an update for that. So this shouldn't be an issue. :) --Sebastian Regards, --Gary Cheers, Reinier On Mon, Jul 19, 2010 at 6:11 AM, Gary C Martin garycmar...@googlemail.com wrote: Hi Reinier, Help! :) I've burnt a week of misc free time trying to untangle this deg/rad bug, but it's a nightmare for me and I seem to have got nowhere. Any hints much appreciated: http://bugs.sugarlabs.org/ticket/ After much poking I discovered you implemented some type of custom plugin system (in the rather scary AstParser class) for the 'functions.py' and 'constants.py' code, which seems to do some magic import tricks that seem to prevent obvious access to accessing the 'functions.py' variable _angle_scaling from the outside, and/or blocking the 'functions.py' plugin code from accessing that value from the outside. The toolbar code changes the angle_scaling property in the MathLib class, but that value is never used by the actual imported AstParser function calls, and I've found no way to access the actuall deg/rad scaling value to change it from the outside. Thanks for any hints. Regards, --Gary -- Reinier Heeres Tel: +31 6 10852639 fix_angle_scaling.diff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Testing request] Browse-webkit
On Tue, Jul 20, 2010 at 3:36 PM, Bernie Innocenti ber...@codewiz.org wrote: El Tue, 20-07-2010 a las 03:07 +0100, Lucian Branescu escribió: rgs and myself have ported Browse to pywebkitgtk with all features and we could use some testing. You can get it from here http://git.sugarlabs.org/projects/browse/repos/mainline/trees/webkit It requires pywebkitgtk 1.1.6 and webkitgtk 1.2.*. Can you provide an installable xo bundle? Yup, I'd be interested in a release, too. :) Can you upload one to people.sl.o? Awesome work! --Sebastian Also, note that pywebkitgtk 1.1.6 in fedora (11 and 12 have been observed so far) segfaults. So either wait for the fix or use another distro in a VM. I've just pushed an updated pywebkitgtk-1.1.7 rpm to the f11-0.88 repository. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Call for Testers: LiveUSB Creator on other Distributions
Hi all, I'd like us to get a coherent way in terms of user interfaces for creating Sugar on a Stick on as many distributions as possible. I do have a first iteration of such a release using Fedora's LiveUSB Creator ready and need some testers with - preferably different - distributions. There are a couple of things that need to be checked before this is ready for mass-consumption, but if you're interested in giving this a try, please drop me a line and note the distributions you're running on real machines on which you could actually test this. Thanks, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Sugar on a Stick Weekly Meeting Logs (2010/07/19)
Here are the minutes (follow the link at the bottom for the logs): http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100719_1506.html Bernie, what's the state of the VM we had been talking about for Mel and me (I'd really like to have a real bot there). Points raised: * Raffael asked about the state of this feature: http://wiki.sugarlabs.org/go/Features/Feature_intro_language_keyboard_options * We had a convo with Gary and others about the entry barrier for new activity developers in terms of making releases. * The feature freeze is coming close. Next week is the last chance to submit new features. We'd really like to see more feedback from activity authors interested in getting activities in SoaS. Thanks everyone for attending, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] [DESIGN] Restart
On Fri, Jul 16, 2010 at 9:42 PM, Bernie Innocenti ber...@codewiz.org wrote: El Fri, 16-07-2010 a las 09:37 -0400, Frederick Grose escribió: Anything else we would like feedback on? Please also consider http://bugs.sugarlabs.org/ticket/503. I don't know... if we drop the Restart button in the menu, do we still need to take any action? Also, where's the proposed SVG icon for Restart X? In SoaS, we used to be able to drop into Gnome by logging out. With the new, dual environment builds in, we should mimic that in SoaS. Couldn't SoaS use a variant of olpc-switch-desktop? I think it works well. I think the last time I looked into this, olpc-switch-desktop depended on olpc-dm, which comes with the entire olpc-utils package. Hence, we're currently going with gdm. :) --Sebastian It may help permit user switching without rebooting the workstation--Learners would swap sticks to access their Journal. We have a simple journal patch to show the Documents folder on the volumes toolbar. It covers 80% of the Gnome/Sugar interoperability needs adding just 20 lines of straightforward code to Sugar. Another possibility was developing a fuse interface to the datastore, but I think it brings too much complexity and fragility. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ SoaS mailing list s...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [GSoC] [Patch] Sugar Smolt Control Panel Integration
Sorry that it took me a bit to reply. Catching up on email backlog once again. I dropped a couple of replies inline. :) On Mon, Jun 28, 2010 at 11:57 AM, Sascha Silbe sascha-ml-ui-sugar-de...@silbe.org wrote: Excerpts from Sebastian Dziallas's message of Sun Jun 27 21:07:11 +0200 2010: I've been working on an integration of Smolt (https://fedorahosted.org/smolt/) into Sugar as part of my GSoC. The Nice! The repository lives here (http://git.sugarlabs.org/projects/sugar/repos/sugar-smolt) and A quick look doesn't show any major mistakes (take that as praise ;) ). There are a few minor style issues; pylint + pep8 might catch some of the easy ones (like EOL spaces and naming conventions for constants). Oh, okay! I'll run that... Some questions I had: - Why do you recommend to delete the profile (including UUID) after submission? Isn't one of the purposes of smolt support to be able to help individual users with hardware trouble (which would require knowing the UUID of the user)? It's not the we actually *recommend* to the user to delete the profile afterwards. It's just that they should have the option to delete it, if they want to. But yes, indeed: We'd need to know the URL to read the profile. - Is the privacy policy really large enough that we need to destroy the widget even while the section view is active? (If section views are kept in memory even after they got closed, that should be fixed rather than worked around). Uh, I looked at how the GPL was read in the about-my-computer screen and that's how they did it there. The privacy policy might be a little shorter, though. Suggestions: - Only show the section if smolt is actually installed (not all distros have it). Might need support on the Sugar side as this check is currently hardcoded for the keyboard and power sections. The latter one even checks for /ofw, but that's stuff for the OHM support thread, not this one. I put that in the __init__.py file: the control panel section only shows up when the smolt file executing the submission is present. - Don't store the handler ids of the GTK callbacks if you don't use them. We don't need to keep a reference in our code to protect them from garbage collection. - Maybe deactivate the Delete button if no profile is present? (Submitting a second time can be useful so that button should always be active). That should be doable, yeah. :) - Assuming smoltSendProfile is synchronous (i.e. doesn't finish until sending the profile has either been finished successfully or failed), you should run it in the background. The Sugar shell is currently a single process, so running synchronously will block everything. Yup yup, I'll look into that! - Check for smolt errors (rc, stderr) and relay them to the user. I marked the ticket as r?, so a review would be appreciated, too. Sending the patch to the mailing list makes it easier to review, so you'll get more feedback that way. My config is rather complicated because of the email address scheme I use, but maybe it shows you how to automate everything so sending the patch to the ML is as simple as typing a single git command. For patches that might need to be revised before they can be committed I use TopGit. git rebase -i is nice as well, but only works if you don't publish your repository. Thanks for all the feedback and hints, it's really appreciated! :) --Sebastian This is my ~/.gitconfig : [user] email = sascha-...@silbe.org name = Sascha Silbe [url gitori...@git.sugarlabs.org:] pushInsteadOf = git://git.sugarlabs.org/ [alias] send-to-ml-multi = !git send-email -s --annotate --summary --cover-letter --add-header=\Reply-To: Sascha Silbe sascha-ml-reply-to-$(python -c 'import time; t=time.gmtime(); print \%d-%d\ % (t.tm_year, t.tm_mon//4+1)')@silbe.org\ send-to-ml-single = !git send-email -s -p --stat --add-header=\Reply-To: Sascha Silbe sascha-ml-reply-to-$(python -c 'import time; t=time.gmtime(); print \%d-%d\ % (t.tm_year, t.tm_mon//4+1)')@silbe.org\ tg-send-to-ml-single = !tg mail -s \-p --stat --add-header=\\\Reply-To: Sascha Silbe sascha-ml-reply-to-$(python -c 'import time; t=time.gmtime(); print \%d-%d\ % (t.tm_year, t.tm_mon//4+1)')@silbe.org [sendemail] from = Sascha Silbe sascha-...@silbe.org chainreplyto = false signedoffcc = false suppressfrom = true confirm = always [color] diff = auto And this is (part of) my .git/config for sugar: [format] headers = Mail-Followup-To: sugar-devel@lists.sugarlabs.org [sendemail] to = sugar-devel sugar-devel@lists.sugarlabs.org envelopesender = sascha-ml-ui-sugar-de...@silbe.org Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org
[Sugar-devel] [GSoC] [Patch] Sugar Smolt Control Panel Integration
I've been working on an integration of Smolt (https://fedorahosted.org/smolt/) into Sugar as part of my GSoC. The purpose of this is to help us gather information about the hardware Sugar is running on, as well as to help users filing bug reports to simplify the process of providing said information to developers. The repository lives here (http://git.sugarlabs.org/projects/sugar/repos/sugar-smolt) and there's a ticket filed for review here (http://bugs.sugarlabs.org/ticket/949). It still needs a shiny icon, though, since we're using the not-very-sugar-like smolt icon right now - maybe somebody could help with that? I marked the ticket as r?, so a review would be appreciated, too. --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] Read in SoaS with Fedora 13
On Thu, Jun 24, 2010 at 2:18 AM, Thomas C Gilliard satel...@bendbroadband.com wrote: I just made a 4 GB USB with persistence from soas-i386-20100623.03.iso In testing: Read 86, it still fails to start log showed unable to find/open evince [...] Read does not work because the way it interacts with evince has changed on the evince side. Hence, Read would have to be adjusted for working again (which is a pretty critical thing, I guess). I read, though, that David Farning's ActivityCentral was going to provide incentives for people to work on that? (I'm just walking through my email backlog right now, so please correct me if I'm wrong.) There is a ticket on that in trac: http://bugs.sugarlabs.org/ticket/1900 Tried to open a e-book in sugar-journal evince could NOT ACCESS JOURNAL. Yes, this is the case because evince itself is not a sugar activity. --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] GCompris problems on SoaS
I'm moving this from IAEP to sugar-devel. Aleksey, do you have an idea what's going on here? I haven't tried GCompris in SoaS lately, but could this be 0sugar-related? --Sebastian On Thu, Jun 17, 2010 at 10:49 PM, Werner Westermann werne...@gmail.com wrote: Hello, regards from Chile. Working with a teacher, she wanted to explore GCompris activities loading them in her SoaS, in the context of our first pilot deployment in K-3. But there's a problem with launching those activities with this message: Cannot find cached 0sugar-launch implementation. It's confusing the situation, because she said the in the first instance the activities did launch, but now they won't. I tried it out on my SoaS and had no trouble with one GCompris activity (weigthscale), but I downloaded 2 of the and had the same problem. Can this problem be solved in any way on the SoaS? Can we rely on using GCompris activities in a deployment context? Thanks for your suggestions, werner http://cl.sugarlabs.org ___ IAEP -- It's An Education Project (not a laptop project!) i...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Attention Activity Developers: SoaS Activity Inclusion Criteria
Hi all, at today's SoaS meeting [1], we agreed on applying the SoaS Activity Inclusion Criteria [2] as outlined in the wiki to the activity selection for the upcoming release of SoaS v.4. We'd like to encourage you to work towards meeting these goals and to submit your proposals for activities and further features following the feature process [3] according to the release schedule [4]. The final deadline to have features *approved* (please submit your proposals well in advance) is July 27. We're especially lead to this step to ensure to continued stability of future Sugar on a Stick releases and look forward to working with you! Please email the SoaS list or our release team with any concerns. --Sebastian Dziallas [1] http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100607_1510.html [2] http://wiki.sugarlabs.org/go/SoaS_Activity_Criteria [3] http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Feature_process [4] http://wiki.sugarlabs.org/go/Sugar_on_a_Stick#Release_schedule ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] [Marketing] Soliciting SoaS v.4 Codename Colour Suggestions
Thanks everybody for the proposals thus far. I've converted them into a table for a better overview [1]. Please keep in mind that Sugar has a defined color palette for its logo, too [2]. --Sebastian [1] http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_meetings#Agenda [2] http://wiki.sugarlabs.org/go/Marketing_Team/Logo#Color_Palette On Fri, Jun 4, 2010 at 11:41 PM, Outofindia outofin...@gmail.com wrote: Jambul also known as Jamun in India and by others name in different parts of the world. http://en.wikipedia.org/wiki/Jambul A medicinal fruit/plant/tree. Supposed to be a rich source of iron, vitamins A and C Besides the fruit, every part of the tree too is used. The bark, the seed (dried and powdered) and even ash from the burnt leaves for gums. The wood is used to make furniture! The colour crimson. http://www.agriculturalproductsindia.com/fruits/fruits-jamun.html Regards Harriet On Fri, Jun 4, 2010 at 12:33 PM, Sebastian Dziallas sebast...@when.com wrote: Hi Sean, On Fri, Jun 4, 2010 at 5:32 PM, Sean DALY sdaly...@gmail.com wrote: Sebastian, I guess you want to drop the name we had chosen together previously, Cloudberry? If you remember we had wanted to underline collaboration and connectivity, and decided to postpone that name when we realized that it was too ambitious for this release. this is by no means the intention of this email. You will note that this email is also sent to the marketing list, so this is not aimed at excluded marketing, but rather at getting the conversation started. We're simply encouraging brainstorming here so that we don't get stuck later there and have a prominent way of calling the upcoming next version early in the release cycle (Fedora has already chosen its codename for F14, too). I don't recall us already having chosen Cloudberry. It was the previous codename for v.3, but as you say, we decided to go with Mirabelle instead since it could have caused confusion. I personally believe that it only makes sense to chose a name like Cloudberry if we're able to provide a sufficient amount of cloud-related features, since we might get otherwise beaten up over it. This is a marketing discussion and should really be in the marketing meeting. Sugar on a Stick is a pillar of our marketing strategy and the name needs to fit with our strategy. That said, I wouldn't want to spoil anyone's fun choosing ice cream flavors. It could be nice to pick a non-berry flavor too as Peter and others have said in the past. I think this is debatable and I'm certainly not objecting to having this conversation in the marketing meeting, too. However, this also concerns the project itself, so I think it's also fair to raise it in the Sugar on a Stick meeting. --Sebastian Sean On Thu, Jun 3, 2010 at 8:31 PM, Sebastian Dziallas sebast...@when.com wrote: We'd like to kick off the process for the upcoming Sugar on a Stick v.4 already, while gearing up for the SoaS PR at LinuxTag, too. And so we're looking forward to your ideas and suggestions on the codename and colour selections for the next release iteration. These will be discussed at the next meeting, which is scheduled to take place on Monday, June 7 on 1900 UTC in #sugar-meeting. Thanks, --Sebastian ___ Marketing mailing list market...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/marketing ___ IAEP -- It's An Education Project (not a laptop project!) i...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Soliciting SoaS v.4 Codename Colour Suggestions
We'd like to kick off the process for the upcoming Sugar on a Stick v.4 already, while gearing up for the SoaS PR at LinuxTag, too. And so we're looking forward to your ideas and suggestions on the codename and colour selections for the next release iteration. These will be discussed at the next meeting, which is scheduled to take place on Monday, June 7 on 1900 UTC in #sugar-meeting. Thanks, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Read 86 failed to start in Mirabelle
On Sun, May 30, 2010 at 7:22 PM, samy boutayeb s.bouta...@free.fr wrote: Hi, I tried to use the Read activity (version 86) in Mirabelle (either running from within Virtualbox on a USB stick) and got the following error: Failed to start. However, the same activity (same version) do launch and opens a document correctly (e.g. a pdf or a djvu file) on a XO 1.5 with Sugar 0.84.16 (version 125). I'm sorry to report this as a known error. We only noticed this very late in the release cycle and got surprised by this. As it turns out, this is apparently due to major API changes in gnome-python-evince. There's a ticket open at bugs.sl.o: http://bugs.sugarlabs.org/ticket/1900 If anybody could help with the porting, I bet Sayamindu would appreciate it. --Sebastian Regards, Samy ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Announcing Sugar on a Stick v.3 (Mirabelle)
Mirabelles have arrived! (http://www.flickr.com/photos/enil/3892066169/) I am proud to announce the availability of Sugar on a Stick v.3, code-named Mirabelle. More information about Sugar on a Stick, including download and installation details, are available at http://spins.fedoraproject.org/soas/. Changes in Sugar on a Stick since the last release (v.2 Blueberry): Sugar version 0.88. The most recent release of the Sugar Learning Platform features support for 3G connections, increased accessibility, and better integration with our Activity Portal (http://activities.sugarlabs.org) allowing students and teachers to update their sticks with additional Activities. More information about the 0.88 release of Sugar is available at http://wiki.sugarlabs.org/go/0.88/Notes. Customize your own remix of Sugar on a Stick. You'll notice that v.3 Mirabelle has a smaller Activity selection than its predecessors, Blueberry and Strawberry. We realized we'll never be able to create an Activity selection suitable for all deployments - instead, we've chosen to include and support a core set of basic, teacher-tested Activities in the default image, and invite deployments to use this as a base on which to build a customized Activity selection for their classrooms. Instructions on how to do this are available at http://download.sugarlabs.org/soas/docs/customization-guide/. Sugar on a Stick is now a Fedora Spin. After two prior releases of being based on the Fedora distribution, Sugar on a Stick has recognized by the Fedora Project as an official Spin. This ties us more closely to Fedora's release cycle and gives us resources from their engineering and marketing teams, which extends the reach of Sugar on a Stick and makes the project itself more sustainable. In exchange, users of Fedora have access to an easily deployable implementation of the Sugar Platform; it's a great example of a mutually beneficial upstream - downstream relationship. The biggest difference in v.3 of Sugar on a Stick has been in its release processes and engineering sustainability; it's now much easier for new contributors to get involved. We continue to move towards our long-term vision of bringing stability and deployability to Sugar's personalized learning environment, and invite all interested parties to join us. If you'd like to contribute to the next version, due for release in early November, join us at our Contributors Portal at http://wiki.sugarlabs.org/go/Sugar_on_a_Stick. All types of contributions are welcome, from the technical to the pedagogical, and we're happy to teach what we know and learn what you have to share. Thank you especially to the Sugar on a Stick team and all the people involved for their awesome work on this release! Sebastian Dziallas Sugar on a Stick Project Lead ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] SOAS-3: Final Activity List - Attention needed!
On Mon, Apr 26, 2010 at 11:04 PM, Thomas C Gilliard satel...@bendbroadband.com wrote: Yes it has jabber.sugarlabs.org in Control Panel / Network It looks very much like this, which seems to be pretty much a blocker, yup: https://bugzilla.redhat.com/show_bug.cgi?id=585413 Tom Gilliard satellit Peter Robinson wrote: On Mon, Apr 26, 2010 at 9:09 PM, Thomas C Gilliard satel...@bendbroadband.com wrote: Peter; I know it is not an activity, but it affects all of them: Will the presence service get fixed in time for the release? All I am able to see is xmpp local on any of the f13 Composes of Soas log application has no entries No Jabber server access for collaboration. (Or are we waiting for tomeu to rework it for the next version) Is there a jabber server configured in the default config? I'm looking into the problem and its on my list. I'm hoping to get it fixed before the final release. Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [GSoC] Improved Sugar on a Stick Proposal
Hi folks, I have been busy lately and will continue to be for the next couple of weeks. However, summer possibility exploration happens, too. So. Here's a GSoC proposal. Comments appreciated! :) http://wiki.sugarlabs.org/go/Summer_of_Code/2010/Improved_Sugar_on_a_Stick Cheers! --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] What's going on with Sugar on a Stick?
Hi all, as you may have noticed, there are a couple of changes coming to Sugar on a Stick to keep the whole project sustainable. In the upcoming month, from March 28 (I'll be off starting Sunday night) to May 7, my ability to devote time to the project will cease. I have to prepare for my major A-level exams; more importantly, I have to secure a significant amount of funding in order to be able to attend college later this fall. (If you're interested in helping, see http://sdziallas.com/blog/sebastian/2010/03/sebastian-needs-100k.html for more details - any advice would be appreciated.) This does not affect the release date. Sugar on a Stick will be released as a spin through Fedora's release engineering process on May 11. We are bound to this date and will have a working release in time. The general release schedule including all relevant policies is available here [1]. Nightly builds are also available [2] (and will contain a fixed IRC activity within a couple of days, as soon as [3] has been pushed to stable). Activity authors are also advised that the final freeze date for package updates is April 27, so make sure to get fixes pushed well in advance to give package maintainers and the update system time to process. Peter Robinson has kindly agreed to act in case something is needed. Please make sure to post to the appropriate lists, though, so that everybody is in the loop. Finally, please file bugs at bugs.sugarlabs.org as explained in [4] to save all of us time. Thanks, --Sebastian [1] http://fedoraproject.org/wiki/Releases/13/Schedule [2] http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ [3] https://admin.fedoraproject.org/updates/sugar-xoirc-6-4.fc13 [4] http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick/Getting_Involved ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] SoaS change in engineering direction: activity questions
SoaS engineering just proposed a major change-in-direction for the upcoming (Mirabelle) release. See http://lists.sugarlabs.org/archive/soas/2010-March/000906.html and http://lists.sugarlabs.org/archive/marketing/2010-March/002727.html for more information - the short version is that instead of include all Activites by default, we're thinking of shipping very few (6) Activities by default - the ones that help users get further Activities and help - and driving them to ASLO to download Activities and engage directly with Activity creators (you!) instead. If you're an Activity maintainer and would really like to see your activity in SoaS, please holler and make sure to give us a heads-up. Also, testing that your activity actually works with the latest snapshot would be awesome, as it gives us some certainty that we aren't shipping broken stuff this late in the release schedule. Thanks, --Mel and Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Testing activities on latest daily SoaS builds
Art Hunkins wrote: I am unable to test my activities (Our Music, Our Music MC) on recent daily builds because Browse doesn't work, and other USB drives are not recognized. (The neighborhood view shows nothing except me.) These are my only ready ways of getting activities into the system. Browse has been fixed in the latest snapshots. At least I can confirm that in yesterday's build. Sorry for the inconvenience! I know that csound-python *is* installed, as *yum works*, and shows that csound-python is already up to date. Otherwise, after installing csound-python on the test day build, everything was OK, so I *presume* things should work. However, I'd really like to be *sure* the activities are completely 0.88-ready. Any suggestions? (I only have SoaS sticks to work with - no virtual machine.) It should be okay now. Let us know if there are more issues! :) --Sebastian Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ANNOUNCE] Sucrose 0.87.6 Tarballs Due
Art Hunkins wrote: Can we be certain that csound-python is included, please? Art Hunkins This is SoaS related, I'd say (and not for Sugar itself). As stated in a previous e-mail, I've pushed an appropriate commit earlier [1]. If you want to make sure, you can check the current kickstart file that's used for composing the nightly builds on the way to SoaS v3 here [2]. Finally, said nightly builds live here [3], so it can also be verified. Be advised that these nightly builds might be unstable, though. --Sebastian ...who thinks that Yes We Can would have been another possible reply. ;) [1] http://git.fedorahosted.org/git/spin-kickstarts?p=spin-kickstarts.git;a=commitdiff;h=945e62dd13dbd26d09147cb76ca10f08c89f7532 [2] http://git.fedorahosted.org/git/spin-kickstarts?p=spin-kickstarts.git;a=blob;f=fedora-livecd-soas.ks [3] http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ - Original Message - From: Simon Schampijersi...@schampijer.de To: Sugar-devSugar-devel@lists.sugarlabs.org Sent: Wednesday, February 24, 2010 12:20 PM Subject: [Sugar-devel] [ANNOUNCE] Sucrose 0.87.6 Tarballs Due Dear Sucrose Maintainers, please provide source tarballs for the Sucrose 0.87.6 unstable release [1] by the end of the first of March 2010 and announce them as explained at [2]. This will be our Beta release! So, clean up the Features, go over the review queue and fix bugs. Please remember the string freeze at this date, too. Thanks, Simon [1] http://wiki.sugarlabs.org/go/0.88/Roadmap#Schedule [2] http://sugarlabs.org/go/Development_Team/Release#Module_release ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Commonly Used SoaS and XO Sugar Distributions
Art Hunkins wrote: It would be most helpful to me to know whether SoaS v3 will be called Cloudberry or something else. This was the original plan, as far as I'm aware. However, the final release name will be determined through consideration of the various involved teams, such as the Marketing and the Development Team. Indeed, can I know the complete content of the fedora-release file? For the snapshots, it's currently just linking to Fedora, I guess. This is not final and we will work on that, too. --Sebastian Art Hunkins - Original Message - From: Sean DALYsdaly...@gmail.com To: Art Hunkinsabhun...@uncg.edu Cc:Sugar-devel@lists.sugarlabs.org Sent: Tuesday, February 23, 2010 9:39 AM Subject: Re: [Sugar-devel] Commonly Used SoaS and XO Sugar Distributions Art - SoaS v3 will be called Cloudberry. Note that Strawberry was v1 and Blueberry v2 Sean On Sun, Feb 21, 2010 at 9:19 PM, Art Hunkinsabhun...@uncg.edu wrote: Can someone please complete the following list of commonly used (by students) distributions of both SoaS and Sugar installed on the XO computers? XO-1 (Sugar 0.82) XO-1.5 (Fedora 11 for XO-1.5) SoaS Strawberry (Sugar 0.84) SoaS Blueberry (Sugar 0.86) Should Fedora 11 for XO-1 also be included? And what will SoaS (Sugar 0.88) be called, and how will it be identified in the file fedora-release? (I need this info to update my activities to 0.88.) Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Font display revisited
Daniel Drake wrote: On 22 February 2010 03:13, Tomeu Vizosoto...@tomeuvizoso.net wrote: You may want to ask in the soas ml, but in 0.88 we are going to make it easier to users to change the default font size, so apps shouldn't make any assumptions based on a fixed value for that. But, in the few cases where it is of importance, they should still be able to assume that a size 13 font will be rendered at physical size of 13/72 inches on a decent display. If Soas continues to hardcode a DPI value, this will not be true. I can't find any evidence that we're currently doing this, as in: the kickstart files used for the snapshots on our way to Cloudberry don't contain any DPI setting, afaics --Sebastian Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Fedora Sugar SoaS Meeting Time
I've a conflict coming up for the next weeks with our current meeting time and would need to start something like half an hour later. If you're interested in attending, please take a second to put down when you're available here: http://whenisgood.net/fedora-sugar-mtg-1 Make sure to select your timezone at the top! --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fedora Sugar Packaging Queue
Bert Freudenberg wrote: On 12.02.2010, at 12:11, Sebastian Dziallas wrote: Hi all, I'd like to take the chance to hint once more at our tracking bug [1], [1] https://bugzilla.redhat.com/show_bug.cgi?id=558617 This should also depend on #520294. - Bert - Cool! Wasn't aware of that - thanks added. ;) --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fedora Sugar Packaging Queue
James Cameron wrote: On Fri, Feb 12, 2010 at 09:11:02PM +0100, Sebastian Dziallas wrote: In other news, we're being blocked by licensing issues for some activities and the boot screen, as I've posted before. I've recently submitted patches to bugs.sugarlabs.org for two activities because we had identified them in dev.laptop.org bugs as having inadequately described licenses in code and packaging, but are there other activities that need this review? First, I wanted to thank you for doing this! Well, I'd love to see the Physics one being finally pushed. There was another one but the maintainer fixed it directly. I'll holler if there's more (which I presume we'll come across, yes). --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Fedora Sugar Packaging Queue
Hi all, I'd like to take the chance to hint once more at our tracking bug [1], as well as the activity wiki page [2]. Recently, TamTam has been posted for review, too. I'm a little disappointed with the speed we're progressing with. Here's a list of the currently most important things we need to get in. Settings Manager - https://bugzilla.redhat.com/show_bug.cgi?id=563598 NoDM - https://bugzilla.redhat.com/show_bug.cgi?id=559559 TamTam Suite - https://bugzilla.redhat.com/show_bug.cgi?id=564425 Typing Turtle - https://bugzilla.redhat.com/show_bug.cgi?id=559213 Other reviews still require action, either by the packager or the reviewer. I'm going to ping the owners directly. In other news, we're being blocked by licensing issues for some activities and the boot screen, as I've posted before. If you get a second, please go ahead and help to unblock us here - for example by reviewing a package (these aren't really that complicated, so it shouldn't take too long) or by packaging an activity from the list. Thanks, --Sebastian [1] https://bugzilla.redhat.com/show_bug.cgi?id=558617 [2] https://fedoraproject.org/wiki/Sugar_Activities ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity SoaS Licensing Concerns
Sebastian Dziallas wrote: Sebastian Dziallas wrote: Hi folks, I've lately taken the task of packaging more activities to get us a reasonably user experience for the next iteration of SoaS. The normal review process requires an application to be properly and clearly licensed. I'd like to encourage activity authors to work on getting these clarifications, if needed, committed into GIT. For example, if your activity doesn't contain a license file that states unambiguously the licenses of the *whole* activity and all of its bundled libraries, a kind of per-file licensing would be good, as some files would be otherwise without a license specification. I'm not trying to make things up here, but am rather just realistic, as such things are simply blockers. I'll try to follow up with people... Actually, another topic is the SoaS boot screen. Since we need to get that packaged in Fedora in time (meaning basically as soon as possible), we need to have a public location where we host a tarball or a GIT repo of the boot screen picture files, together with licensing information. Can I just move ahead and put them in git.sl.o? Just to make sure everybody understands what this is about. If we are unable clarify this, there won't be a boot screen specifically for SoaS at all. If nobody complains by the end of this weekend, I'll just upload the images, put a GPLv2+ license in the archive and make a tarball, as this is what they've been listed under in Strawberry and Blueberry, too. --Sebastian Thanks, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity SoaS Licensing Concerns
Tim McNamara wrote: On 13 February 2010 09:15, Sebastian Dziallas sebast...@when.com mailto:sebast...@when.com wrote: If nobody complains by the end of this weekend, I'll just upload the images, put a GPLv2+ license in the archive and make a tarball, as this is what they've been listed under in Strawberry and Blueberry, too. --Sebastian Sebastian, apparently the GPL isn't really that great for creative works, like images documents. Will see if I can get some more info by the end of the weekend. Tim Alright, so here's the thing: I basically don't care what it's licensed under, as long as it's in the blessed license list either here [1] or here [2]. It would make certainly sense to go with a content license instead, agreed. And I guess from how our logo policy [3] looks like, we might need to have a some more restrictive one there, since the tarball would essentially only bundle the boot screen (I guess it wouldn't make much sense to put something that's intended for SoaS in the sugar-artwork package, right? - Simon?). From the wiki table in [2], it looks like we could go with a CC-BY-ND, too. Is everybody alright with this? --Sebastian [1] https://fedoraproject.org/wiki/Licensing#Good_Licenses [2] https://fedoraproject.org/wiki/Licensing#Good_Licenses_3 [3] http://wiki.sugarlabs.org/go/Marketing_Team/Logo#Logo_usage ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Heads Up: Sugar 0.87.4 coming to Rawhide
Title says it all, it should be in tomorrows build. --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Heads Up: Sugar 0.87.4 coming to Rawhide
James Cameron wrote: On Thu, Feb 11, 2010 at 08:13:40PM +0100, Sebastian Dziallas wrote: Title says it all, it should be in tomorrows build. Briefly, how do I swing across to this on an OLPC XO-1.5 that is installed with an OLPC F11 build? (There are several problems I'm investigating where I'd like to be able to test a much more recent version of Sugar, and I've not set up an environment to do that in yet). You could do something like: yum --enablerepo=rawhide update sugar* This should work - in case it doesn't, you might need to update some more dependencies from rawhide, too. I'll mention that once you executed that command, it's hard to get back, though. So it'd probably be reasonable to just reflash the XO, if things go wrong. --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity SoaS Licensing Concerns
Sebastian Dziallas wrote: Hi folks, I've lately taken the task of packaging more activities to get us a reasonably user experience for the next iteration of SoaS. The normal review process requires an application to be properly and clearly licensed. I'd like to encourage activity authors to work on getting these clarifications, if needed, committed into GIT. For example, if your activity doesn't contain a license file that states unambiguously the licenses of the *whole* activity and all of its bundled libraries, a kind of per-file licensing would be good, as some files would be otherwise without a license specification. I'm not trying to make things up here, but am rather just realistic, as such things are simply blockers. I'll try to follow up with people... Actually, another topic is the SoaS boot screen. Since we need to get that packaged in Fedora in time (meaning basically as soon as possible), we need to have a public location where we host a tarball or a GIT repo of the boot screen picture files, together with licensing information. Can I just move ahead and put them in git.sl.o? Thanks, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] image-writer-mac, incompatible with earlier Mac OS X versions
Bert Freudenberg wrote: On 30.12.2009, at 00:57, Bert Freudenberg wrote: On 30.12.2009, at 00:22, James Cameron wrote: On Wed, Dec 30, 2009 at 12:11:46AM +0100, Bert Freudenberg wrote: The changes look okay, though I'd just remove the read-only check, that should make it work on both Mac OS versions. Also since it appears to be set if an ISO-9660 filesystem is present on the media. ;-) Oh. Good point. No idea where to put it - do you think a new project on git.sl.o is warranted? I've no opinion. I don't know enough about git.sugarlabs.org policy. I made a repo and pushed the fix to http://git.sugarlabs.org/projects/image-writer Would be nice if someone could upload the latest version to http://download.sugarlabs.org/soas/releases/ - Bert - Done! Thanks for working on this. :) --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Sugar on a Stick Planning Meeting Tomorrow
Please join us in #sugar-meeting tomorrow - directly after the SLOBs meeting (so around 1600 UTC) - for a SoaS meeting. Topic will obviously be the future of SoaS for v3. --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Wrapping the Sugar Packaging Session up
Hi all, thanks everybody for attending! It was a great with cool questions and discussions. We're currently readying the logs, notes and docs which Mel logged in a GIT repo. So if you're interested in a practical step by step guide, looking at the repository would already be a good start. The logs go here (the page is currently being filled with content): https://fedoraproject.org/wiki/Classroom/Packaging_Sugar_Activities We'll meet tomorrow again at the same time, 1500 UTC in #fedora-olpc to discuss the session and how to proceed further. Thanks for attending! --Sebastian Make sure to drop me an e-mail if you've any questions! ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fedora Sugar Meeting Minutes 31/12/2009
Hi Wade, thanks a lot for sharing your concerns that openly! I've dropped a few comments inline... Wade Brainerd wrote: Hi Sebastian, I'm concerned that you guys are planning to require activity authors to package their activities in Fedora, in order to see them shipped in SoaS. Is this the case? We're not going to require anybody doing anything - and certainly not in the current state. Creating RPMs from activities is at the moment still too complicated - which is why we're working at making it easier. As you say below yourself, even tarballs don't get created by some authors. So it wouldn't even be possible to ask people to install Fedora, read lots of documents, create random .spec files and run spurious commands (exaggeration intended). So. That's also why we're doing this as a Fedora / Sugar effort and we're sending this to fedora-olpc and sugar-devel: People from Fedora could get easily into contributing to Sugar by helping out with packaging and probably doing more things on their favorite activity. And Sugar folks might be interested in doing some distro work, too. Currently SoaS pulls a predefined list of activities from ASLO. This is true. I think requiring Fedora packaging would be too much extra work activity authors. If you look at the packaged versions on download.sugarlabs.org, many are out of date from their ASLO equivalents. That's true, too. But it means that even just running one additional command doesn't get done by some authors. Also, will you still allow packages from rpmfusion? These are currently required to make VirtualBox Guest Additions work. I don't think this should be a blocker for us. From what I know, the VirtualBox Guest Additions are not in Fedora because they ship a kernel module and Fedora doesn't permit the inclusion of kernel modules. Anyway, what I'm basically saying is just that moving work we're doing anyway (as SoaS, a distributor) upstream is a good thing. Best, Wade Cheers, --Sebastian On Thu, Dec 31, 2009 at 11:30 AM, Sebastian Dziallassebast...@when.com wrote: This is it. First meeting after some time, quite some folks joined. Thanks to all those who dropped by! Here are the minutes and logs: http://meeting.olpcorps.net/fedora-olpc/fedora-olpc.minutes.20091231_1013.html http://meeting.olpcorps.net/fedora-olpc/fedora-olpc.log.20091231_1013.html Next date is the Sugar Packaging Session on Jan 6, 1500 UTC [1] - if you're interested in learning how to package, join us! --Sebastian [1] https://fedoraproject.org/wiki/Classroom#Upcoming_Classes ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Fedora Sugar Meeting Minutes 31/12/2009
This is it. First meeting after some time, quite some folks joined. Thanks to all those who dropped by! Here are the minutes and logs: http://meeting.olpcorps.net/fedora-olpc/fedora-olpc.minutes.20091231_1013.html http://meeting.olpcorps.net/fedora-olpc/fedora-olpc.log.20091231_1013.html Next date is the Sugar Packaging Session on Jan 6, 1500 UTC [1] - if you're interested in learning how to package, join us! --Sebastian [1] https://fedoraproject.org/wiki/Classroom#Upcoming_Classes ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Weekly Fedora Sugar Meetings
Walter Bender wrote: What channel? #fedora-edu? #sugar-meeting? Oh, right! I'd say let's just go for #fedora-olpc for now... See you there! --Sebastian -walter On Mon, Dec 28, 2009 at 4:06 PM, Sebastian Dziallassebast...@when.com wrote: Hi all, you've probably heard the rumor, that SoaS v3 will only ship Fedora packages. Now let me tell you this: It's true. What this means is that we can use a lot of help with packaging all kinds of crazy-awesome activities and other stuff for Fedora - which will get a Sugar environment with even more and better apps on its turn. So. Let's get this party started. I'm suggesting weekly meetings starting this Thursday, at 1500 UTC, 1000 EST [1]. Who else is in for this? Drop a note here! For those who're interested in getting started with contributing to Sugar, for example by packaging activities, there will be a Fedora Classroom session on January 6 (1500 UTC) in IRC Gobby [2]. --Sebastian [1] http://www.timeanddate.com/worldclock/fixedtime.html?month=12day=31year=2009hour=15min=0sec=0p1=0 [2] https://fedoraproject.org/wiki/Classroom ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] SoaS with Sugar 0.87.2 coming to a system near you
Hi everybody, by popular request, there's now a Sugar on a Stick snapshot with the latest Sugar development release available. Please note that this snapshot is already part of our way to Sugar on a Stick v3. It's still based on F12 for stability reasons, though (this will change in the development cycle). But it incorporates already a number of significant changes which are part of the change to the SoaS v3 builds. The build is available here: http://download.sugarlabs.org/soas/snapshots/3/soas-3-20091228.iso Please follow the Blueberry instructions to put it on your flash drive. You can even run it on your XO-1 from a flash drive (NAND installation possibilities are being evaluated) by using liveusb-creator. Afterwards, plug it into your XO-1 and type: boot u:\boot\olpc.fth However, a known issue is (on the XO-1 only) that the X session tends to crash when trying to scroll. Help with debugging this would be very welcome. Thanks and happy testing! --Sebastian P.S.: Enjoy your holidays! ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] SoaS with Sugar 0.87.2 coming to a system near you
Sebastian Dziallas wrote: Hi everybody, by popular request, there's now a Sugar on a Stick snapshot with the latest Sugar development release available. Please note that this snapshot is already part of our way to Sugar on a Stick v3. It's still based on F12 for stability reasons, though (this will change in the development cycle). But it incorporates already a number of significant changes which are part of the change to the SoaS v3 builds. Before somebody beats me to it: I'm aware that this build features a... er, hot-dog on the boot screen. This is /not/ a delayed Christmas present, though. Rather, it's a consequence of using strictly only packages that are currently in Fedora for this snapshot. This also affects the number of present activities. I want everybody to be aware that this is *very* early in the development cycle. Please don't report bugs on each missing activity, but help us packaging it. Expect more to come on that front, soon. --Sebastian The build is available here: http://download.sugarlabs.org/soas/snapshots/3/soas-3-20091228.iso Please follow the Blueberry instructions to put it on your flash drive. You can even run it on your XO-1 from a flash drive (NAND installation possibilities are being evaluated) by using liveusb-creator. Afterwards, plug it into your XO-1 and type: boot u:\boot\olpc.fth However, a known issue is (on the XO-1 only) that the X session tends to crash when trying to scroll. Help with debugging this would be very welcome. Thanks and happy testing! --Sebastian P.S.: Enjoy your holidays! ___ SoaS mailing list s...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Weekly Fedora Sugar Meetings
Hi all, you've probably heard the rumor, that SoaS v3 will only ship Fedora packages. Now let me tell you this: It's true. What this means is that we can use a lot of help with packaging all kinds of crazy-awesome activities and other stuff for Fedora - which will get a Sugar environment with even more and better apps on its turn. So. Let's get this party started. I'm suggesting weekly meetings starting this Thursday, at 1500 UTC, 1000 EST [1]. Who else is in for this? Drop a note here! For those who're interested in getting started with contributing to Sugar, for example by packaging activities, there will be a Fedora Classroom session on January 6 (1500 UTC) in IRC Gobby [2]. --Sebastian [1] http://www.timeanddate.com/worldclock/fixedtime.html?month=12day=31year=2009hour=15min=0sec=0p1=0 [2] https://fedoraproject.org/wiki/Classroom ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] SoaS with Sugar 0.87.2 coming to a system near you
Peter Robinson wrote: Hi Sebastian, by popular request, there's now a Sugar on a Stick snapshot with the latest Sugar development release available. Please note that this snapshot is already part of our way to Sugar on a Stick v3. It's still based on F12 for stability reasons, though (this will change in the development cycle). But it incorporates already a number of significant changes which are part of the change to the SoaS v3 builds. The build is available here: http://download.sugarlabs.org/soas/snapshots/3/soas-3-20091228.iso Please follow the Blueberry instructions to put it on your flash drive. You can even run it on your XO-1 from a flash drive (NAND installation possibilities are being evaluated) by using liveusb-creator. Afterwards, plug it into your XO-1 and type: boot u:\boot\olpc.fth However, a known issue is (on the XO-1 only) that the X session tends to crash when trying to scroll. Help with debugging this would be very welcome. Hi Peter! ;) Given that this is only using upstream and sugar 0.86 is in Fedora 12 is the 0.87.x components in their own repository? If so where is it :-P Well... this was accomplished by doing a quick dirty rebuild. Here's the repository: http://download.sugarlabs.org/soas/repositories/3/ Those are exactly the F13 packages, just rebuilt. As soon as we move on to using F13 as the base system, this repo will be nuked. --Sebastian Regards, Peter ___ SoaS mailing list s...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Please Read] SoaS v2 RC Issues
Sayamindu Dasgupta wrote: Confirmed that Read v78 has a jumpy cursor issue which can be avoided by reverting back to v77. Can't reproduce crash yet (trying to get hold of a F12 based system). I can reproduce it using v77, too. The log is here: pastebin.be/22280 --Sebastian -sdg- On Thu, Dec 3, 2009 at 9:55 AM, Sayamindu Dasguptasayami...@gmail.com wrote: Please revert to the previous version of Read if possible (v77) and check if it works. I'm trying to reproduce this, but I'm at a conference at the moment and can't download vm images. Also, regarding Project Gutenberg EPUBs, they are quite shoddy, so we should really consider whether including them is a nice idea (I can figure out some of the legal issues, but in such a situation it may be prudent not to include any EPUB at all) Thanks, Sayamindu On Thu, Dec 3, 2009 at 7:13 AM, Sebastian Dziallassebast...@when.com wrote: Hi all, this is a very quick update on the current state of SoaS v2. We discovered on Tuesday that we wouldn't be able to ship content due to legal concerns that was originally intended to be included and discussed how to proceed in the last two days. Specifically, we won't include anything that contains a CreativeCommons NC or ND clause, or any equivalent license. Hence, we're going to ship only books from Project Gutenberg. I've taken the task of replacing all books in question with adequate alternatives. Please speak up if you've any book suggestion that: * is illustrated * comes from Project Gutenberg * is preferably in a language other than English (not required) On the other hand, while testing another RC locally in a VM, I figured that Read crashed when attempting to *scroll* through an .epub file. Additionally, one isn't able to open the content afterwards. This is almost certainly a blocker, but we *will* need to create the master image this afternoon (Central European Time). If you've a spare minute, please help us out here! Thanks, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Sayamindu Dasgupta [http://sayamindu.randomink.org/ramblings] ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] [Please Read] SoaS v2 RC Issues
Sebastian Dziallas wrote: Sayamindu Dasgupta wrote: Confirmed that Read v78 has a jumpy cursor issue which can be avoided by reverting back to v77. Can't reproduce crash yet (trying to get hold of a F12 based system). I can reproduce it using v77, too. The log is here: pastebin.be/22280 Actually, with v76, I get two scrollbars. The left one works, while the right one causes the crash, too. --Sebastian ...going down the version history now. --Sebastian -sdg- On Thu, Dec 3, 2009 at 9:55 AM, Sayamindu Dasguptasayami...@gmail.com wrote: Please revert to the previous version of Read if possible (v77) and check if it works. I'm trying to reproduce this, but I'm at a conference at the moment and can't download vm images. Also, regarding Project Gutenberg EPUBs, they are quite shoddy, so we should really consider whether including them is a nice idea (I can figure out some of the legal issues, but in such a situation it may be prudent not to include any EPUB at all) Thanks, Sayamindu On Thu, Dec 3, 2009 at 7:13 AM, Sebastian Dziallassebast...@when.com wrote: Hi all, this is a very quick update on the current state of SoaS v2. We discovered on Tuesday that we wouldn't be able to ship content due to legal concerns that was originally intended to be included and discussed how to proceed in the last two days. Specifically, we won't include anything that contains a CreativeCommons NC or ND clause, or any equivalent license. Hence, we're going to ship only books from Project Gutenberg. I've taken the task of replacing all books in question with adequate alternatives. Please speak up if you've any book suggestion that: * is illustrated * comes from Project Gutenberg * is preferably in a language other than English (not required) On the other hand, while testing another RC locally in a VM, I figured that Read crashed when attempting to *scroll* through an .epub file. Additionally, one isn't able to open the content afterwards. This is almost certainly a blocker, but we *will* need to create the master image this afternoon (Central European Time). If you've a spare minute, please help us out here! Thanks, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Sayamindu Dasgupta [http://sayamindu.randomink.org/ramblings] ___ SoaS mailing list s...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/soas ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Please Read] SoaS v2 RC Issues
Sean DALY wrote: My call is we leave them out and concentrate on the wiki page. (http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/ebooks). We can't keep slipping the master as I'm sure you'll agree Sebastian :-) +1 - to both! :) That's really reasonable. Ideally, the default Browse homepage could have a link under the Sugar labs logo: click here for sample eBooks for children. is that doable? I wouldn't be able to do this by hacking in the kickstart file anymore, ideally, Simon would release a new Browse version with a modified index.html file. For now, I've replaced the schools tag on the top of the page with one saying books. If somebody provided a patch for the main page and we'd get a new release, that would be probably better, though. with a link to the wiki page which by Tuesday will have a simple procedure for downloading and reading an eBook as well as links to sources. I'm pleased that contributors have added links to that page. Yes, cool! :) We'll put that link in the PR too. I've renamed the page to E-Books instead of ebooks, but there's a redirect in place, so both will work. What do you think? That sounds all cool to me! --Sebastian Sean On Thu, Dec 3, 2009 at 12:24 PM, Sebastian Dziallassebast...@when.com wrote: Sayamindu Dasgupta wrote: Please revert to the previous version of Read if possible (v77) and check if it works. I'm trying to reproduce this, but I'm at a conference at the moment and can't download vm images. Also, regarding Project Gutenberg EPUBs, they are quite shoddy, so we should really consider whether including them is a nice idea (I can figure out some of the legal issues, but in such a situation it may be prudent not to include any EPUB at all) Yes, I'm not that confident with the Gutenberg ones, either. epubbooks.com had really high quality content, but the books are under a CC NC ND license, which causes the issues. Not sure, maybe we should focus on the newly designed wiki page and leave them really out? Sean, what do you think? I'm just saying this because I don't have much time today and would either put effort in getting the wiki page or the book selection done. Thanks for the quick reply! --Sebastian Thanks, Sayamindu On Thu, Dec 3, 2009 at 7:13 AM, Sebastian Dziallassebast...@when.com wrote: Hi all, this is a very quick update on the current state of SoaS v2. We discovered on Tuesday that we wouldn't be able to ship content due to legal concerns that was originally intended to be included and discussed how to proceed in the last two days. Specifically, we won't include anything that contains a CreativeCommons NC or ND clause, or any equivalent license. Hence, we're going to ship only books from Project Gutenberg. I've taken the task of replacing all books in question with adequate alternatives. Please speak up if you've any book suggestion that: * is illustrated * comes from Project Gutenberg * is preferably in a language other than English (not required) On the other hand, while testing another RC locally in a VM, I figured that Read crashed when attempting to *scroll* through an .epub file. Additionally, one isn't able to open the content afterwards. This is almost certainly a blocker, but we *will* need to create the master image this afternoon (Central European Time). If you've a spare minute, please help us out here! Thanks, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [Please Read] SoaS v2 RC Issues
Hi all, this is a very quick update on the current state of SoaS v2. We discovered on Tuesday that we wouldn't be able to ship content due to legal concerns that was originally intended to be included and discussed how to proceed in the last two days. Specifically, we won't include anything that contains a CreativeCommons NC or ND clause, or any equivalent license. Hence, we're going to ship only books from Project Gutenberg. I've taken the task of replacing all books in question with adequate alternatives. Please speak up if you've any book suggestion that: * is illustrated * comes from Project Gutenberg * is preferably in a language other than English (not required) On the other hand, while testing another RC locally in a VM, I figured that Read crashed when attempting to *scroll* through an .epub file. Additionally, one isn't able to open the content afterwards. This is almost certainly a blocker, but we *will* need to create the master image this afternoon (Central European Time). If you've a spare minute, please help us out here! Thanks, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] SoaS v2 approaching RC state
Bert Freudenberg wrote: On 24.11.2009, at 22:13, Sebastian Dziallas wrote: Hi all, with the next SoaS release coming up really soon (final image is supposed to be composed this weekend, release date is Dec 8), there's a new snapshot ready for you. It includes a lot of fixes and smaller adjustments. It's currently only available as a general .iso build, others will presumably follow later. You can get it from here: http://download.sugarlabs.org/soas/snapshots/2/soas06.iso Nice! As for the instructions on the Mac, it's odd that you need the most skills on that platform ;) I just modified the Linux image-writer script for Mac OS X, see attachment. It's a bit safer and more comfortable than using raw dd (e.g., it only offers USB drives, shows the volume label not just device node etc). Only tested on my own Snow Leopard machine so far - please report back. Whoa! :) Great work, thanks! I don't have a Mac here, so I can't test it, but I think we'd want to use it and put the screenshot in the instructions. Of course, doing this with an iso image as in the screenshot is nonsense, but there is no real USB image yet, right? When it becomes available, what will be its name? Oh, you can actually even do that! The F12 .iso images are hybrid ones, so you can use dd to copy them over to a flash drive... Thanks again, --Sebastian - Bert - PS: for the documentation folks: it is spelled Mac OS X. Not OS/X or OSX. Just spaces. See http://apple.com/macosx/ ;) *noted*! ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Reminder please how to flash XO-1 NAND with soas05xo.iso
Sean DALY wrote: that's the thing, there are no .img and .crc files for soas05xo that I can find? True, actually (sorry for the confusion). There are currently some issues with the image creation for the XO, which just need to be worked around (no big deal, really not) - we just need to get to it. --Sebastian thanks Sean On Tue, Nov 24, 2009 at 4:02 PM, Sebastian Dziallassebast...@when.com wrote: Sean DALY wrote: I did manage to generate the .img and .crc files with the live-iso-t-xo.sh script, but after successful nand-copy of soas05xo.img the XO-1 does not boot, freezes at avatar with no dots :-( Sorry for the late reply. I was a bit busy with writing docs and fixing bugs over the last days. I'm not sure why you're trying to use the livecd-iso-to-xo script, as we're providing .img and .crc files for the latest snapshots: http://download.sugarlabs.org/soas/snapshots/2/ To all: Any help with debugging issues, especially the critical ones, would be greatly appreciated: https://bugs.launchpad.net/soas/+bugs Oh, and just to make sure: SoaS is supposed to go GOLD this weekend! --Sebastian Sean On Tue, Nov 17, 2009 at 12:04 PM, Sean DALYsdaly...@gmail.comwrote: I found this post by Tomeu with instructions: http://lists.sugarlabs.org/archive/sugar-devel/2009-March/012521.html I burned the ISO file to a CD and found the livecd-iso-to-xo script on it. I will generate the .img and .crc files, if that works I will update the wiki with the step-by-step procedure. thanks Sean On Tue, Nov 17, 2009 at 10:39 AM, Peter Robinsonpbrobin...@gmail.com wrote: On Tue, Nov 17, 2009 at 9:33 AM, Sean DALYsdaly...@gmail.comwrote: Tomeu helped me with this at SugarCamp with the soas04xo image, but I didn't see what files were on his stick. I'd like to update an XO-1 to the soas05xo image, could someone please confirm this is the procedure? I'm confused that what should be an .img file seems to be an .iso file (found here: http://download.sugarlabs.org/soas/snapshots/2/ ). I'm willing to update http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation/OLPC Option 2 section More recent builds are better if this is indeed the procedure. thanks, Sean ** * Verify security is disabled (developer key valid). Boot into OpenFirmware ok prompt (hit Escape key - upper left with X - right after chime), type disable-security; response should be No wp tag. Obtain key otherwise as described here (usually takes 24 hours): http://wiki.laptop.org/go/Activation_and_developer_keys * Verify firmware version is Q2E41 ( http://wiki.laptop.org/go/OLPC_Firmware_q2e41 ). In Sugar, inspect Settings/About my Computer, alternatively boot banner above OpenFirmware ok prompt, or in Terminal Activity: cat /ofw/openprom/model * Remind XO-1 owner that all data will be completely erased. To back up existing nand image: save-nand u:\my-nand.img or save-nand sd:\my-nand.img * Shut down XO-1, insert USB stick or SD Card with soas05xo.iso file. Make sure battery is not discharged, better to have power plugged in * Boot to OFW ok prompt, type copy-nand u:\soas05xo.iso for USB stick or copy-nand sd:\soas05xo.iso for SD Card * After nand is written, reboot. That looks OK to me. You should have an img and a crc file so it looks like the image for the XO wasn't generated correctly. Cheers, Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Feature_SoaS_customization Draft
Carlo Falciola wrote: Hi, I think that customization support is going to be an key point for Sugar/SOAS deployement efforts and for nanaging relationship with field structures. So I'm trying to start an effort in order to write down in as much as possible detail all the potentially existant entry points for customizing Sugar without breakin it. Till' now I choose to sketch this in a Feature proposal, because even if really documentation only effort I think it could be part of the Sugar platform. Please, any help, critics, suggestion, fix, are absolutely welcome and needed! Cool, thanks for moving this forward! http://wiki.sugarlabs.org/go/Features/Feature_SoaS_customization I'm not sure it should be a Sugar 0.88 feature, but will leave this to Simon Tomeu - I guess it would fit more into the SoaS process, which is to be outlined once Blueberry is out. Anyway, really nice work! :) Eventually sometimes in the future this should become some more structured and formalized ... I had already started a page some time ago here, but didn't get to finish it: http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Customization Maybe we could throw the stuff together at some point... ciao carlo --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Reminder please how to flash XO-1 NAND with soas05xo.iso
Sean DALY wrote: I did manage to generate the .img and .crc files with the live-iso-t-xo.sh script, but after successful nand-copy of soas05xo.img the XO-1 does not boot, freezes at avatar with no dots :-( Sorry for the late reply. I was a bit busy with writing docs and fixing bugs over the last days. I'm not sure why you're trying to use the livecd-iso-to-xo script, as we're providing .img and .crc files for the latest snapshots: http://download.sugarlabs.org/soas/snapshots/2/ To all: Any help with debugging issues, especially the critical ones, would be greatly appreciated: https://bugs.launchpad.net/soas/+bugs Oh, and just to make sure: SoaS is supposed to go GOLD this weekend! --Sebastian Sean On Tue, Nov 17, 2009 at 12:04 PM, Sean DALYsdaly...@gmail.com wrote: I found this post by Tomeu with instructions: http://lists.sugarlabs.org/archive/sugar-devel/2009-March/012521.html I burned the ISO file to a CD and found the livecd-iso-to-xo script on it. I will generate the .img and .crc files, if that works I will update the wiki with the step-by-step procedure. thanks Sean On Tue, Nov 17, 2009 at 10:39 AM, Peter Robinsonpbrobin...@gmail.com wrote: On Tue, Nov 17, 2009 at 9:33 AM, Sean DALYsdaly...@gmail.com wrote: Tomeu helped me with this at SugarCamp with the soas04xo image, but I didn't see what files were on his stick. I'd like to update an XO-1 to the soas05xo image, could someone please confirm this is the procedure? I'm confused that what should be an .img file seems to be an .iso file (found here: http://download.sugarlabs.org/soas/snapshots/2/ ). I'm willing to update http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation/OLPC Option 2 section More recent builds are better if this is indeed the procedure. thanks, Sean ** * Verify security is disabled (developer key valid). Boot into OpenFirmware ok prompt (hit Escape key - upper left with X - right after chime), type disable-security; response should be No wp tag. Obtain key otherwise as described here (usually takes 24 hours): http://wiki.laptop.org/go/Activation_and_developer_keys * Verify firmware version is Q2E41 ( http://wiki.laptop.org/go/OLPC_Firmware_q2e41 ). In Sugar, inspect Settings/About my Computer, alternatively boot banner above OpenFirmware ok prompt, or in Terminal Activity: cat /ofw/openprom/model * Remind XO-1 owner that all data will be completely erased. To back up existing nand image: save-nand u:\my-nand.img or save-nand sd:\my-nand.img * Shut down XO-1, insert USB stick or SD Card with soas05xo.iso file. Make sure battery is not discharged, better to have power plugged in * Boot to OFW ok prompt, type copy-nand u:\soas05xo.iso for USB stick or copy-nand sd:\soas05xo.iso for SD Card * After nand is written, reboot. That looks OK to me. You should have an img and a crc file so it looks like the image for the XO wasn't generated correctly. Cheers, Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] SoaS v2 approaching RC state
Hi all, with the next SoaS release coming up really soon (final image is supposed to be composed this weekend, release date is Dec 8), there's a new snapshot ready for you. It includes a lot of fixes and smaller adjustments. It's currently only available as a general .iso build, others will presumably follow later. You can get it from here: http://download.sugarlabs.org/soas/snapshots/2/soas06.iso Let us know how it goes and help us debugging and fixing the remaining bugs here: https://bugs.launchpad.net/soas/+bugs A last note, if anybody knows what's wrong with Record, Cairo and F12, please drop us a line! Thanks. --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Non sugar activities on ASLO
Jim Simmons wrote: Aleksey, It would be helpful to have a way to distribute things like the gstreamer espeak plugin you wrote. Fedora doesn't currently include it. It would be even better if you could distribute versions that work on the XO running .82, as well as versions for current Fedora. Don't know if that was what you had in mind. Actually, it does [1]. I know because I packaged it for Fedora to move as many packages as possible directly into our upstream distribution. So it's available, but only for newer Fedora versions, as the older ones have been EOLed. --Sebastian [1] https://admin.fedoraproject.org/pkgdb/packages/name/gstreamer-plugins-espeak James Simmons Date: Mon, 23 Nov 2009 13:23:22 + From: Aleksey Limalsr...@member.fsf.org Subject: [Sugar-devel] Non sugar activities on ASLO To: sugar-devel@lists.sugarlabs.org Message-ID:20091123132321.gb3...@antilopa-gnu Content-Type: text/plain; charset=us-ascii Hi all, Non sugar activities we (could)have on ASLO: ++ programs with high sugar integration(journal etc.) + programs that start smooth in sugar environment(sugarised screen mode etc.) - programs that are just absent in GNU/Linux distributions -- programs that present in GNU/Linux distributions In case of '-*' programs we just not follow Occam's razor principle moreover we are splitting education community(people should know that there is native GCompris and sugarized GCompris). On the other side if ASLO intended to be software repository for sugar DE. So, what about not multiplying entities and reusing 0install for '-*' programs(but still not sure about '--'). For example in case of OO4kids activity we can create 0install infrastructure(and benefit other non sugar 0install users) or reuse existed 0install package. For sugar user, 0install activities will look on ASLO like other activities, so click on Download button just runs sugarized 0install GUI. -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fw: Nano and soas03/04/05
Sorry for the late reply... I'm quite behind my e-mail. :/ Just add --nogpg to your yum call, and it should work for now. We're looking to get this generally to work in Blueberry. --Sebastian Art Hunkins wrote: I'd really appreciate a response about this. On sticks make with snapshots soas03, 04, and 05, I've attempted to install nano. (Yes, I try to do development with the USB sticks themselves.) Via yum, tt downloads nano 2.0.9-6.fc13.i686.rpm, but then indicates that the rpm is not signed. Can I do anything - or do I need to wait for Blueberry for this to sort itself out? Art Hunkins - Original Message - From: Art Hunkinsabhun...@uncg.edu To:sugar-devel@lists.sugarlabs.org Sent: Tuesday, November 17, 2009 8:32 PM Subject: Nano and soas03/04/05 I've been working with the SoaS03, 04, and 05 iso's, and want to download the nano text editor. I've not been able to do so. I do: su yum install nano This has always worked for me in the past. All goes well until I'm informed that the (fc13) rpm is not signed. Perhaps a version incompatibility? What to do? Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Adjusting the Sugar on a Stick (Blueberry) Roadmap
Hi everybody, after considering input from the various teams involved in Sugar Labs and the Sugar on a Stick creation, we're shifting the SoaS as followed. 2009-11-17 Fedora 12 Final Release in the time between: wiki documentation must be readied! 2009-11-29 Image Gold Master Creation Upload 2009-12-08 Sugar on a Stick (Blueberry) Public Release I'm working on the docs at the moment, so expect some posts on that soon. It would be great if we could get SoaS on the static SL pages, too - maybe we could get something off the ground there? Please consider SoaS v2 to be in freeze from now on. Let's make this a great release! Help us fixing the bugs listed on our bug tracker: http://bugs.launchpad.net/soas Thanks, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Strawberry ID?
The file /etc/fedora-release might be where you want to look... --Sebastian Art Hunkins wrote: I can't seem to find either the lsb_release command, or a file by that name. Typing lsb_release in the Terminal gives me file not found. Find doesn't locate the file either, nor does a listing of the /etc/ directory (I thought I understood that is where it was supposed to be). I tried these things on the XO-1, Strawberry, soas03 and soas04. Can you give a further hint? Should my Python line read something like: if not /etc/lsb_release(LSB_VERSION) == 1.0: to rule out Strawberry? I'd at least like to play around with this idea to see if I can accurately identify select versions. Art Hunkins - Original Message - From: Tomeu Vizosoto...@sugarlabs.org To: Art Hunkinsabhun...@uncg.edu Cc:sugar-devel@lists.sugarlabs.org Sent: Thursday, November 12, 2009 1:47 PM Subject: Re: [Sugar-devel] Strawberry ID? On Thu, Nov 12, 2009 at 19:36, Art Hunkinsabhun...@uncg.edu wrote: What bit of code would identify SoaS as Strawberry, in contrast to any later versions, including soas03, soas04 and eventually Blueberry? A common mechanism for detecting the distro and version is lsb_release, but I'm not sure how well will work for the use cases you are interested in. Regards, Tomeu Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] is csound-python part of the Sugar Platform?
Art Hunkins wrote: Please do include csound-python. I'd like my new activities to work right out of the box. On a side-note, we've already included it in the latest SoaS snapshots, so it'll make it's way into the Blueberry release. --Sebastian Hopefully, doing so will also encourage others to write activities that use Csound. I, for one, would *never* have attempted an activity if it weren't for csound-python and Victor Lazzarini's csndsugui (a python Csound helper script). Art Hunkins - Original Message - From: Aleksey Limalsr...@member.fsf.org To: Daniel Draked...@laptop.org Cc: Sugar-dev Develsugar-devel@lists.sugarlabs.org Sent: Tuesday, November 03, 2009 1:51 PM Subject: Re: [Sugar-devel] is csound-python part of the Sugar Platform? On Tue, Nov 03, 2009 at 11:35:12AM +, Daniel Drake wrote: Hi, http://wiki.sugarlabs.org/go/0.84/Platform_Components doesn't make it clear. Is csound-python part of the Sugar platform? In my mind its wasn't part of SP-0.84, we didn't have activities (at least on ASLO) that use python binding. But I guess we can add it to SP-0.86 - in most cases if distribution has csound, it has python binding. For old OLPC builds, olpcsound did include the csound python module, although this was unused by all of the standard OLPC-shipped activities. (TamTam uses csound directly, without the python wrapper) As of the latest fedora packages, the standard csound packages do not include the python wrapper, you need an extra package (csound-python) for that. FWIW, The OurMusic activity requires this. Thanks, Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] New SoaS Snapshot ready!
Hi all, here's the next snapshot on our way to SoaS v2 Blueberry. This one fixes some issues and introduces new features, namely: * the updated FoodForce2, Slideruler and SocialCalc activities * the gtk-recordmydesktop tool - execute it from the terminal * new sample content - Alice's Adventures in Wonderland - see below * fix boot issues of XO builds - Martin Dengler The snapshot is available here (following the soas04 naming scheme): http://download.sugarlabs.org/soas/snapshots/2/ Known issues (https://bugs.launchpad.net/soas/+bugs) include: * Sugar crashes on XO if vertical scrollbar accessed * Record fails to launch on a Classmate 2 (Magalhãls) * No sample maps appear in v2 Snapshots * Read crashes when trying to display EPUB sample * CartoonBuilder Activity fails to launch In case you've an idea what's going on with these issues, please comment in their tickets or just reply here, as they're pretty critical for the upcoming SoaS release! Thanks, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New SoaS Snapshot Ready!
Art Hunkins wrote: I can report that TamTamMini's sound is working fine with Soas Strawberry (with the upgrades to Csound and csound-python made by Peter Robinson). Thanks for the report! Actually, I can confirm this to be working in soas03.iso, too (didn't seem to work for me last time). However, it looks like when Kernel Mode Setting is enabled (which is the case by default), the screen might vanish. Not yet sure what's causing it... --Sebastian Art Hunkins - Original Message - From: Sebastian Dziallas sebast...@when.com To: SoaS s...@lists.sugarlabs.org; Sugar Devel sugar-devel@lists.sugarlabs.org Sent: Saturday, October 24, 2009 9:18 AM Subject: [Sugar-devel] New SoaS Snapshot Ready! Hi everybody, I'm happy to announce the availability of a new SoaS snapshot! We're only one month away from our release, so testing is very much appreciated to find the latest blockers now. Get your copy from here: http://download.sugarlabs.org/soas/snapshots/2/ This release incorporates the latest Sugar (0.86.3) packages and updates the zyx-liveinstaller to a newer version (0.1.14). Additionally, we were able to resume appliance creation! The .zip file in the download directory is exactly what you'll want for that. We could use help with the following known issues, too: * Record doesn't work and seems to have issues with its blobs (#423859) * CartoonBuilder doesn't start at all * InfoSlicer (its parser) needs to be fixed for Wikipedia * No sound is apparently working in TamTam In case we are unable to fix these issues in time, those activities won't be shipped in the final release. Please report any other bugs you encounter at our bug tracker: https://bugs.launchpad.net/soas Thanks, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] New SoaS Snapshot Ready!
Hi everybody, I'm happy to announce the availability of a new SoaS snapshot! We're only one month away from our release, so testing is very much appreciated to find the latest blockers now. Get your copy from here: http://download.sugarlabs.org/soas/snapshots/2/ This release incorporates the latest Sugar (0.86.3) packages and updates the zyx-liveinstaller to a newer version (0.1.14). Additionally, we were able to resume appliance creation! The .zip file in the download directory is exactly what you'll want for that. We could use help with the following known issues, too: * Record doesn't work and seems to have issues with its blobs (#423859) * CartoonBuilder doesn't start at all * InfoSlicer (its parser) needs to be fixed for Wikipedia * No sound is apparently working in TamTam In case we are unable to fix these issues in time, those activities won't be shipped in the final release. Please report any other bugs you encounter at our bug tracker: https://bugs.launchpad.net/soas Thanks, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] New SoaS v2 Snapshot Ready
Hi everybody, there is a new, true SoaS snapshot ready for you, awaiting testing. You can grab it here: http://download.sugarlabs.org/soas/snapshots/2/ Note that the XO images have apparently an issue (my fault!), which prevents them from booting, but will be addressed in the next build. Anyway, this build has been created and quickly tested on Monday. It adds FoodForce2 per default and introduces a number of other minor changes, mostly to the way the images are built. However, also the base system has matured, as Fedora is now in its Final Freeze, too. Finally, this build ships the latest Sugar build, 0.86.2! Satellit reports that the user need to add the selinux=0 line manually in this build when the zyx-liveinstaller is used. It will be fixed, too. Please report all issues you encounter on the appropriate bug tracker! Thanks, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] rawhide report: 20091010 changes
Mathieu Bridon (bochecha) wrote: On Sat, Oct 10, 2009 at 14:59, Rawhide Reportrawh...@fedoraproject.org wrote: Compose started at Sat Oct 10 06:15:04 UTC 2009 Broken deps for i386 -- konversation-1.2-1.fc12.i686 requires kdelibs4= 0:4.3.2 sugar-toolkit-0.86.0-1.fc12.i686 requires python-json [snip, same for x86_64, ppc and ppc64] Removed package gai Removed package gai-pal Removed package gai-temp Removed package python-json Do we have a problem Houston ? Houston here! I see Luke Macken has rebuilt sugar-toolkit not to depend on python-json since that got merged into the general python. The obvious question is whether this build got tagged. If not, well, we need a request. And could maybe use that to get the latest Sugar stuff in... ;) --Sebastian -- Mathieu Bridon (bochecha) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [SoaS] Structural Changes New Snapshots
Hi everybody,
I'm happy to announce quite some changes to Sugar on a Stick about which
you should be aware. Those have been made - incorporating users' and
developers' feedback - to reduce confusion.
(1) The SoaS directory structure has been adjusted! The snapshots have
been moved to their appropriate directory, so you'll find the SoaS v2
snapshots in /2. The same goes for the repository directories.
Additionally, the release file names have also been clarified.
(2) The SoaS snapshot naming scheme has changed! New snapshots will
follow a continuous scheme, like soas{xo}01.* and counting.
ATTENTION: The following work is untested and could eat babies.
(3) A new, SoaS and SoaS-XO snapshot is out! Thanks to the work done by
Martin Dengler, we've been able to merge the SoaS and SoaS-XO codebase.
Following subsequent efforts, we're NOW building and releasing those
images at the same time. A first result of has been made available and
is ready here: http://download.sugarlabs.org/soas/snapshots/2/
The soasxoXX.* images are obviously intended for use only with XO-1s. On
the other hand, the soasXX.* builds are the continued, general SoaS.
Please report any issues you encounter, if necessary also at Launchpad,
and let us know which images you've been using so that we can possibly
save space. Finally, on a side-note, the new soasXX.iso images should
also support being dd'ed to a device, as Satellit previously reported.
Thanks to everybody who contributed to these efforts,
--Sebastian Dziallas
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Xoos Special Interest Group
David Farning wrote: As promised, we have started work on the XO operating system SIG at Sugar Labs. The SIG pages are at http://wiki.sugarlabs.org/go/Xoos . Based on feedback from the current developers working in this space, the most valuable starting point will be to start making daily Xoos builds. The next step will be to work with others in this space to create a release cycle which includes alphas, betas, and final releases. These releases will enable more users and testers to participate in the development cycle. Martin Dengler has been incredibly pushing an effort to make SoaS run on the XO. In fact, for some time now, the normal SoaS builds and the SoaS-XO builds are using the same code-base. The plan was and is to build and announce these snapshots jointly in the very near future. Setting up a cron job to have builds should probably be not too hard... There has even been a feature proposal for that in Launchpad: https://blueprints.launchpad.net/soas/+spec/joint-soas-release Will this SIG's work be incorporated in the SoaS-XO files (I can't even speak of GIT branches anymore, because it's all in mainline now, which is just awesome!) or will it create another solution? --Sebastian Initially, communication will happen on the de...@lists.laptop.org, sugar-...@lists.sugarlabs.org, and fedora-olpc-l...@redhat.com mailing lists. We have received initial support from the OLPC contributor program in the form of developer machines. david ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [SoaS] Introducing a new Mailing List
Hi all, so here it is, finally, a mailing list for the Sugar on a Stick project. If you're interested in its future, technical discussions or just want to talk about ideas you've, this is the place to go! Jump in, say hi and introduce yourself - that's it. Join the fun here: http://lists.sugarlabs.org/listinfo/soas User feedback might be better suited for IAEP, though. By the way: Other Sugar LiveUSB projects are very much welcome on the list, too. See you there, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] [SoaS] The Future of Sugar on a Stick
Mel Chua wrote: There's a lot going on in this thread, so here is my attempt to summarize discussions so far. If I've missed or misstated anything, my apologies - and it's a wiki, so go fix it. ;-) http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick By my count, there are 4 things we need to decide on and then execute in order to wrap up this conversation. Some are already in progress. * 4.1 Make a SoaS mailing list * 4.2 Formalize a SoaS development team * 4.3 Determine what Sugar on a Stick refers to * 4.4 Determine what the code Sebastian is working on is called Only the third one has a clear owner (SLOBs) and can be decided at this time (the 4th seems to depend on the answer to the 3rd). How can we move these forward - and are there any other blocker decisions that aren't listed here? --Mel, the human ticket tracker Ahhh! Sorry, I'm a bit late to this party here... Mel, this talk and the summary page is *awesome* - thanks a lot for getting everything together there! I agree that most of the other parts are non-blocking - at least for 4.1 4.2 we probably don't need a SLOBs decision, right? - while 4.3 is something that still needs to be solved (4.4 is related to it, I'd say). --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] SoaS: Searching for Decision Panel volunteers.
Chris Ball wrote: Please volunteer by replying to this mail if you're interested, and please do so by Thursday September 24th so that we can run the vote at the Friday September 25th SLOBs meeting. Thanks! - Chris. Thanks for getting this process off the ground! :) Well, I'd obviously volunteer here... --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] [SLOBS] SLOBs Position on SoaS
Tomeu Vizoso wrote: On Wed, Sep 16, 2009 at 16:24, Daniel Draked...@laptop.org wrote: 2009/9/16 Sebastian Dziallassebast...@when.com: Let me rephrase again, to make things clear. I'd love to hear an official answer on this. Soon. Is the current SoaS going to be the primary way Sugar Labs distributes a Sugar-centric GNU/Linux distribution? Isn't there a wider question first? the one that asks if Sugar Labs is actually interested in being a distributor rather than just an upstream. I raised that question in my recent discussion and my feeling is that the responses basically said well we should really just focus on being an upstream since we already are overworked there, but actually Sugar Labs is just a platform where everyone interested in Sugar can get together and run Sugar-related projects Based on that, I'd say that SoaS is a fine project to sit under Sugar Labs but there shouldn't be a primary way of getting Sugar. Like other upstream projects, Sugar Labs should work with multiple downstreams (treating them equally) in order to achieve wide adoption of the software. That matches quite well my personal point of view. I'm just a bit concerned that the marketing team might need something like SoaS as part of their job to make Sugar widely known. But I'm just guessing here... That said, SoaS is very important for me as an upstream Sugar developer because before we had it, people had to install a linux distro or get an XO to try or test Sugar. So I have a big interest in that SoaS work continue forward, in SLs if needed. Regards, Tomeu Args! I notice that what I asked could have been misunderstood. I didn't mean to imply SoaS being only way of distributing Sugar. That's out of question and was never my intention. I apologize for any confusion if this feeling has been created. I wonder, though, if the current SoaS is going to be the primary LiveUSB distribution of Sugar supported by upstream (known as SoaS). Daniel, yes, I think this question needs to be asked. In fact, it has been asked. You mentioned it. Martin Dengler has pointed it out very clearly on IAEP just a day ago (while receiving no replies). I felt that this one question I asked implied it, but you're right. Tomeu, I agree, too. SoaS has started gaining foothold with it's (imo) very successful v1 launch. Now we need to continue following the path. The question is just where. --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SLOBS] [IAEP] SLOBs Position on SoaS
Caroline Meeks wrote: [...] snip! I agree with Daniel's question. Sebastian, what is your theory of change here? What do you think we should do and why does doing it and doing it now as an official strategic decision get us closer to having all the world's children use Sugar? So well. I think I've explained my vision of SoaS already pretty well in the open letter. That was the long-term side of things. Now it comes to what I think is important in a project. And that is - also - certainty and trust. Those are pretty important factors. For developers, as well as for users, to know where one stands. I have asked for a reply on this question because it truly affects my work. I would like to know whether my work is needed in the way I'm doing it, whether it's appreciated, whether it's respected. Wait, how do you measure this? Well, I think I've been doing quite a big amount of the SoaS work over the last year. I've been told the Sugar community was about people doing stuff, so I considered myself to be leading the SoaS effort at some point. So far so good. But if I'm leading an effort, I'd prefer to be *informed* about what's happening. This starts with trademarking things (about which I haven't been informed), continues with the idea SL has of SoaS (just to be sure I don't waste my work) and ends with people using the name of the project I considered myself to be leading - without talking while planning it. So. This is not about avoiding competition. Or about having a dictatorship. Or whatever. It's about providing a bit of certainty. In my opinion, Sugar Labs has about four options how to act wrt SoaS. (1) SL decides the current SoaS to be *the* SoaS and enforces the brand. (Did you know that you're able to lose a trademark when not enforcing it?) Exceptions could be granted by a trademark committee. (2) SL decides to have more than one SoaS, basically allowing everybody to use the brand's name. (3) SL decides not to do a distribution of Sugar and doesn't care about the naming of other projects, allowing everybody to use the name. (4) SL decides not to do a distribution of Sugar and delegates this to *one* other project, probably in another project (Fedora, Ubuntu, TOS). Those are the possibilities I can think of right now. There are probably more. I would just like to know where I'm investing my work in, since I am just a volunteer. I don't get money for this. --Sebastian On Wed, Sep 16, 2009 at 10:25 AM, Daniel Drake d...@laptop.org mailto:d...@laptop.org wrote: 2009/9/16 Daniel Drake d...@laptop.org mailto:d...@laptop.org: 2009/9/16 Sebastian Dziallas sebast...@when.com mailto:sebast...@when.com: Let me rephrase again, to make things clear. I'd love to hear an official answer on this. Soon. Is the current SoaS going to be the primary way Sugar Labs distributes a Sugar-centric GNU/Linux distribution? and to answer a question with a question: how does the answer to this affect your work? I can't immediately see its importance. Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] The Future of Sugar on a Stick
This document is an open letter written to the Sugar Labs community. It is an attempt to clear up the recent confusion about SoaS and let community members know what SoaS is, what our goals are with regards to it, and what possibilities we're considering for the future - both technical and organizational - direction of the project. With the next release of SoaS coming up in about three months, we also want to have this discussion with our current release schedule in mind. == What is SoaS? == Sugar on a Stick (SoaS) is a Linux distribution that enables kids to reclaim computers for themselves in a world of computers made and managed for and by adults. SoaS aims to make it easy for local deployers to provide each student with a thumbdrive (stick), which can be booted into the student's personalized Sugar environment from any machine. Thus, SoaS advances in achieving its goal of giving each child in the world access to its free and open source learning environment to create, explore, reflect, and collaborate on any machine - at school, at home, and elsewhere. Values: * Customizability - Deployments, as well as users, should be able to build their own SoaS easily. It is crucial for the success of SoaS to allow modifications and to make the process of creating derivates as easy as possible. * Deployability - SoaS must be easy to deploy. It should take as little effort as possible to get to a working system, both for individual sticks and for bigger deployments in computer labs. * Local Support - We must encourage and foster the growth of local community support for deployments. If we build things in a way that means deployers can't fix most of their own problems, we're doing something wrong. A note on deployability: We want SoaS to always be the easiest Sugar deployment option to support, which becomes more and more important as the product matures and is used by more schools and teachers. In order to properly support SoaS users, it is important that the upstream components of the project also be well-supported, and that we have a strong relationship with each upstream, especially our current base system - Fedora, so we can rapidly resolve any issues that may arise. But SoaS is not mature yet. It currently consists of various technologies thrown together into a first working version of a product, resulting in a number of inconsistent hacks. While we have been actively trying to follow upstream development - for example within our major component, Fedora - as much as possible, we didn't always succed here. The more development took place, solutions got hacked up, causing a difficulty of maintance in general. With the next release of SoaS coming up in about three months, we are working on reducing these issues now. One of these issues mentioned earlier is affecting users through the possibility of installing and directly deploying SoaS. Right now, teachers have to look for their own solutions to get SoaS in place, which is a situation we want to change: Ideally, they would be able to use a well-designed interface for installations and deployments. On the other hand, the structure around SoaS is rather loose: decisions tend to happen spontaneously on various mailing lists (since there is no dedicated one), as well as in IRC channels. To create a place where the project itself lives, to advance in realizing technical innovations, we need such a mailing list - as well as a development team. Yes, we need a SoaS development team for being able to implement all the cool things out there. And since I don't have the bandwidth to handle all of this myself and open source is about sharing experiences, about working together, we need to find a good way of letting more people participate in the process of working on SoaS. Following the goals and visions stated above, the subsequent short-term steps for SoaS are outlined below, with the goal in mind to become a SL project. However, the technical communication will proceed on the newly created mailing list and on Launchpad, whose pilot usage as our bug tracker will continue, too. Short Term Action Items: * We create a SoaS mailing list. * We establish the SoaS development team. Thanks, Sebastian Dziallas ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Sugar on a Stick v2 Release Naming
Sean DALY wrote:
Sebastian, what's your take? Can we retire SoaS-{1,2,3} or fold them
into the public v1, v2 numbers?
Okay, let me shed some light in here, though I think this has already
been discussed in length.
In the early days when I started working on SoaS, we still had internal
builds based on Fedora 10 - which were labeled SoaS-1 - but never got
actually released. As we proceeded in development, SoaS was rebased on
Fedora 11 and since we needed new directories, we just increased this
number. This is what became Strawberry (meaning Sugar on a Stick v1) in
the end. And it's the explanation for this probably strange situation.
It might not be the best solution and we should probably think of ways
to fix it (for example on a newly created SoaS mailing list, heh). But I
don't think it's something incredibly wrong that will scare all our
users away. Most of them will probably not even see the .iso label.
Regarding the docs, I agree: the wiki pages are cluttered. They need to
be cleaned up before the release (we've a documentation deadline in our
roadmap, though)! But this also goes hand in hand with what should be on
those pages - and that's something for the future of SoaS-thread.
--Sebastian
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] The Future of Sugar on a Stick
Jonas Smedegaard wrote: On Mon, Sep 14, 2009 at 07:47:21PM +0200, Martin Langhoff wrote: On Mon, Sep 14, 2009 at 5:32 PM, Sebastian Dziallas sebast...@when.com wrote: Short Term Action Items: * We create a SoaS mailing list. * We establish the SoaS development team. if you split off sugar-dev, to reach the involved people you either have to crosspost all the time, or get everyone sub'd to both. I'm with Jonas on this one. That depends on your definition of everyone. Possibly everyone directly involved in developing Sugar is also actively involved in developing SoaS. But not everyone interested in closely _following_ the development of Sugar (and thus in subscribing to the mailinglist) is also interested in closely following the development of SoaS. Agreed. I think such a list should be for the *development* of SoaS. That's something that concerns Sugar, too, but not my all means. If we discuss technical changes to SoaS with regard to deployments or whatsoever, sugar-devel might not be the best place. Some may suggest to take that then to IAEP, but if it's about the technical side of things, I think it should go to a different list. It might be that I am the only one not part of your everyone. But I doubt it. I imagine more people that love the concept of SoaS but have their hands full already with e.g. other distributions - making Sugar interesting to follow closely but SoaS too much sidetracking. Right. And I don't think that sugar-devel needs to get noisier than it is now - I'm strongly suggesting to create a soas mailing list. Kind regards, and all the best with the development of SoaS, - Jonas Thanks! :) --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Sugar on a Stick v2 Release Naming
Martin Dengler wrote: On Thu, Sep 10, 2009 at 05:30:30PM +0200, Sean DALY wrote: re marketing course: in fact I have accepted Mel's invitation to do a classroom for Fedora. Congratulations. re logos: Strawberry=6, Blueberry=4, and 5 we'll use some other time Very clear - thanks. [Have we agreed on Blueberry as the Name of Record?] Sebastien? So it will be! :) The next release of SoaS will be named Blueberry. Gary, Sean, could any of you give creating a new boot screen with an updated logo for plymouth a try? Thanks, --Sebastian thanks Sean Martin ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Getting a SoaS Docs Effort off the Ground
From looking at the currently available documentation for Sugar on a Stick, I think it makes sense to collaborate on writing well written official instructions for it. So I've entered a Blueprint in Launchpad on it: https://blueprints.launchpad.net/soas/+spec/better-docs-for-soas I'd like to give the great Fedora Publican tool a try, as it has recently seen a new beta release. I have set up a new GIT repo in Gitorious, which lives here: http://git.sugarlabs.org/projects/soas-docs So if you're interested in writing the next generation of totally awesomeness-spreading SoaS docs, please speak up! :) ...you can even add yourself already to the Launchpad page and apply for commit access to the GIT repo, too. --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Project Guidelines posted
David Farning wrote: The project guidelines are now on the wiki at http://wiki.sugarlabs.org/go/Sugar_Labs/Project_Guidelines . Please edit as necessary. When it looks like the editing has stopped, I ask the board the ratify the guidelines. david I just looked into this, sorry for the delay. While reading it, some questions came to my mind: How does this relate to the existing teams? In Fedora, most efforts have been started as SIGs or still in that state. Even the team working on the general Fedora desktop metaphor and maintaining the Fedora Desktop Spin is one. So would we have teams, SIGs and projects then? Or are the teams going to be migrated to SIGs? And is the Oversight Board going and willing to step into this process? I'm asking because it seems like it would be a pretty significant change to the board's tasks - at least compared to what I've been told before. --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] SoaS Test Day Team: Please sign up!
As announced before, the SoaS QA test day [1] is coming up quickly and will already take place tomorrow. We're still looking for people willing to join the team, which will support the testers in #fedora-test-day. If you'd like to jump on the train, please enter your availability here [2] so that we can schedule from when to when the test day will run (so that we don't run out of developers while testers are still around). --Sebastian [1] https://fedoraproject.org/wiki/Test_Day:2009-09-03_SoaS [2] http://whenisgood.net/soas-test-day ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Next Test Day: Sugar on a Stick [Tomorrow]
Greetings, sorry for the late notice and the cross-post. This test day will focus on Sugar Labs' Sugar on a Stick, a downstream project based on Fedora. Sugar on a Stick has launched it's first version codenamed Strawberry successfully in June and has recently announced the beta release of its next version. It contains basically a slightly modified version of the Sugar Desktop on a Fedora System, prepared to be deployed on USB keys. The test cases have been developed with the goal in mind to be of value for both projects, Sugar Labs and the Fedora Project. The latter one will especially profit from a better integration of the aforementioned desktop, as well as the testing of the LiveUSB technology. Additionally, new features like the rebootless live installer, which has been discussed before (and been included in Fedora lately) are also ready for testing. We invite you to jump in #fedora-test-day tomorrow, September 3, and to join the fun! More concrete information can be found in the wiki: https://fedoraproject.org/wiki/Test_Day:2009-09-03_SoaS Thanks, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] SoaS Test Day: Join the Support Team
Hi everybody, as noted in our roadmap for Sugar on a Stick [1], we are going to have a joint test day with the folks from Fedora's Quality Assurance [2] to improve the quality of SoaS on its way to version 2 (in November). The test day is scheduled to take place on September 3, which is this Thursday. We are also going to announce the SoaS v2 beta release shortly, which is intended to be used for this testing. However, we are still looking for people to join the team to hang out in the IRC channel and to provide directions and help to the testers. If you have some spare time on Thursday and are able to contribute to this effort, please sign up in the Fedora Wiki [3]. In case you don't have a Fedora Account, please drop me a line and I will add you there. Thanks, --Sebastian [1] http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap [2] https://fedoraproject.org/wiki/QA [3] https://fedoraproject.org/wiki/Test_Day:2009-09-03_SoaS ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] New snapshot on the way...
Dave Bauer wrote: On Tue, Aug 18, 2009 at 6:05 PM, Sebastian Dziallas sebast...@when.com mailto:sebast...@when.com wrote: Hi everybody, we've a new SoaS snapshot ready for testing. Here are the major changes: - We just made the switch to Rawhide (which is supposed to become F12). So watch out for any breakages - and shout if you notice any! :) - We now ship the shiny new zyx-liveinstaller! This is a very early alpha implementation which installs the contents of your USB key to a hard disk (which you'll need to partition manually with the included gparted for now). It features a rebootless installation feature, meaning that after the installation has finished, you should already be able to unplug the USB key. If you encounter any issues especially related to this new technology, please let us know immediately, given that this is somewhat critical for the release. Does this allow you to create a full install onto anoter USB yet? Sorry for the late reply. Well, I think upstream made some progress, however I heard there was still some stuff to work out. Maybe we can find a way to duplicate USB keys using livecd-iso-to-disk (that was suggested in RHBZ #448030). I'll ping Jeremy. --Sebastian Thanks Dave ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Sugar on a Stick switches to a new Bug Tracker
Hi everybody, with the imminent release of the SoaS v2 Beta in just ten days, I would like to announce the switch to Launchpad as our bug tracker. We have been evaluating an instance Luke Faraone set us up with lately and are confident that it will fit our needs. The upcoming beta release is the first one intended to be used with this instance. More precisely, we will use it to track bugs, as well as new features. Note that this change only affects Sugar on a Stick, while the core Sugar bug tracker stays at dev.sugarlabs.org. You can access and explore it here: https://launchpad.net/soas Thanks, --Your SoaS Team ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] SoaS v2 Beta Readiness Meeting Appointment
The SoaS v2 Beta Readiness Meeting is going to take place on Sunday, August 23, 1400 UTC (making it 1000 EDT and 1600 CEST) in #sugar-meeting. Looking forward to seeing everybody there! --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Fedora Education Spin Nightly Builds now available!
Just a quick heads-up to note that daily builds of our education spin based on Rawhide are available thanks to the great work of the Infra Spin SIG folks. http://alt.fedoraproject.org/pub/alt/nightly-composes/ Those builds conclude what is supposed to become the Fedora Education Spin for F12 and follow the concept of POSSE's Education Fedora Remix [1]. If you've any suggestions how we can improve the experience on this spin or what additional apps to include, please let us know! --Sebastian [1] https://www.redhat.com/archives/fedora-announce-list/2009-July/msg7.html ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Call for volunteers to implement Bug Report feature
C. Scott Ananian wrote: On Mon, Aug 17, 2009 at 12:59 PM, Mathieu Bridon (bochecha)boche...@fedoraproject.org wrote: On Mon, Aug 17, 2009 at 18:29, Luke Faraonel...@faraone.cc wrote: On Mon, Aug 17, 2009 at 11:53, Aleksey Limalsr...@member.fsf.org wrote: One of sugar lacks is an easy way to send bugreports(especially for non-tech users), so if someone interested in please pick [1] up. From what I've seen on IRC, Sebastian Dziallas is currently working on a solution, either by porting Apport to Sugar, using GNOME's bug-buddy, or the Fedora bug reporter. (still in the investigative stage) FWIW, at my current company we: a) use apport, tied to our internal bug tracker (fogbugz) -- it works great. So apport++ in general, but it works best for *automatically generated* bugs (ie, crashes). b) We *also* have a very simple web-based bug reporter -- basically it just opens a web site with a simple form on it. It should be pretty trivial to make an activity based on Browse that just points to a local html file which submits to bugzilla (or some other database). I'd recommend using this to collect feedback which is not crashes. --scott Oh, that sounds cool! :) Yeah, as Luke said, I'm investigating both Ubuntu's Apport and Fedora's ABRT. However, I'm not yet sure if they'll fit our needs, so we might also end up with something web-based, yeah. /me hrms and wants to get this to work soonish... --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Call for Help: SoaS Display Manager (Auto-Login)
Ton van Overbeek wrote: Regarding getting auto-login to work after restarting X. Yesterday I looked at the slim sources and it seems at first sight easy to add auto login of the default user after the first login. Any interest in me trying to implement this? If we use an extra option to slim we could push this change upstream to Fedora and then we do not have to maintain our own manager (olpc-dm). But maybe Sebastian is already happy with a working olpc-dm. Ton van Overbeek Ahhh! Sorry, I missed this entirely and just noticed it in another folder when going through my e-mail today. Well, I certainly wouldn't mind if you went ahead and gave it a try, but I'm not sure how likely it is that this change would be accepted, pushed into a release and then packaged for Fedora. Well, you're right, I'm happy with a working olpc-dm, but I'm also always looking for ways to improve SoaS... ;) Thanks a lot, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Who's interested in testing a new installer for SoaS?
Joshua N Pritikin wrote: On Sun, Aug 09, 2009 at 02:46:50PM +0530, Joshua N Pritikin wrote: A few lines up from the last boot message, it says: mount: unknown filesystem type 'jffs2' That can't be a good sign. This is indeed not a good sign. We've had this some time ago with the Rawhide-XO builds. Apparently, it affects our general images, too. See for the report: https://bugzilla.redhat.com/show_bug.cgi?id=500196 Martin Dengler has been building special builds of SoaS for the XO, which we should probably get out soon. Martin, what's the current state of that, can we put 'em up? :) I got the same failure with the Strawberry release. Has anybody realized success with Option 3? http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation/OLPC I wasn't aware of the fact that it affects us directly, but it looks like we might need to clean up our docs at some point... Sorry for the issues, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [SoaS] Snapshot shipping Sugar 0.85.2
Hi everybody, we've a new snapshot ready for you including the latest Sugar 0.85.2 release (except etoys, which is still being packaged). Also, this release ships now with the firstboot wizard, as discussed during FUDCon. The latter one allows you to change your keyboard settings before logging in, as well as to submit your hardware profile information using smolt. More information will follow soonish. Also note that we've pulled the latest activity release from a.sl.o, which should fix some bugs. Finally, here are the links: http://download.sugarlabs.org/soas/snapshots/3/SoaS3-200908072039.iso http://download.sugarlabs.org/soas/appliances/soas3-20090807.zip Thanks and happy testing, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] Snapshot shipping Sugar 0.85.2
Sebastian Dziallas wrote: Hi everybody, we've a new snapshot ready for you including the latest Sugar 0.85.2 release (except etoys, which is still being packaged). Also, this release ships now with the firstboot wizard, as discussed during FUDCon. The latter one allows you to change your keyboard settings before logging in, as well as to submit your hardware profile information using smolt. More information will follow soonish. Also note that we've pulled the latest activity release from a.sl.o, which should fix some bugs. Finally, here are the links: http://download.sugarlabs.org/soas/snapshots/3/SoaS3-200908072039.iso http://download.sugarlabs.org/soas/appliances/soas3-20090807.zip Looks like I'm shooting out announcements too quickly! So here's the thing: We'd like to evaluate new possibilities of gathering feedback and Luke has kindly set up an instance to do so (as discussed on IAEP). So if you've any general feedback, issues or ideas, you could start using it. Please report how it worked for you and what you think. Here's the link: http://getsatisfaction.com/sugarlabs Thanks and happy testing, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Artwork Request for SoaS: Firstboot Theme
Hi everybody, as I've recently mentioned on-list SoaS now ships firstboot, which is a tool to configure some system-related stuff at... well, first boot! ;) So as this is usually quite Fedora-branded and since we aren't able to ship that trademarked logo, it would be great if we could get some Sugar branding here, just like for the boot screen. Basically, we'd need some .png files for that. To see what's exactly needed, you can download the latest snapshot and check the /usr/share/firstboot/themes directory, or you can grab the generic-logos package from here: http://koji.fedoraproject.org/koji/buildinfo?buildID=101905 The following three files are concerned: * firstboot-left.png * splash-small.png * workstation.png It would certainly be great to get this done in time for the SoaS v2 Beta Release at the end of August... Cheers, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Who's interested in testing a new installer for SoaS?
Hi everybody, I'm looking for some volunteers to test the hard disk installation with the latest SoaS snapshot and newly designed installer. Since this upstream project is really in the early stages of development but also concerns a pretty critical part of SoaS, I'd prefer getting some testing before throwing it in a snapshot and possibly breaking stuff. If you're interested and aware of the risk, please drop me a line. Thanks, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] SoaS with SD cards irregularities
Sascha Silbe wrote: On Fri, Aug 07, 2009 at 09:11:31PM +0930, Bill Kerr wrote: The sticks I have with SD cards have started to fail on the older computers at school (after working ok for 2 weeks of lessons). But they still work fine on my newer Dell mini inspiron. The older ones are not XOs, right? Warning: cannot find root file system Can you append rootwait (without the quotes) to the kernel parameters, please? I hope Sebastian can give specific instructions how to do this interactively for SoaS. I'll try to! :) When you boot SoaS, you'll see a blue screen for one second - press escape there quickly - you'll be presented a menu saying in its first entry boot. Press tabulator there. You can now modify the kernel arguments (add rootwait) and boot by pressing enter then. This will add it only once, though. Usually, one needs to edit /etc/grub.conf to makesuch a change persistent, but I seem to recall that this didn't work in live images lately... --Sebastian CU Sascha ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [SoaS] Major Changes in the latest Snapshot
Hi everybody, I'm very happy to announce the availability of a new SoaS snapshot, today now especially with the latest Sugar release 0.85.3, freshly off the press (thanks to all the devs packagers here)! This release includes a number of new features, awaiting to be tested! * SoaS switches to a new distribution method for Fructose activities, meaning that now *all* activities can be directly updated from activities.sugarlabs.org without issues. * Official appliance creation has been resumed (we ship a zipped .vmdk file which should be readable by all major virtualization products). The appliance includes now all activities, all locales, and even sample content - just like the original SoaS! * This release introduces a new display manager, to be more specific olpc-dm, which should auto-login the user, even after restarting Sugar from the control panel. No blue login screen anymore! * SoaS ships now with capabilities of using sudo - by default! * The SoaS build date will from now on be clearly printed in the control panel (in the About my Computer screen). That's it so far. Now here are the links: http://download.sugarlabs.org/soas/snapshots/3/SoaS3-200908021950.iso http://download.sugarlabs.org/soas/appliances/soas3-20090802.zip Known bugs include a killed X server each time an activity saves to the journal. Please report all other issues you encounter (and note the build date when opening a ticket please)! Thanks and happy testing, --Sebastian for the SoaS Team ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Call for Help: SoaS Display Manager (Auto-Login)
Tomeu Vizoso wrote: On Fri, Jul 31, 2009 at 16:48, Sebastian Dziallassebast...@when.com wrote: Hi everybody, I could use a hand with auto-login on SoaS. We've been using slim so far but will switch in the near future (in fact, I already committed a change in GIT), as we also need to login automatically after killing / restarting X. Therefore, the most feasible solution seems to be olpc-dm from the olpc-utils right now. Unfortunately, I haven't been able to get it successfully to work and am lost with a black screen on tty1 so far. Looking at /var/log/message, the following stuff seems spurious: olpc-dm: Can't get tty name: inappropriate ioctl for device init: prefdm main process terminated with status 1 The occurs quite a few times and running initctl start prefdm manually from the console also gives a prefdm respawning too fast. On the other hand, running olpc-dm directly as root works, though. If anybody has an idea how to fix this, meaning to get auto-login to work again, any help is greatly appreciated. We can also provide the current snapshot pre-built as an .iso file, if required. Feel free to contact me directly, too. So did you got this working by yourself? Yup, fixed! :) Thanks, --Sebastian Regards, Tomeu Thanks, --Sebastian Dziallas for the SoaS Team ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Devel mailing list de...@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Call for Help: SoaS Display Manager (Auto-Login)
Hi everybody, I could use a hand with auto-login on SoaS. We've been using slim so far but will switch in the near future (in fact, I already committed a change in GIT), as we also need to login automatically after killing / restarting X. Therefore, the most feasible solution seems to be olpc-dm from the olpc-utils right now. Unfortunately, I haven't been able to get it successfully to work and am lost with a black screen on tty1 so far. Looking at /var/log/message, the following stuff seems spurious: olpc-dm: Can't get tty name: inappropriate ioctl for device init: prefdm main process terminated with status 1 The occurs quite a few times and running initctl start prefdm manually from the console also gives a prefdm respawning too fast. On the other hand, running olpc-dm directly as root works, though. If anybody has an idea how to fix this, meaning to get auto-login to work again, any help is greatly appreciated. We can also provide the current snapshot pre-built as an .iso file, if required. Feel free to contact me directly, too. Thanks, --Sebastian Dziallas for the SoaS Team ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Marketing] press release opportunity...
Caroline Meeks wrote: On Wed, Jul 29, 2009 at 9:14 PM, Gary C Martin g...@garycmartin.com mailto:g...@garycmartin.com wrote: On 29 Jul 2009, at 21:35, Walter Bender wrote: Begin handwaving. LiveUSB came from the world of LiveCD and with it came an overlay concept to enable writing in what had been a read-only world. It is not clear that the approach was intended for more than demonstration purposes, in order to show off the power of Fedora Linux. That would suggest that in the long run, we may need to revisit the way in which we manage user data on our images. End handwaving. +1 My gut feeling is we don't want a LiveUSB, we want a bootable USB with a regular install on it. Ideally being installed from a LiveCD, that can either directly boot and demo Sugar, install to a USB stick, or install to a hard-disk. Once booted we'd want the minimum of file writes to maximise a stick lifetime, and reduce the chance of a write landing as a child unplugs. Regards, --Gary +1 except I think that we need it sooner not later. It is the most likely suspect on most of our stick failures. We will have upset teachers and kids if its not more reliable plus added expense and time costs. It is a blocker on: * Reading things you've created on your Sugar Stick on a Windows or Mac machine. * Createing a VM that can switch stick based users without rebooting out of the native OS- This will help usability quite a bit on the Mac Laptops the GPA will be using next year. I'm going to try to create a spec and publicize our need for help to my network. I'd love help with both parts of that. I'll throw my two cents in here, too. I agree with Walter that we might need to revisit the whole concept in the long term. However, it's probably the best we can get right now. Let me put it this way: Looking at my recent composes for SoaS, those were around 390 MB. This contains the compressed squashfs image. Because of this compression, it's read-only, but it's also that small. Now in comparison, we could obviously place the whole file tree on a USB key and hack up some magic to make it boot. In fact, that's from what I see already the somehow preferred way used for the XO. But for this, we'd also need to have the file tree uncompressed (since otherwise it would be read-only again). And that could become a problem. The compression works rather well for us, so if we'd try to go this way, we'd definitely need to move the USB key size requirement up (at least 2 GB, if not even more). And then, I'm not really sure if this solves the data corruption issue (which I haven't experienced myself, so far) - because files could get destroyed if the USB key is improperly removed anyway. Caroline, maybe you could explain the way you're using to make these keys, because I've lost track about what the current way is. Regarding reading contents one created in Sugar on Windows / Mac, I think this is still quite some time away. In fact, I'm wondering whether this isn't a datastore related feature. /me thinks about this... Cheers, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar on HP Mini 110
Philippe Clérié wrote: Fedora 11 works just fine. As soon as I've resolved my wireless problem (the Mini 110 uses a Broadcom chip and I missed that before placing the order.) I'll install Sugar and give that a try. Hi Philippe, thanks for your continuous tries and reports here - those are very helpful! We definitely have improving the user experience here on the list for the SoaS v2 release. In fact, if everything goes well, we might be able to feature a complete installer. Thanks, --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Test the POSSE Education Fedora Remix today!
=== Test the POSSE Education Fedora Remix today! === Have you ever wanted to contribute - or get others to contribute - to an open source education project, but never found the time to set up and get started? We've got a ready-to-go contributors' (not just code!) environment for you. The Fedora Education SIG (http://fedoraproject.org/wiki/Education_SIG) announces today in cooperation with POSSE (http://teachingopensource.org/index.php/POSSE_2009), a Red Hat sponsored summer program to introduce professors to the open source way of development, the release of the POSSE Education remix. The remix will be deployed immediately to the professors at POSSE and has been developed with the purpose of creating a ready-to-go development environment for contributing to educational projects inside, but also outside of the Fedora ecosystem in mind. It contains development environments, tools, documentation, and getting-started resources for contributing to a number of projects including Fedora, Mozilla, Sugar Labs and KDE Education and can be used by individuals or by teachers, students, and classrooms that want to contribute to open source projects as part of their course effort. The download is directly available, together with the SHA-1 checksum, over HTTP from here: http://alt.fedoraproject.org/pub/alt/remixes/POSSE/POSSE-Education-1.iso 391a0170e09e68142cbe2c95b62b2b0c6fa628d5 POSSE-Education-1.iso Being based on the latest Fedora release, this remix provides users with a stable environment with supplemental features, such as: * an easy starting point into educational open source projects by providing pre-selected bookmarks and related IRC channels * the Sugar Platform (http://www.sugarlabs.org), as seen on the OLPC - as of 2009/07/15, all required dependencies for building sugar-jhbuild, a way of pulling and running the latest sugar bits, are included * a number of educational applications, such as the KDE Education Packages (http://edu.kde.org) or software for numerical operations - a Moodle session (http://www.moodle.org) to showcase an open source learning management system * a whole development environment including gcc, python and more, as well as Fedora's packaging tools - the Eclipse environment with plugins for Python and RPM, but also LaTeX and documentation purposes A getting started guide is also available and contains instructions for various applications and communities: https://fedorahosted.org/education/wiki/GetStarted If you are interested in getting in touch with the developers, other users or would just like to submit feedback, please join our mailing list here: http://www.redhat.com/mailman/listinfo/fedora-education-list. If you are interested in using this for your own development or in your classroom, or have an open source education project you'd like to see included in the next version, please let us know and we'll get you started. If you report bugs in bugzilla, please make sure to make them depend on our tracker: http://bugzilla.redhat.com/show_bug.cgi?id=EducationTracker Thanks, Sebastian Dziallas for the Education SIG ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] SoaS Meeting TODAY at 10.30 EDT
Sorry for the short notice, but please join if you can. That's in half an hour from now! Topics will include the roadmap features for v2. --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] SoaS Meeting TODAY at 10.30 EDT
Well, that's certainly understandable, given that I rushed the whole thing quite a bit. 30 Minutes is not that much time... ;) Fred was still quicker with posting the logs... thanks! --Sebastian Peter Robinson wrote: Hi Sebastian, Sorry I missed this one. Will the minutes be published anywhere? Peter On Mon, Jul 13, 2009 at 3:01 PM, Sebastian Dziallassebast...@when.com wrote: Sorry for the short notice, but please join if you can. That's in half an hour from now! Topics will include the roadmap features for v2. --Sebastian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Bug tracker enhancements
Bryan Berry wrote: On Thu, 2009-07-09 at 07:45 +0200, Simon Schampijer wrote: Hi, Our current trac instance is missing some basic functionality: - versions per component: a really simple enhancement would be to have a text field (maybe some versions (sugar core) you can select from) but that we do not have to keep the list updated for each activity - milestones should be on a component basis as well (similar to versions) - I want to make certain fields only being available with certain permissions (a milestone and priority can only be set by the mainteiner, the severity by the bugsquad (see new fedora policy)) Can u provide me a link to the policy? Is this what u r referring to http://fedoraproject.org/wiki/Security/TrackingBugs I think Simon was referring to this one: https://www.redhat.com/archives/fedora-devel-announce/2009-July/msg1.html --Sebastian - having a clear separation from the Soas component - if we have the things from above this is maybe not as critical, otherwise I would suggest to get a new instance for Soas Can someone help to get there? Is trac giving us that functionality? Other trac software we should consider (besides bugzilla :)? Thanks, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Backup and Restore Feature added to Wiki
Dave Bauer wrote: On Tue, Jul 7, 2009 at 10:21 AM, Tomeu Vizosoto...@sugarlabs.org wrote: On Tue, Jul 7, 2009 at 16:05, Greg Smithgregsmit...@gmail.com wrote: Hi All, I created a Feature request for backup and restore here: http://wiki.sugarlabs.org/go/Features/Back_Up_and_Restore Shouldn't this be already working in SoaS 0.84 with XS 0.6? May be waiting for someone to give it a tray. CC'ing Martin and Dave who may have already tried it. We need 1) changes to allow registering soas to an XS 2) ds-backup-client patched to work on soas 3) ds-backup-client installed on soas. I believe there are outstandings tickets for this. I guess these changed need to be made in the fedora packages so we can pull them into soas. Yup, there's a ticket: #916 Well, the problem is that ds-backup-* hasn't been packaged for Fedora, yet. I discussed this with Martin Langhoff (adding to CC here) at LinuxTag lately, and it shouldn't be a big problem to get the patches from Hamilton (in the ticket) applied and then a new RPM uploaded to our SoaS yum repo. I guess we'd need people testing this once it's ready, though. --Sebastian Dave Regards, Tomeu I'm still not sure how to tie it to GPA or a release or pile of pending feature requests. If anyone knows the right wiki markup to do that, please go ahead. I'll watch what you do and use it for the next one. I made myself the owner but it should probably be someone smarter than me and able to program, maybe Martin...? Any comments or questions on the feature are welcome. It occurred to me as I was writing it that this problem must have been solved already in Linux. If anyone knows a good solution there, lets take it! That will solve most of the problem leaving us with the special case of the DataStore/Journal. Comments on format and more accurate filling out of the template also appreciated. From this list http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Goals, I'll work on collaboration next. That is such a tough nut that I may fill in a few priority B items too for practice. HTHs. Thanks, Greg S ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Marketing] [SoaS] The next Step: v2 Roadmap
Greg Smith wrote: Hi Tomeu, Looks great! You guys are really cranking. Three questions: 1 - Where do I see all the Features that have been proposed, regardless of target release? Speaking for SoaS? Heh. ;) I tried to list some under Preliminary Features (v2) on the Roadmap page. Then there's the Goals page with the thoughts from Caroline. And finally, this is where the proposals should go (thanks to Fred for setting it up): http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Proposals 2 - Can/should we add a section/tag to tie features back to real deployments? I'd like to see exactly which user or school needs each item and keep tabs on where and when they will use it. That's probably the direction Caroline started with the GPA pages... +1 for the section / tag idea :) 3 - Should I create Feature Template pages for the Priority A items from Caroline's list? They are a little high level and some may be bug fixi work instead of new features. I'm open to any suggestions on how to start tracking these items: http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Goals in way that's useful for you. That would be awesome! Would be really helpful to get an idea of what is needed and what still needs to be done to get there. If you are open to some churn as I get my style back in synch w/Simon, I'll start filling out Feature Templates ASAP. :) --Sebastian BTW: Good to have you here... Thanks, Greg S On Mon, Jul 6, 2009 at 10:04 AM, Tomeu Vizosoto...@sugarlabs.org wrote: On Mon, Jul 6, 2009 at 16:01, Greg Smithgregsmit...@gmail.com wrote: Hi Sebastian, Fred, and Caroline, This looks like a very useful thread on the Sugar Roadmap and I like the focus on Customer requirements. How do we get the GPA Sugar goals Caroline enunciated on to the main Roadmap? I added a link on the GPA page to the Fred's Sugar on a Stick Goals page. Hopefully we can find a place to collect a Backlog, as they say in Agile. http://wiki.sugarlabs.org/go/Gardner_Pilot_Academy#Sugar_Feature_Requests It would be great to flesh out each GPA item with use cases and work flows, then software design proposals and eventually links to source code. The features should also be parsed down to smaller tasks ala Agile. FYI, Last year, S Page built and I populated a Semantic Wiki Roadmap Collection and Prioritization tool for the XO. See: http://wiki.laptop.org/go/Feature_roadmap I'm not sure if the Semantic Wiki format can be moved to the Sugar wiki or if there is interest in tracking the Sugar roadmap that carefully. The Semantic format was a huge time saver once it was implemented. IMHO its critical to minimize the coordination overhead and maximize the coding time. That said, discussion of what is important and why goes a long way to making better releases. I'll try to chip in by picking up items Caroline marks Priority A, adding details to them, tracking them on the roadmap and looking for programmers to come up with options for implementation. Hi Greg, Simon is working on adapting Fedora's feature process to Sugar, what do you think of it? http://wiki.sugarlabs.org/go/Features/Policy Regards, Tomeu Thanks, Greg S ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
