Re: [Sugar-devel] [RELEASE] TurtleArt-71
On 10/02/2009 01:15 AM, Walter Bender wrote: more sample Python code Is this a bugfix? There should only be bug fixes in releases going into 0.86.x Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Namespace for 0.84 updates to Browse and Chat?
Hi Tomeu (and others), On Wed, Sep 30, 2009 at 06:48:05PM +0100, Tomeu Vizoso wrote: sorry for the late reply, this is a very good question. I think we should move to dotted version numbers for activities in 0.88, maybe interpreting a version number without a dot as 0.xx. For now and for your specific use case, what about preppending 0.84/0.86 to the activity version number? Debian supports resetting version numbers, but it may cause problems for other distributions if Sugarlabs start releasing new packages with _lower_ version numbers than the older ones. As an example, are you sure that your Mozilla web interface supports resetting version numbers? Do the install mechanisms in Sugar itself? - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature ___ 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
Re: [Sugar-devel] Xoos Special Interest Group
The core focus of the Sig is to be an upstream for the the deployment releases. My guess is that while the project is not identical to either Sugar on a Stick, or Martin's work on making the sugar on a Stick run on the XO, we will have a very significant code overlap. I am planning on starting from Steven M. Parrish's F11 on XO1.5 tree and seeing what happens. david On Fri, Oct 2, 2009 at 5:04 PM, Sebastian Dziallas sebast...@when.com wrote: 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
Re: [Sugar-devel] [SoaS] Where should we put our mixture of bugs, feature requests and misunderstandings as we develop curriculum
Also, as a developer I would need to see a list of the features and bugs most requested by deployments, and which deployments need them. It will be also useful when asking for help and recruiting more volunteers. Yes, exactly. We need a way for individuals to contribute individually to this. We need a system that is tolerant of bad reports, supports peer-to-peer problem solving, and creates a pattern of data and feedback that can be fed back upstream. I'm just not sure how to create this yet, if you have ideas on implementation please let me know. I am leaning towards Launchpad and I also will talk to Adam Holt about his experiences and how we can work with the support gang. Regards, Tomeu -- «Sugar Labs is anyone who participates in improving and using Sugar. What Sugar Labs does is determined by the participants.» - David Farning -- Caroline Meeks Solution Grove carol...@solutiongrove.com 617-500-3488 - Office 505-213-3268 - Fax ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Display a message when an activity fails to start
http://dev.sugarlabs.org/ticket/1447 Would love to get some testing on the latest patch! There was an occasional crash bug but it seems to be fixed now. Just make your activity fault during launch and see what happens. Thanks, Wade ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Karma] State of Chakra and knavbar
sorry i keep missing u on irc I have investigated using E4X for knavbar but unfortunately only firefox supports E4X. webkit doesn't and has no plans to. It does appear there are a couple other decent options I am playing with jqote and PURE http://aefxx.com/jquery-plugins/jqote/ http://beebole.com/pure/ PURE looks the most promising I will play w/ PURE more tomorrow hopefully I have looked at your latest changes, looks good! We need to split out the css selectors general to all of karma to karma.css and that specific to chakra to chakra.css. Currently, karma.css does very little :) On Fri, 2009-10-02 at 23:34 +0100, Pavel Mocan wrote: I made a few changes to the html and css. I wrote a couple of comments in the commit message on git, might worth taking a look. I should be online tonight (night for me), so ... talk to you soon if you will be. Pavel Mocan -- Bryan W. Berry Technology Director OLE Nepal, http://www.olenepal.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
