Re: [IAEP] Renaming the Telescope activity to Scope
Am 20.11.2012 um 06:23 schrieb Martin Langhoff martin.langh...@gmail.com: On Mon, Nov 19, 2012 at 11:58 PM, Chris Leonard cjlhomeaddr...@gmail.com wrote: As I recall, this activity was already renamed once from xoscope after it became clear it was colliding in name space with an oscilloscpe activity. Renames are a pain in infrastructure, and in upgrade handling for users. I would say prefer to retain the current name until there's an overwhelming case for change. Agreed. A rename should be well thought through. If you do it, agreed with what Chris said, please use a cerb. Thanks, Simon cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list de...@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Sugar Labs service outage: Thu, Sep 20 9:30-12:30 EDT
Yay! Thanks Bernie and everyone involved. You are the basis of our lab - kudos to the infra team! Simon On 09/20/2012 06:37 PM, Walter Bender wrote: On Thu, Sep 20, 2012 at 12:34 PM, Bernie Innocenti ber...@codewiz.org wrote: We're back in business. Let me know if anything didn't come back online. thx -walter On Thu, 2012-09-20 at 00:26 -0400, Bernie Innocenti wrote: Tomorrow, Thursday 20 Sep 2012, between 9:30 and 12:30 eastern time, the Media Lab sysadmins will reconfigure the rack in room E15-243. During the maintenance work, the following services hosted on treehouse.sugarlabs.org may become temporarily unavailable: - git.sugarlabsa.org and all related services - chat.sugarlabs.org - jabber.sugarlabs.org - meeting.sugarlabs.org - network.sugarlabs.org - obs.sugarlabs.org - rt.sugarlabs.org - schooltool.sugarlabs.org - ns1.sugarlabs.org (primary nameserver for multiple domains) - Various services related to ole.org - Various services related to paraguayeduca.org - Various services related to treehouse.su - Others I might have missed We'll use this opportunity to rack our two new servers and prepare them for production. -- _ // Bernie Innocenti \X/ http://codewiz.org ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Sugar as a Mac Ap?
The question is what you refer to when you talk about Sugar. The concept of an app is similar to the concept of an Activity in Sugar. If you want to bring educational material to the ipad you have to look at specific Apps like 'Move the turtle' which is similar to Turtle Art. 'garageband' is another one interesting for older kids. Regards, Simon Am 13.06.2012 um 07:50 schrieb Steven Thompson steven_sen...@yahoo.com: Even just in English in Japan could help kids. The common denomenator for jhs and hs kids is an iPhone or android and the iPad at home...much more so than buying an Intel Classmate or having a hope of getting an XO. It's not about price or energy requirements here, its about good education for kids. Can we get sugar as a Mac Ap at the Ap Store? From: Chris Leonard cjlhomeaddr...@gmail.com; To: Steven Thompson steven_sen...@yahoo.com; Cc: Walter Bender walter.ben...@gmail.com; community-n...@lists.sugarlabs.org; iaep@lists.sugarlabs.org; sugar-de...@lists.sugarlabs.org; Subject: Re: [IAEP] Sugar as a Mac Ap? Sent: Wed, Jun 13, 2012 1:10:09 AM On Tue, Jun 12, 2012 at 9:05 PM, Steven Thompson steven_sen...@yahoo.com wrote: Thank you all in this community for your creative dedication. I am considering using sugar for my 4 year old daughter and her friends. Parents have access to iPads. We are in Osaka Japan. Can Sugar be used on an iPad? If not does anyone have any suggestions for getting a group if Japanese kids involved? The benefit of the tablet us that very strong cases can be easily purchased for kid use. Why buy an Intel Classmate when we already have iPads lying around! All suggestions welcome, Steven Dear Steven, One of the first things that is needed is more complete Japanese localization. http://translate.sugarlabs.org/ja/ cjl Sugar Labs Translation Team Coordinator ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] reporting simple error on pippy 42
On 10/05/2011 11:45 AM, Carlos Rabassa wrote: Gonzalo Could it be the translator decided to avoid Pippy, thinking it is too close to pipí, the Spanish-Baby-talk word for urine? Correct this was the idea, back then. Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] Gtk3 Hackfest, Praha 2011, news updates
Hi, two major changes have recently occurred in Sugar's underlying technologies. Firstly, GTK+ 2 has been obsoleted by GTK+ 3, and GNOME is now based on GTK+ 3. Secondly, PyGTK, the underlying Python library that Sugar uses to call into GTK+, has been deprecated in favor of PyGObject Introspection (hereafter PyGI). More background info can be found at Features/GTK3 [1]. Goal of this hackfest is to remove the biggest blockers before we can start the porting and potentially start porting over. == Sponsoring regional trips == This Hackfest is sponsored by the OLPC Foundation. If you need help for funding your travel, please send an email to simon AT laptop DOT org before the 8th of October 2011. OLPCF won't be able to refund more than 150 USD per trip, and we will fund regional (european) travels in priority [2]. Regards, Simon [1] http://wiki.sugarlabs.org/go/Features/GTK3 [2] http://wiki.sugarlabs.org/go/Marketing_Team/Events/Gtk3_Hackfest_2011 [3] http://brmlab.cz/| ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] A question about adult education in Uruguay
On 06/22/2011 09:25 PM, Alan Kay wrote: Hi folks, I posted the Ceibal video to Mark Guzdial's blog ... and here is a question from it that seems interesting and important (I'd like to know also). On a related topic, does Uruguay have anything like free online courses for adults, perhaps available in public libraries? Cheers, Alan Hi Alan, there are two portals that I am aware of: Uruguay Educa [1]: educative material for teachers, school children and parents Plan Ceibal Portal [2]: material for the use with the XO for teachers, school children and parents Regards, Simon [1] http://uruguayeduca.edu.uy [2] http://ceibal.edu.uy ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] OLPC OS 10.1.3 final release
Dear olpc community, we are very pleased to announce build os860 as the final 10.1.3 release build for XO-1 and XO-1.5 laptops! This is an update to software release 10.1.2 that fixes important bugs and includes some new improvements (listed at the bottom of this mail). The release is based on Fedora 11 and contains the latest Sugar 0.84 and the GNOME desktop. The full release notes can be found at [1]. Instructions for installing the release on an XO can be found at [2]. Many thanks to everyone -- testers, translators, documenters, developers and others -- who contributed to this release! On behalf of the OLPCA-team, Simon [1] http://wiki.laptop.org/go/Release_notes/10.1.3 [2] http://wiki.laptop.org/go/Release_notes/10.1.3#Installation ==New features== ===Collaboration under a tree on XO-1.5=== We have significantly improved collaboration when XO-1.5 is used with no Access Points available (under a tree). The Neighborhood View now shows three default Ad-hoc networks (for channels 1, 6, and 11) in user-friendly icons, and XOs will auto-connect without user intervention. This behavior is similar to the mesh behavior on XO-1. ===Sharing/Backup Journal entries using a mass storage device=== You may now share Journal entries with another learner using a [[USB drive]] or SD card. The user experience is: Martin wants to give a picture he has been drawing to Simon. He plugs in his USB drive and copies the Journal entry on the drive. Simon plugs in Martin's drive in his laptop. The entry will be shown with Martin's XO color on the drive. Simon copies Martin's entry into his Journal. You can use this feature to backup Journal entries to a USB drive or SD card. ===Connect your XO to external projectors and monitors=== We have added support for USB2VGA adapters. You can now connect an XO to a projector over a USB2VGA adapter and project what is on your XO screen onto a screen or for many people to see. ===Screen Rotation on XO-1.5=== On XO-1.5 it is now possible to rotate the screen using the 'rotate' button. This allows learners to use the XO in ebook mode. ===Protected Activities Support=== In this build certain activities are protected from being deleted by accident. In the activity list in the home view the erase option is disabled for those. Protected activities are: Browse, Terminal, Log, Write, ImageViewer and Record. ===Better interaction between GNOME and Sugar=== Switching between Sugar and GNOME user interfaces is smoother. Changes of settings in GNOME now do not affect Sugar, and vice-versa. The ~/Activities directory is now hidden from the user in GNOME, to prevent accidental deletions that could harm Sugar. The networking settings are now synchronized so enabling/disabling networking is unified. Users can now change GNOME panels and fonts without risk of breaking GNOME -- invalid settings are reset on restart. The dialog to set a GNOME keyring password when connecting to a secure wireless network has been disabled. ===Browse=== A home button has been added into the Browse toolbar. The button returns to the home page, where important links are. A busy cursor has been added for when a page is loading. This was present in 8.2.1 but missing from 10.1.2. Finally, previews for downloaded images have been added, so that the Journal will show appropriate thumbnails of downloaded images. ===Paint=== The Paint activity has been improved a lot: * The cursor has been enhanced and realigned, * Text tool has been improved * New filters: invert colors and mirror effects * Tool size and shape are shown * Improvements to copy and paste ===Read=== Scrolling has been improved. The up and down directional keypad to the left of the XO display will now scroll, which is especially useful if the laptop is in ebook mode. Using the fn key with the up and down arrow keys will now scroll by page. ===Write=== You can now paste images into Write. Images can be copied from Browse, Paint or Write. You can now put images into tables and export to PDF. The style list has been reordered to place paragraph text styles before heading styles. ===Wikipedia=== Page loading has been sped up and several smaller fixes made. ===Scratch=== A new camera plugin adds importing from camera on XO-1. ===Activity Updates=== We included the latest versions of Calculate, Colors, Distance, Etoys, Help, InfoSlicer, Jukebox, Labyrinth, Memorize, Physics, Pippy, Turtle Art and Typing Turtle. ===System Lid Behavior=== When the lid is closed on the XO, the laptop will suspend its operations and turn off the screen. Historically re-opening the lid has turned on the screen and woken up the laptop for normal use. In order to avoid a problem where stacked XO units may accidentally turn each other back on, this wake-up behavior has been disabled. To wake up the laptop from suspend press the power button once. ___ IAEP --
Re: [IAEP] Moon Activity Has an Easter Egg!
On 12/21/2010 05:55 PM, Caryl Bigenho wrote: Hi All It was very rainy last night during the lunar eclipse so it wasn't visible here in SoCal. I decided to look at the Moon Activity instead. The moon was a rosy, pinkish color much like it sometimes appears during totality! This morning it was back to black white and shades of gray. Want to see it for yourself? You will have to wait about 6 months until June 15, 2011. Caryl I actually saw it, since a learner in class opened the activity this morning :) Cheers, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] stepping down as maintainer
On 10/19/2010 06:50 PM, Tomeu Vizoso wrote: Hi, for personal reasons have to drastically reduce my involvement in the project. Will be leaving maintenance of my modules and unsubscribing from the mailing lists. My place on the board is vacant from now on and I'll be adding to the wiki the new vacancies: http://wiki.sugarlabs.org/go/Vacancies Cheers and good luck, Tomeu Thanks for all the great work you have been doing over the last years! Good luck to you, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] Sucrose 0.90 Final Release
Dear Sugar community, Sucrose 0.90 is the latest version of the Sugar learning platform: Sugar promotes collaborative learning through Sugar Activities that encourage critical thinking, the heart of a quality education. Designed from the ground up especially for children, Sugar offers an alternative to traditional “office-desktop” software. Furthermore it provides a flexible and powerful platform for activity developers. Sugar is Free and Open Source Software and consists of Glucose, the base system environment; and Fructose, a set of demonstration activities. This new release contains many new features, performance and code improvements, bug fixes, and translations. Full release notes can be found at: http://wiki.sugarlabs.org/go/0.90/Notes Thanks everyone for your great contributions! On behalf of the Sugar community, Your Release Team ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Introduction
Hi Steven, On 09/28/2010 01:00 PM, Tomeu Vizoso wrote: On Tue, Sep 28, 2010 at 12:46, Steven Parrishsmparr...@gmail.com wrote: Some of you may have already heard that I have accepted a position with ActivityCentral to be the project manager for Dextrose. It feels like I have come full circle as I started out as a volunteer maintaining the F11 for the XO-1 builds for the past 18 months. That work was very rewarding and I was glad to see OLPC step in and release official builds based on my work. The F11 for the XO-1 was also a starting point for the original Dextrose system, which Bernie Innocenti brought to fruition. Now we will be taking the original Dextrose and expanding upon it. Dextrose2 will be the result. Based on Fedora11 and Sugar 0.88 it will strive for stability, while providing deployments with a customizable product. I have already started creating builds for the new system with additional language support, and they can be found at http://wiki.sugarlabs.org/go/Dextrose . The builds will be for both the XO-1 and XO-1.5 and will be available both with Gnome and without. We have a team of developers at SEETA who will be working on this with us. Many of them are already known to the community and more will become known as they join the effort. I have already started going over the outstanding issues and know that with everyone's help we can make Dextrose the Premier system for XO deployments. The issues that need to be worked on can be found at: http://bugs.sugarlabs.org/query?status=acceptedstatus=assignedstatus=newstatus=reopenedorder=prioritycol=idcol=summarycol=statuscol=typecol=prioritycol=milestonecol=componentkeywords=$love and http://bugs.sugarlabs.org/query?status=acceptedstatus=assignedstatus=newstatus=reopenedorder=prioritycol=idcol=summarycol=componentcol=statuscol=typecol=prioritycol=milestonekeywords=$extrose If you are already working on any of these tickets please send me a quick note as to which tickets you are working on and what the status is. I look forward to working with everyone. I'm very happy to read this, look forward to work further with you. It would be very helpful if any new contributors could take the time to present themselves and their plans as you have done. Regards, Tomeu Thanks for your great introduction. It is a good habit to present oneself and his role to the community. I would like to encourage others to do so as well. Looking forward to work with you, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] Sucrose 0.89.6 Development Release (Release Candidate)
Dear Sugar Community, This is our development release number 6 in the development cycle [1]! This is our Release candidate! We now entered Hard Code Freeze. When the hard code freeze is in effect, each and every code change should be approved by the release team. Only critical fixes will be considered. To request approval send mail to sugar-de...@lists.sugarlabs.org, including the patch and a detailed description of the changes, the benefits and the risks. Approval will have to be granted by two members of the team. There will be a bug fix release at the end of October, so all the other bug fixes which are not considered for the release can go in there. Full release notes can be found at [2]. Thanks everyone for your great contributions! In behalf of the sugar community, Your Release Team [1] http://wiki.sugarlabs.org/go/0.90/Roadmap#Schedule [2] http://wiki.sugarlabs.org/go/0.90/0.89.6_Notes ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Child in charge of FOSS or Sugar
On 09/18/2010 04:01 AM, Martin Langhoff wrote: On Fri, Sep 17, 2010 at 9:27 AM, Søren Hougesen soren.houge...@gmail.com wrote: For about a month ago, I asked as a curious outsider, if kids were actually hacking sugar. Two factors are important here: - We all have very high and complex expectations for Sugar, so Sugar itself is internally complex; and that trend is increasing. So to actually hack in the core of Sugar you have to make a long trip of discovery and learning. (Activities are a lot easier to hack.) Yes there are Activities that are low floor and you can more or less easily do new frame devices and control panel extensions. - Sugar (and XOs) have not been in use for long enough! Sugar users have only started their journey. Will they travel all the way to hacking Sugar? Hard to know! If they are working on TurtleArt / TurtleBlocks, EToys, Scratch or Pippy, they are on the right track. Yes, I think already having TA and Pippy gives you a very good introduction to the concepts of 'thinking like a programmer'. From my experience in class these work really well as well. Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [MARKETING] Get Sugar landing page
Hi Walter, first of all - thanks for your efforts! On 09/15/2010 03:25 PM, Sascha Silbe wrote: Excerpts from Walter Bender's message of Tue Sep 14 18:30:54 +0200 2010: I've been doing some work on the Get Sugar landing page in the wiki, which has been the source of some confusion amongst our potential user community. My proposed modifications (See http://wiki.sugarlabs.org/go/User:Walter/Get_Sugar) are an attempt to streamline and consolidate the instructions for first-time users. I'm missing the mention of distro packages. For existing Linux users, this is the easiest way to run Sugar. I actually thought the same thing. I think this should be more prominent in the page that you can just install the distro packages. At the moment it rather reads like this is only meant for developers. Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Sugar Labs page Deployment Team/Places has been changed by Bernie
On 09/07/2010 09:43 AM, Tomeu Vizoso wrote: Hi, Bernie has updated the page in the wiki that lists known Sugar deployments, please update it if you have more information: http://wiki.sugarlabs.org/go/Deployment_Team/Places Regards, Tomeu Done, thanks Bernie for working on this. Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Proposal release management
On 06/24/2010 09:37 PM, Martin Langhoff wrote: On Thu, Jun 24, 2010 at 2:05 PM, Michael Stonemich...@laptop.org wrote: Perhaps we should instead be talking about whatever role describes the people who /do/ care about the code that goes in? Programmer. Implementor. Product manager. :-) I think the view is that features have their own drivers (motivated programmers making sure it gets done) the RM keeps things orderly as they get merged or landed into the master branch. The above is just my limited understanding -- proper SLers probably know much better. cheers, m Of course the release manager is interested in having a stable and releasable software at the end of the release cycle. So, he sets the freezing dates and makes sure that those are not violated. The actual code review happens by the module maintainers. They are responsible for the quality of their modules. And for accepting which feature goes in, we have the Feature process [1]. A defined process to make sure people are able to contribute their features in a fair manner. Btw, the basic idea has been adopted from the Feadora Feature process. The idea is: the responsibilities are distributed and handled by the persons with the expertise to do so. In short: the release manager gives a frame for the development cycle and makes sure people are able to contribute in different ways and that at the end of the cycle we have a software that is stable and fun to use. Nothing spectacular, but important to keep the ball rolling. Regards, Simon [1] http://wiki.sugarlabs.org/go/Features/Policy ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Proposal release management
On 06/24/2010 11:49 AM, Bert Freudenberg wrote: On 24.06.2010, at 09:32, Simon Schampijer wrote: Hi, in May I tried to find someone to replace me as release manager [1] for 0.90, but as nobody has stepped up to do the job as we defined it I decided that it will be best to keep this role for some more time. I think it will be important for Sugar that we keep some continuation of the processes that we have been setting up during the last years. It would also be very good if someone would like to lend a hand with this or shadow me for future tasks so more people in Sugar Labs have direct hands-on knowledge. We defined the role of the release manager in the past 3 releases like the following: * setting the schedule * make sure that the Feature process is followed by the submitters [2] * keeping the wiki updated about the released modules and making sure to have final release notes available * sending email reminders about approaching Freezes, tarball due dates etc The schedule would be based on the GNOME releases, a 6 month release cycle. As there is not much time left for 0.90 [3] I think we should mainly focus on stabilizing and landing the features that were left over from the last release. I would start to announce a time frame for future releases so that future development can go on. New Features would be handled by the Feature process, as it has been the case in the past. What do others think about this? I think thanks are in order. It's a solid, low-risk plan for the last mile in our development cycle. Now we just need to get our acts together in covering the middle ground, so you actually have something to release :) To that extent I proposed to the Etoys developers to follow the Sugar development cycle more closely. And that's what we're going to do. Thank you for stepping up again! - Bert - Hi Bert, awesome! Happy to hear that Etoys, a very important part of the Sugar experience, is rowing with us. I like the approach of Etoys to follow the Sugar release cycle. Similar to what Sugar does, we follow the GNOME cycle and they make sure that we are on track with the various distributions. Standing on the shoulders of giants... Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] Proposal release management
Hi, in May I tried to find someone to replace me as release manager [1] for 0.90, but as nobody has stepped up to do the job as we defined it I decided that it will be best to keep this role for some more time. I think it will be important for Sugar that we keep some continuation of the processes that we have been setting up during the last years. It would also be very good if someone would like to lend a hand with this or shadow me for future tasks so more people in Sugar Labs have direct hands-on knowledge. We defined the role of the release manager in the past 3 releases like the following: * setting the schedule * make sure that the Feature process is followed by the submitters [2] * keeping the wiki updated about the released modules and making sure to have final release notes available * sending email reminders about approaching Freezes, tarball due dates etc The schedule would be based on the GNOME releases, a 6 month release cycle. As there is not much time left for 0.90 [3] I think we should mainly focus on stabilizing and landing the features that were left over from the last release. I would start to announce a time frame for future releases so that future development can go on. New Features would be handled by the Feature process, as it has been the case in the past. What do others think about this? Regards, Simon [1] http://lists.sugarlabs.org/archive/sugar-devel/2010-May/023710.html [2] http://wiki.sugarlabs.org/go/Features/Policy [3] http://wiki.sugarlabs.org/go/0.90/Roadmap ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Devel Team vacancies
On 06/06/2010 10:30 PM, Tomeu Vizoso wrote: SeanDaly if tomeu were here, he would say: we need someone experienced, who knows the open source way, and does not need lots of briefing to get up to speed (he will correct me if I err) You can count on me for that :) So the idea of team coordinator is that of someone who takes care for: * keeping the list of team members updated in the wiki, * making sure the mission statement is in sync with the team's activities, * announce and moderate regular meetings and publishing its minutes. So I don't think you need any special skills, just be willing to donate a few hours per month. If we had a community team, we would have a structure for the people who want to work together on such issues ;) cjb (I think the most important job the release manager does is decide whether a late change constitutes acceptable risk, and I think doing that requires deep understanding of programming and the complexity of a given bug/solution.) There seems to be a misunderstanding, maybe because OLPC had a position with the same name (and maybe our use of it is not totally appropriate). In Sugar's case, who decides what goes in and what not is the schedule, the maintainer and the release team, with input from several others. The schedule says what kind of changes can go in at every moment in the release cycle, the maintainer is expected to have enough criteria to classify every change accordingly and the release team votes on exceptions to the schedule. All about releases: http://wiki.sugarlabs.org/go/Development_Team/Release New features process and what is the release manager: http://wiki.sugarlabs.org/go/Features/Policy In this way, the release manager doesn't have as much responsibility as was implied in the meeting but he's mainly responsible for making sure that the process _for proposing new features_ is followed. It's largely an administrative role, but much more exigent than coordinating a team. The reason for having a weaker release manager and relying more on the criteria of maintainers is because by SLs being an upstream these decisions won't affect as directly to our users as downstreams are anyway expected to do integration, testing and maybe some amount of patching after each release is made. For a downstream such as OLPC or Fedora, someone needs to control very strictly what gets in at the end of the cycle because there's more pressure to get stuff in and because once you have sent the image to the factory or have started to seed a torrent it's much harder to go back and fix some bug. In the Sugar case, if a maintainer made a goof and introduced a major bug just before release, it will take some time before the code is packaged, then distributed to testers, then submitted to a stable release that users will use with some expectation of not finding major regressions. It would be great if people could search the wiki before entering in discussing a process or a role, because as you can see from the link above, that took someone quite a bit of time to write and would be sad to waste time discussing something else. Also, the docs in the wiki indeed could be clearer and any help will be welcome. To make it clearer: * the release manager is not needed to make module releases, * the release manager doesn't decide by herself if a change goes in or not, * the release manager makes sure the feature process is followed. Maybe a more appropriate name for what we call the release manager would be new feature process manager but as it's a bit long and we don't have a release manager, we ended up using that name instead. Regards, Tomeu Thanks for taking the time to lay this out as detailed. It is true indeed that the main role of the release manager, as Sugar Labs interpreted that role, was to give a timeframe for the release. The release manager is setting the schedule and makes sure that the commiters are on track. To control which Features will go into a release we have the Feature process [1]. The role of the release manager during the Feature Process is a sanity check, presumed in most cases to be a formality, to ensure that new features compliment Sugar guidelines and is manageable [2]. And if a Feature follows these guidelines there is no reason why it can not go into a release. However, if the Feature is not ready time-wise (Feature Freeze etc) it has to wait until the next release to land. And the code review itself is handled by the module maintainers, like Tomeu described. Regards, Simon [1] http://wiki.sugarlabs.org/go/Features/Policy [2] http://wiki.sugarlabs.org/go/Features/Policy#Acceptance_of_a_feature ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Announcing the Development Team Lead election
On 05/15/2010 06:48 PM, Chris Ball wrote: Hi everyone, Tomeu's stepping down as the Development Team Lead¹, and we'd like to elect a replacement. This is an important position -- the team lead is responsible for setting clear goals for the team, being a responsive upstream for work we receive from the community, appointing a release manager for the next (0.90) release and helping to define its scope, and holding regular Development Team meetings on IRC, including coordination with the Design and Deployment Teams on new features. There are more details on the role and the team here: http://wiki.sugarlabs.org/go/Development_Team Hi Chris, the position as you describe it, seems quite complex. I would make a difference between a coordinator and a leader. The coordinator will make sure there are regular meetings to be held and to give a structure for those and is in contact with the release manager about the schedule. A team can have several leaders, this role is not appointed but comes naturally with the work one has been doing, in my opinion. I don't think the development team lead has to appoint the release manager. From my experience I can say, that I did one release with Marco together and then kept on doing it. Ideally a model where the current release manager is shadowed and then keeps on that task. If we have more candidates that want to fulfill that role, even better, they can share this task. Coordination with the design team is a good point, and the design team coordinator is another critical open vacancy. Last release I did manage that since I was interested in the outcome for the release, though this was not a long term solution ;) And for the general strategy, we have the Feature process [1]. This helps all the deployments and contributors to raise their voice. And if there is consensus in the community the Features will make their way forward into releases. So, we have the processes to move forward, we just have to use them and keep on doing. In general, I think we should wide spread more the load. There is an issue of resources. And we have to describe the positions and fill them. Make the roles small and clear, define them well and communicate well between the teams are the keys here. Most of the tasks are not that time consuming at all, but if people does fill out several roles it quickly gets too much for the individual. From my experience from last releases I would definitely add to the list: the deployment team position (which has been done already), the design team one and the testing one. Those were always the week points in previous releases. Thanks for helping to enhance in this area, Simon [1] http://wiki.sugarlabs.org/go/Features/Policy ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] maintenance
Hi, thanks Tomeu for bringing this on the table and for providing a plan how we can improve the situation and thanks everyone for the interesting comments. == Release == I first want to highlight the situation from the release process point of view. SL had a release process in place for three releases now. It is a six month development cycle that is time wise close to the Fedora release process (to make sure the new Sugar release is available in the new Fedora one) [1]. We established the process with the knowledge we had from the processes at OLPC and the Fedora process. When we started the process our resources were different, more people were still directly paid to work on Sugar. Over time we scaled back on our goals per release, as we found out that the processes have to be different with a volunteer based community. For example a Feature that involves changes in UI and workflow is something that takes a lot of time (if you want to do it right) when working with the resources we have today. This is just something we had to understand. So we scaled back on the number of features and tried to make sure we set higher priorities on features that were needed in the field. This is reflected in the Feature process [2]. Christoph and others have pointed out that downstreams are probably happy what they have today and that they want to just stabilize that state. That would explain to me a lot the reservation during the release process when it comes to new features and heavier polishing. There was a direct interest by downstream in the 3G-Feature and that went trough all the steps needed to make it into a release (congrats and thanks for following the process btw). == Maintainers, Coordinators == Even with a down scaled process someone has to run it, that those that are interested in including a Feature find the possibilities to do that. Someone has to do the release management, take care of the feature process, do review the code, maintain the modules, does bug triage, does testing... Some people might say: Oh that sounds time consuming, or I have no experience in that. What made me really sad this cycle were the missing small pieces like people doing testing or coordinating testing. Those are really low entry points into getting involved and would have showed an interest in what we are doing. == What to do now == And I think those are the missing pieces Tomeu is referring to. First we need to define our goals, and that has to happen on our given resources, I presume. We overestimated for too long on what we can do, because some people took too many roles and tried to fill the gaps. We need maintainers/peers for the code. As Sascha suggested, those can be several people, our maintainer structure suggests peers per module to not block on a single person and to minimize the load. Furthermore we need coordinators. A coordinator for the deployments - the deployment team must be in place. This is the entry point for the deployments, ideally each deployment is represented there. We have a process for giving feedback what is needed in the field [2]. Of course this can be enhanced but we have a starting point. Furthermore if we want to keep on doing software releases we need a testing/QA team and a bugsquad that keeps our bug database up to date. Of course this can grow and shrink depending on our expectations too. If we just do stabilizing work this is a small effort, if we want to do features this effort should grow. Regards, Simon [1] http://wiki.sugarlabs.org/go/0.88/Roadmap [2] http://wiki.sugarlabs.org/go/Features/Policy ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Sugar in the news: picked up by BBC, AFP, IDG, eGov, Crunchgear, Boston Globe, Heise (DE), People's Daily (CN), UNIC Rio (BR), DigitalTrends, Daily Monitor (UG)
On 04/29/2010 11:27 PM, Sean DALY wrote: As our press release today was parallel to OLPC's and many journalists consulted both, I am including links to articles which cite OLPC but not Sugar by name. Also, yesterday's announcement by OLPC concerning the Memorandum of Understanding with the East African Community was often folded into the Palestine Territories coverage, so I will link to some of those too. Some errors occurred (the Boston Globe found an extra 10 million XOs, IDG said Activities are Windows-compatible) but most coverage has been positive. An encouraging step: OLPC has agreed to cite Sugar in their communications going forward, which will be helpful. BBC (1): One Laptop per Child targets Middle East and E Africa http://news.bbc.co.uk/2/hi/technology/10091177.stm BBC (2): One Laptop Per Child reaches Gaza Strip http://news.bbc.co.uk/2/hi/middle_east/8651580.stm AFP (via YNet): UN to distribute 200,000 laptops to Gaza refugees http://www.ynetnews.com/articles/0,7340,L-3882775,00.html IDG: UN to Buy 500,000 OLPC Laptops for Palestinian Children; the laptops will run Sugar, not Windows, marking a return to OLPC's roots http://www.pcworld.com/businesscenter/article/195240/un_to_buy_50_olpc_laptops_for_palestinian_children.html http://www.itworld.com/hardware/106222/un-buy-50-olpc-laptops-palestinian-children eGov Monitor: 500,000 Palestinian Children To Receive Laptops - A Collaboration Between UN And One Laptop per Child (OLPC) http://www.egovmonitor.com/node/36068 Crunchgear: OLPC gets a boost: 500,000 units ordered by U.N. for Palestinian children http://www.crunchgear.com/2010/04/29/olpc-gets-a-boost-50-units-ordered-by-u-n-for-palestinian-children/ Boston Globe: OLPC aims to send 30m laptops to African students http://www.boston.com/business/ticker/2010/04/one_laptop_per_12.html Heise (DE): OLPC-Laptops für ostafrikanische und palästinensische Kinder http://www.heise.de/newsticker/meldung/OLPC-Laptops-fuer-ostafrikanische-und-palaestinensische-Kinder-990195.html DigitalTrends: OLPC Inks Deals in Africa, Middle East http://www.digitaltrends.com/computing/olpc-inks-deals-in-africa-middle-east/ People's Daily (CN): UNRWA distributes laptops to Palestinian school children http://english.people.com.cn/90001/90783/91321/6968177.html UNIC Rio (BR): Crianças palestinas recebem computadores de parceiro da ONU http://unicrio.org.br/?p=579 Daily Monitor (UG): EAC adopts one laptop per child initiative http://www.monitor.co.ug/News/National/-/688334/909080/-/wy23nk/-/ Sean, and others involved, thanks for getting this press release out of the door. And, yes, it is important that Sugar is cited. Is the press release available online? Could not find it in the press category on the site. Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] Sucrose 0.88.0 Stable Release
This might be the sweeties Easter egg ever! The new shining version of the sweet learning environment is available. Many people from all over the world have been working together over the last six months to make this tooth breaker possible. 0.88 is the latest version of Sugar, consisting of Glucose, the base system environment; and Fructose, a set of demonstration activities. This new release contains many new features, performance and code improvements, bug fixes, and translations. You can learn more about Sugar itself by studying the Sugar definition or by reading the comic strip about the learning platform from Dongyun Lee. Even better, why not try Sugar today? You can read more about this release at the full release notes: http://wiki.sugarlabs.org/go/0.88/Notes Thanks everyone for your great contributions! In behalf of the sugar community, Your Release Team ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] getting things done (was Re: [Sugar-devel] Language Learner, a GSOC 2010 idea proposal)
On 03/30/2010 10:59 AM, Tomeu Vizoso wrote: On Tue, Mar 30, 2010 at 10:22, Christoph Derndorfer christoph.derndor...@gmail.com wrote: snip slight general rant I generally feel like there's still a real lack of activities aimed at teaching, learning and practicing basic skills such as writing, speaking, using the keyboard/touchpad, learning basic Mathematics, etc. This is *exactly* what primary schools all around the world are doing yet I think we haven't done a great job at addressing this when it comes to providing appropiate activities. /slight general rant This gives me an opportunity for ranting myself ;) From time to time someone shows frustration because SLs hasn't been able to achieve something. This in itself is a great thing to happen because shows an opportunity to get closer to our goals. But isn't actually useful unless we accompany that burst of energy with the will of putting in place whatever is needed for that something to be achieved. In this particular case, we could ask the Activity team coordinator to call for a meeting and add it to the agenda. If the team likes the goal but it turns out that there aren't available resources for tackling the specific work that derives from that goal, we could see if the Community team wants to add to their TODO list finding people interested in working on that kind of activities. We again request the community manager to add to their meeting agenda this item, the community team meets and sees if their recruitment strategy is adequate or if it can be improved in order to find activity developers. It may seem that I'm proposing adding bureaucracy for the sake of it or that I want to put bosses on top of volunteers, but rather what I'm saying is that unless we give visibility to issues, explicitly discuss things and people take ownership of responsibility areas, most things won't happen. So I want to know: do people agree that a team structure with named coordinators and members could help us do more and better, or are people happy with just hoping that someone will fall from the sky and do the right stuff? Regards, Tomeu a) It is good to put a structure in place with coordinators for specific areas (e.g. testing team,...) This may sound like a lot of work, but I am sure it is doable in the end if one concentrate on one role (see point c as well). [1] is a good example. Could have been done by the testing team, based on the release notes. In the end I did it because I thought this would help to get testing going (the result can be seen in the page history). b) People that proposes something should try to help to make it happen, this will not be possible all the time, but enhances the chances that things get done. c) We need more people to actually take action items. If that will not happen we will always be in the same situation, a few people do many things, can not address them really and will be burned out quickly. Regards, Simon [1] http://wiki.sugarlabs.org/go/0.88/Testing ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] Sugar 0.88 release --- status update
Hi, we are 10 days away from the 0.88 release [1]! We are currently in Hard Code Freeze, which means that no source code changes can be made without approval from the release-team. Translation and documentation can continue [2]. See as well [2], on how to request an exception for your show stopper. The hard code freeze ends by March the 29th when the 0.88 tarballs are due. If your fix is not a show stopper but fixes a critical issue, it has good chances to go into the upcoming bug fix release April the 28th. All the other fixes will be moved to 0.90. We will branch directly after the 0.88 release, so development can continue and Features, enhancements and invasive fixes that we moved out can be landed early in the cycle to not be forgotten. What needs to happen in the upcoming week: === Testing === I have gathered some testing plans at [3]. There are instructions on how to get the latest Soas build and put it on stick, and how you can test the latest 0.88 packages on Ubuntu Karmic. Testers are encouraged to leave notes at the wiki page, so we know what has already been tested and what failed. I will send out a daily report now with these results. Of course the bug tracker should be used to report back the findings when testing bugs, too. So we need help in testing and if people step up to coordinate testing and helps to gather test cases etc that would be awesome! === Bugfix, Review === The bugs that are found need to be fixed if possible, reviewed by the module maintainers and finally landed. === Release Notes === The 0.88 Release Notes needs to be finished [4]. === Localization === There is good progress by the localization teams in translating the 0.88 release. Especially New-String-Rich is the 3G Feature, would be nice if we get it 100% translated by next week. @Language Team Heads: Please make sure to push your translations by Monday the 29th of March, so they get included in the tarball. Of course translations after this date will be included in the 0.88.1 Bugfix Release. Regards, Simon [1] http://wiki.sugarlabs.org/go/0.88/Roadmap#Schedule [2] http://wiki.sugarlabs.org/go/Development_Team/Release#Hard_code_freeze [3] http://wiki.sugarlabs.org/go/0.88/Testing [4] http://wiki.sugarlabs.org/go/0.88/Notes ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] [ANNOUNCE] Sucrose 0.87.7 Development Release --- Release Candidate
On 03/11/2010 09:07 AM, Aleksey Lim wrote: On Thu, Mar 11, 2010 at 08:34:20AM +0100, Simon Schampijer wrote: Dear Sugar Community, This is our 0.88 Release Candidate! The Features have been landed, we are in UI and String freeze and only critical bug fixes can be landed by now. Many thanks to the community members that helped in the last days to clean up the review queue and fixing bugs! Now it is time for another big round of testing and fixing the bugs found. Let's go and make this release a big success! See [1] for more 0.88 schedule details. All the details about the code changes in this particular release can be seen at [2]. We are currently doing nightly soas builds [3]. there is also Karmic based ppa with 0.87.7 http://wiki.sugarlabs.org/go/Community/Distributions/Ubuntu#Sugar-0.88_on_Ubuntu_9.10_.28karmic.29 Thanks Aleksey for mentioning the Ubuntu Karmic ppas. The current build does not contain the 0.87.7 release yet, I will send another note when it landed, though you can certainly start to test the latest build and find possible bugs that has not been fixed with this release. The nightly soas build does contain the 0.87.7 release now. Please test away! http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ Thanks, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] Sucrose 0.87.7 Development Release --- Release Candidate
Dear Sugar Community, This is our 0.88 Release Candidate! The Features have been landed, we are in UI and String freeze and only critical bug fixes can be landed by now. Many thanks to the community members that helped in the last days to clean up the review queue and fixing bugs! Now it is time for another big round of testing and fixing the bugs found. Let's go and make this release a big success! See [1] for more 0.88 schedule details. All the details about the code changes in this particular release can be seen at [2]. We are currently doing nightly soas builds [3]. The current build does not contain the 0.87.7 release yet, I will send another note when it landed, though you can certainly start to test the latest build and find possible bugs that has not been fixed with this release. Thanks everyone for your great contributions! In behalf of the sugar community, Your Release Team [1] Schedule: http://wiki.sugarlabs.org/go/0.88/Roadmap [2] Release Notes: http://wiki.sugarlabs.org/go/0.88/0.87.7_Notes [3] http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] 0.88 String Freeze is in place
Dear Translation team(s), since the first of March, the String Freeze for the 0.88 Sugar Release [1] is in place. This means: No string changes may be made by the developers without confirmation from the localization team and notification to both the release team and the documentation team. This is to help you, the translators, to get a chance to make the translations for the 0.88 Release without having a moving base. Now is a good moment to intensify the localization efforts so that we have another rocking localized Sugar version that we can build tarballs with at March the 29th [1]. Please ask if there are any questions about this process, or anything you need to be able to do your translating work. Being a so well localized learning platform, that Sugar without doubt is, is one of Sugar's a big strength, keep on the awesome work - happy translating everyone, Simon [1] http://wiki.sugarlabs.org/go/0.88/Roadmap#Schedule [2] http://wiki.sugarlabs.org/go/Development_Team/Release#String_Freeze ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [FIELDBACK] Etoys
On 02/25/2010 12:08 AM, Walter Bender wrote: On Wed, Feb 24, 2010 at 5:43 PM, Simon Schampijersi...@schampijer.de wrote: Hi, I am teaching on a regular basis in the Planetarium pilot in Berlin, Germany [1]. I have been using Etoys now for several weeks and here is some first feedback. First: The kids do like it a lot! I want to encourage everyone to include it in his curriculum. For example you can teach easily the concepts of the coordinate system with Etoys. You create an object and print out the X and Y values when moving it on the screen. Or you can use a joystick to alter the position of this object and use this method to deepen the coordinate system concept. You know, of course, that under the View toolbar in Turtle Art, the coordinates of the Turtle are displayed. :) Any feedback re TA-83 would be very welcome. -walter Wow - This is great work! This was something I was missing in class sometimes, as I have already told you ;D This helps a lot for learners to draw the line between their program and the output. Thanks, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [FIELDBACK] Etoys
On 02/25/2010 02:59 AM, K. K. Subramaniam wrote: On Thursday 25 February 2010 04:13:52 am Simon Schampijer wrote: I am teaching on a regular basis in the Planetarium pilot in Berlin, Germany [1]. I have been using Etoys now for several weeks and here is some first feedback. First: The kids do like it a lot! I want to encourage everyone to include it in his curriculum. Etoys can be more than just a topic in a curriculum. It is the swiss army knife of the 21st century. Sure, it is a tool in the end. And then you need to decide how you use it and how you integrate it into your curriculum. That is why I gave the examples of what you can use Etoys for to reach certain goals. Teachers do not to see those possibilities to get interested, in my opinion. An interesting possibility is to get old students to create animated flashcards/sounds clips to teach a topic (say English) to younger students. Traditional flashcards just present a letter as a block. Instead, one can use a bug to create letter shapes with its trail so the children can also perceive how letters are formed. Thanks for that idea. Is there a tutorial for creating flashcards you know of? Thanks, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [FIELDBACK] Etoys
On 02/26/2010 01:29 PM, Kurt Gramlich wrote: * Cherry Witherscwith...@ekindling.org [100226 07:42]: Gerald, It's definitely a balancing act trying to get them to focus on finishing up something and getting them to explore. Once they realize that they can affect the object by scripts they just want to do everything they can possibly do in one sitting (dragging and dropping tiles in one script window ..then I'm in fire fighting mode). Too much resulted in chaos in my class. Not doing THAT again. I now give them some time to go nuts on exploration then pull them back in to finish a project. Now I'm introducing just a max of two concepts (or tiles) in one 40min. session. And 40 minutes are short :/ I definitely have learned by now that you have to teach smaller pieces so the concepts are understood well. I will hand out Sugar on Stick [1] to my learners this week and I am very excited how that will effect their learning curve. They have time to explore at home and I am sure this will advance my learners quickly. Kathleen Harness has really good lesson plans for teaching one concept at a time: www.etoysillionois.org Thanks for sharing this great resource. I really like the step by step tutorials made by waveplace [2]. That helped me a lot to get into Etoys. Regards, Simon [1] http://wiki.sugarlabs.org/go/Sugar_on_a_Stick [2] http://waveplace.com/resources/courseware/ ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] update from Triage Day
On 03/01/2010 07:35 PM, Walter Bender wrote: While we haven't finished yet, we did manage to plow through most of the 167 open tickets for Release 0.88. We've ended the formal session for the day, but plan to keep working. We will reconvene next Monday, March 8, to catch anything that has fallen between the cracks. Many thanks to erikos, tomeu, garycmartin, tch, et al. for their hard work today. -walter If you want to help triaging, help is welcome of course! If you wonder why triaging is helpful, please read here [1]. Then you should have a look at the steps to do for triaging [2]. Please do not change the milestone when triaging, this is the duty by the release team and the maintainer. And do not set the priority of the bugs his is the duty of the component maintainer. If you are new to triaging, for the first bugs we encourage you to make the changes in conjunction with another long term triager. Best is to step into the meeting next week or ask in #sugar walterbender, erikos, tomeu and garycmartin. Thanks, Simon [1] http://wiki.sugarlabs.org/go/BugSquad/Triage_Guide#Why_bug_triaging_is_helpful.3F [2] http://wiki.sugarlabs.org/go/BugSquad/Triage_Guide#Steps_of_Triaging ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] guidance for developing activity
On 03/02/2010 04:31 AM, James Simmons wrote: Parichay, Flash is problematic for developing Sugar Activities. Because it is a commercial product it cannot ship pre-installed with Sugar, although it can be installed later (but not as easily as you would like). As an alternative Sugar supplies Gnash, which supports a subset of Flash. It cannot display movies that use proprietary codecs like DivX, etc. but it does allow some existing Flash plugins to run in the Browse Activity. If you go down the gnash way, you might want to have a look at these blog posts from Tomeu: http://blog.tomeuvizoso.net/2009/05/progress-on-sugar-activities-with-swf.html http://blog.tomeuvizoso.net/2009/04/embed-flash-movies-with-gnash-in-your.html Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] Sugar 0.88 --- Testing Day --- Saturday 13th of February
Dear Sugar community, the preparation for the 0.88 is getting close and the fearless Feature owners are working together with the 'keeping-everything-together maintainers to produce another release. However, this will only get a rock solid software with testing and bug fixing! And, guess what, YOU can help to make this happen! We invite you to join in this Saturday for our first Sugar 0.88 testing day. *** When: Saturday 13th of February Kickoff-Meeting 1: 14:00 UTC Kickoff-Meeting 2: 19:00 UTC *** Where: Channel: #sugar (irc-freenode) *** Todo: Put your name on the wiki page [1] *** How to test: We will use a Sugar on a Stick [2] image with the latest 0.87.x release. This will contain the 0.88 Features landed. The image will be present at the end of the week and linked on the wiki [3] page and announced on the mailing list. This will be an asynchronous effort, hence Testing day :). However we will do two kickstart meetings. One at 14:00 UTC and one at 19:00 UTC. In these meetings we will give a short introduction to what to test and answer questions about how to get the image on a usb-key and of course how to gather the results. Instructions will of course be present on the wiki page, too. *** Help needed: I am kicking off this testing day, since I think this is vital to the success of the 0.88 release. We had problems in the last releases that testing did not happen at all or too late, hence bugs were found late etc. We want to advance in this regard. To make this meeting a success help is needed in the following areas: - Of course, testing. Join the testing day, do testing and follow the instructions to gather that feedback (bug report etc). - Testing instructions: As described in the Feature Status mail, the feature owners have to fill out the How to test section in the Feature page before the testing day. This should be as detailed as possible, imagine what could possibly go wrong and how a tester could test that Feature without having the technical background and has not been working on that Feature for days, weeks or months. - Follow up on bug reports: The Feature owners and bug submitter has to follow up on the bug reports. The final goal is of course to fix the bug. This is a little process that often takes several iterations to be done. Ideally, Feature Owners are present at the Testing day, too. To help gathering the feedback and answer possible questions. Please fill in the field 'Feature owner' [3] when you can attend the meeting and are a Feature owner. - Running the testing day: We need people to help coordinating that day. Keeping the wiki page up to date. Being present at the kickstart meetings. Helping people to flash their usb keys, enter bug reports etc. Please fill in the field 'Coordinator' when you can help in this area [3]. Suggestions, additions, questions are highly welcome of course. Thanks, Simon [1] http://wiki.sugarlabs.org/go/0.88/Testing#Attendees [2] http://wiki.sugarlabs.org/go/Sugar_on_a_Stick [3] http://wiki.sugarlabs.org/go/0.88/Testing#Testing_image ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] dealing with mailing lists
On 01/12/2010 08:55 PM, Marten Vijn wrote: On Tue, 2010-01-12 at 17:58 +0100, Tomeu Vizoso wrote: Hi, this message is to share my concern with the fact that people that could play a very important role in Sugar Labs have expressed their inability to read and participate on any of our mailing lists. Any ideas about what we could do here? Is Walter's Community Newsletter enough? What about when we know that their feedback is needed? Well a lot email is hard to read for me: - I find a lot sentences / abbreviations hard to read - top posting - subjects no changing with the topic - I got cc'ed halfway a thread - some mail are 4-5 times (cc'ing / crossposting) So I know I miss messages where I could serve. My suggestions (not much news): - no top posting - reply to list (less cc's) Hmm, some people do cc people to highlight specific persons some do remove cc and only post to the list to keep traffic low. We should at least have a guideline about it, otherwise you can not rely on a constant income-stream. Same is true to top posting. Of course these are preferences. We should decide on a guideline and then all follow it us much as possible. Where I think we are doing ok is the use of tags in sugar ([ANNOUNCE], [DESIGN], [RELEASE], [FEATURE]). At least this works very well for me to search for emails I have to read. Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] [ANNOUNCE] Feature Policy updated
On 11/27/2009 09:00 PM, Sascha Silbe wrote: On Fri, Nov 27, 2009 at 07:40:26PM +0100, Simon Schampijer wrote: * Backup up by the community * The proposer of the feature has to get feedback from the community. This includes technical feedback, feedback from the deployments etc. See as well in the last paragraph about which points the community might care. Of course there will be some different opinions in the community - in general there should be more YES than NO in the community for a feature to be able to get into a Sugar release. This puts the burden of interacting with deployments on each individual feature proposer (but away from the core developers, which is a good thing). How is that supposed to happen (getting feedback from deployments)? Writing to iaep? What if nobody replies to those messages (e.g. because it doesn't matter to them either way), will the feature be rejected even if it's a good idea? (*) Yes, sending an email to sugar-devel - see here the section community consensus [1]. So deployments for example interested in the evolution of the Sugar platform should read sugar-devel and watch out for the [FEATURE] tag. Of course not only deployers are invited to comment. The idea is to have the submitter of a Feature taking care of getting the feedback. He is the one that knows best about the feature. It is good practice to interact with the community, too. The release manager is just there to make sure the process is done correctly. (*) Obviously good idea is quite subjective, but I assume you understand what I mean. I guess we have to use common sense for that. There are guidelines [2] what you should thinks about before proposing a feature. I hope we don't see dead ends often. If we do, we can create a board that solves such conflicts - like the oversight board (not sure if it is the same board or if it has to be a different one). Regards, Simon [1] http://wiki.sugarlabs.org/go/Features/Policy#Propose_a_feature_for_addition_into_the_release_cycle [2] http://wiki.sugarlabs.org/go/Features/Policy#Things_you_should_consider_when_proposing_a_feature ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] Sucrose 0.88 Development Cycle Schedule
Dear Sugar Community, I am proud to present you the Sucrose 0.88 Schedule [1]! * Dates * We keep the time based 6 months release cycle. Final release will be: 31rd of March 2010. We basically have the same dates as GNOME. Those dates are made in conjunction with the various distributions. So we will be able to get our final release into the distributions. * New Freezes * We added some new freezes based on the experience of previous development cycles. For example we have now an UI freeze to avoid UI changes late in the cycle. As the UI is such a crucial part, we hope to keep the quality of the UI and the Sugar work flow high. This helps documentation efforts, as well. * Earlier Feature Freeze * Furthermore the Feature Freeze is earlier than in previous cycles. We want to give testers more chances to test the new features and the developers more time to clean the rough edges and stabilize them. At the final release we would like to give out a stable release with many new exciting features. * Long term planning * We layed out the 0.90 schedule, too. This allows for long term planning. For example for bigger features like versions in the datastore. If your feature misses the 0.88 boat, don't be sad the next release is coming. * Testing * We want to give out a Soas build containing Fedora 12 and the current development build. This should allow testers to have a simple to use platform for testing. Of course testing can happen as well in other distributions. The release dates are Wednesdays - we hope that the release is then packaged by the weekend to allow testers to do testing. Help wanted: We would like to see testing teams to emerge --- coordinated effort, more fun etc. Of course individuals can do testing, too. * Feature Process * The has been an overview of the Feature Process [3]. Mainly trying to write it up more clearly. But as well adding more details about how to get feedback about a feature and how to work on UI features. There will be another mail with more details on the process. * Release Manager * As already in previous releases Simon Schampijer will be your release manager. * Do the actual work * The roadmap is only the framework for this development cycle. The amount of success is up to each one of us. We have an earlier Feature Freeze now to allow for testing, but the testing itself must still happen. We have more time for stabilizing now, but the developers need to do bug fixing then. The roadmap should help as well contributors to prioritize their work based on the freezes. Use that tool! Everyone a productive development cycle, Simon [1] http://wiki.sugarlabs.org/go/0.88/Roadmap#Schedule [2] http://wiki.sugarlabs.org/go/0.90/Roadmap#Schedule [3] http://wiki.sugarlabs.org/go/Features/Policy ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] Feature Policy updated
Dear Sugar community, the Feature policy [1] has been updated. * Why this process * Let me quote the first paragraph to exaplin what this policy is for: The main goal of the feature process is to phrase out the ideas on how Sugar should evolve that are floating around in the community. These can be requests from the field or individual propositions on how to enhance the learning platform. Once the idea is written out in a wiki page (following the process described in detail below) and a maintainer is found who will be working on this feature, it can be proposed to be part of a Sucrose release cycle. The work on that feature will be tracked during the cycle and if finished in time it will find it's way in the Sucrose stable release. * Who can propose a feature * Basically, anyone can propose a feature following the guidelines in the wiki page [2]. This feature can be emerge from a deployment need or a teacher request etc. You do not need to be able to build the feature yourself. Of course to be making it's way into a release someone needs to own the feature and build it. The way to propose a feature to be included in the release cycle and how it gets included in a stable release is described at [3]. * Backup up by the community * The proposer of the feature has to get feedback from the community. This includes technical feedback, feedback from the deployments etc. See as well in the last paragraph about which points the community might care. Of course there will be some different opinions in the community - in general there should be more YES than NO in the community for a feature to be able to get into a Sugar release. * Design * What we enforce is the work with the Design Team when proposing a feature that includes UI changes or adds a new UI. We want to keep the UI consistent and the quality high. As the Sugar environment is mainly about the UI and a clear work flow this is very important. * Things you should consider when proposing a feature * There are several things you should consider when proposing a feature for the Sugar learning platform [4]. How does it impact learning? How usable and useful is this feature to a young learners? How well does this fit into a classroom environment? [...] These are good guidelines to make a Feature a success. Keep the ideas and implementations coming, Simon PS: If you need an example of someone following the process have a look at Aleksey's last mails [5]. [1] http://wiki.sugarlabs.org/go/Features/Policy [2] http://wiki.sugarlabs.org/go/Features/Policy#Propose_a_feature [3] http://wiki.sugarlabs.org/go/Features/Policy#Propose_a_feature_for_addition_into_the_release_cycle [4] http://wiki.sugarlabs.org/go/Features/Policy#Things_you_should_consider_when_proposing_a_feature [5] http://lists.sugarlabs.org/archive/sugar-devel/2009-November/021031.html ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] Bolzano 2009 - Schedule draft
Hi, I have posted an initial schedule for the Sugar Camp at Bolzano after feedback from Walter, Sebastian, Tomeu, Aleksey and the Zeitgeist people. Please let me know, if you have things you want to present that are not yet part of the schedule or have any concerns or things I have overseen. http://wiki.sugarlabs.org/go/Marketing_Team/Events/Sugarcamp_Bolzano_2009#Schedule The Saturday and Sunday I have left open for free hacking. Many arrive on saturday during the day or on monday. For those there already, use the time and work on specific projects. Please add yourself to the wiki if you have not done so yet. Note as well when you arrive and leave. Thanks, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] Sucrose 0.86.2 Bugfix Release
Dear Sugar Community, This is the second bug fix release last after the final 0.86 release - see http://sugarlabs.org/go/0.86/Roadmap#Schedule for more details. Please test the landed bug fixes carefully. A friendly BugSquad will be available to triage those bugs accordingly. Please use the instructions for your distribution (Fedora, Ubuntu, Debian etc) of choice to upgrade to this release. Note that it may take a while until the release is packaged for each distribution (especially as there are freezes (e.g. F12) at this time of the year). Please stay tuned for distribution specific announcements and watch out for updates at http://wiki.sugarlabs.org/go/Downloads. Thanks everyone for your great contributions! In behalf of the sugar community, Your Release Team == Glucose modules that changed == * http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.86.2.tar.bz2 * http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-4.0.2332.tar.gz == Glucose news == === sugar === * Not able to make screenshot #1464 * debug logs for the presence service and connection managers not working #927 * Not able to stop activities #1444 === etoys === * updated translation: fr * store reference to previous project when a project is re-uploaded * smaller font size for textual scripts * fix translating of value types and function tiles * fix bearing-to and distance-to in Test pane == Fructose modules that changed == * http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-110.tar.gz * http://download.sugarlabs.org/sources/sucrose/fructose/Read/Read-76.tar.gz * http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ImageViewer-14.tar.gz * http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-28.tar.gz == Fructose news == === Read === * Fix pagination for IA Epubs * Updated Vietnamese translations === Terminal === * Updated translations === ImageViewer === * Updated translations ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] Sugarcamp Bolzano 2009 [1]Register [2]Planning Meeting
Hey, [1] Register: As many of you know the next Sugarcamp will be from 7th to 13th November 2009 in Bolzano, Italy - http://wiki.sugarlabs.org/go/Marketing_Team/Events/Sugarcamp_Bolzano_2009. If you want to attend - please add your name to the wiki page! We originally included the weekend (7, 8th of November), to be sure to make it possible for people that work or go to school to attend, too. If that is important for you, please reply to this email and state so. Otherwise we might decide to start the 9th and do the meeting more condensed. What will this Sugarcamp be about among other things: - define the 0.88 roadmap - work on 0.88 features [2] Planing Meeting: We will do a planning meeting tomorrow the 9th of October on irc #sugar on freenode: 14:00 UTC. We mainly want to define the schedule for those dates and see what we need to organize as well in advance. Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] Sucrose 0.86.1 Final Release
Dear Sugar Community,
This is the first bug fix release last after the final 0.86 release -
see http://sugarlabs.org/go/0.86/Roadmap#Schedule for more details.
Please test the landed bug fixes carefully. A friendly BugSquad will be
available to triage those bugs accordingly.
Please use the instructions for your distribution (Fedora, Ubuntu,
Debian etc) of choice to upgrade to this release. Note that it may take
a while until the release is packaged for each distribution (especially
as there are freezes (e.g. F12) at this time of the year). Please stay
tuned for distribution specific announcements and watch out for updates
at http://wiki.sugarlabs.org/go/Downloads.
Thanks everyone for your great contributions!
In behalf of the sugar community,
Your Release Team
== Glucose modules that changed ==
*
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.86.1.tar.bz2
*
http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.86.1.tar.bz2
*
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.86.1.tar.bz2
*
http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-4.0.2326.tar.gz
== Glucose news ==
=== sugar ===
* Activities tray doesn't reflect well on switching between windows if
there are non-sugar ones {{Bug|1444}}
* sugar-emulator starts sugar out of Xephyr {{Bug|1432}}
* Sugar resets gnome's cursor {{Bug|1433}}
* Pass timestamp to gdk.Window.focus() on shell startup {{Bug|1451}}
* Starting/resuming an entry from Journal shows wrong colours {{Bug|1421}}
* Control panel resizing issue (for non en_US languages) {{Bug|308}}
* Do not start title editing for non-ds objects {{Bug|1411}}
* Shutdown/Reboot fails when multiple users are logged in {{Bug|246}}
* Package sugar-desktop icon {{Bug|1139}}
* Present windows in non-active process {{Bug|1423}}
=== sugar-toolkit ===
* Do no use random color if metadata color is not valid {{Bug|1435}}
* Shutdown/Reboot fails when multiple users are logged in{{Bug| 246}}
* Present windows in non-active process {{Bug|1423}}
=== sugar-datastore ===
* Screenshot file is not deleted {{Bug|1445}}
=== etoys ===
* updated translations: de, ja
* attempt to fix the erratic project can't be saved because of blocks
warning
* fix lost formatting when copying and pasting text inside Etoys
* show Haitian Creole instead of ht in language menu
* supply parentheses around 'bearing/distance to' tiles so expressions
can be extended
* prevent tool bar from accidental deletion
== Fructose modules that changed ==
*
http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-109.tar.gz
*
http://download.sugarlabs.org/sources/sucrose/fructose/Write/Write-67.tar.bz2
== Fructose news ==
=== Write ===
* updated translations
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [ANNOUNCE] Sucrose 0.86.0 Final Release
On 10/01/2009 06:13 AM, Kevin Cole wrote: First: congrats to all. Second: User-friendliness bug: The release notes say Please see the instructions (SoaS, Fedora, Ubuntu, Debian, etc.) of choice to upgrade to this release. No link to instructions provided in either e-mail or wiki version. Searching the wiki turned up Supported Systems which merely states that to upgrade sudo olpc-update 767 with the appropriate build number. Build number not provided in the release notes. So a build number and/or a link to the best set of instructions would be most welcome. Thanks. This is the announcement of the source tarballs of the Sucrose 0.86 release. Now it needs to be packaged for the distributions. Each distribution will have another way of packaging (deb, rpm...) and will have different ways of updating (yum, aptitude, olpc-update...). Sugar is the upstream project, that is why I do not add downstream distribution notes in the announcements. What would be nice is that packagers of each distribution update the wiki instructions for their distribution accordingly and send a note to the mailing list to encourage testers. I hope that we will have a new soas snapshot containing the 0.86 for testing soon as well. In the hope that this explanation is of any help, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] Sucrose 0.86.0 Final Release
Dear Sugar Community, this is the Final Release in our Sucrose 0.86 development cycle (http://sugarlabs.org/go/0.86/Roadmap#Schedule)! Sucrose 0.86 is the latest version of the Sugar learning platform, consisting of Glucose, the base system environment; and Fructose, a set of demonstration activities. Sucrose is released every six months. Each new release contains new features, improvements, bug fixes, and translations. Sucrose 0.86 continues this tradition and is our third well-planned release to date. Full release notes with all the links and pictures can be found at: http://wiki.sugarlabs.org/go/0.86/Notes Many people contributed to this release indirectly, including testing, documentation, translation, contributing to the Wiki, outreach to education and developer communities. On behalf of the community, we give our warmest thanks to the developers and contributors who made this Sugar release possible. Thanks everyone for your great contributions! In behalf of the sugar community, Your Release Team == What is new for users == === Activity Toolbar redesign === The toolbar used in the Activities has been redesigned. The previous design using small text tabs to group toolbar options together caused a number of usability difficulties. Many of these issues have been addressed in the redesign. For example, the redesign provides a solution for the how do I stop an activity issue (the older toolbar design did not provide an always visible Stop button, causing confusion for our young learners). Among the Activities, Browse, Write, Calculate, Terminal, Read, ImageViewer, and Turtle Art have already been ported to use the new Toolbar design, while work on many others is under way. === Switch to Metacity window manager === Sugar has switched from Matchbox to a new window manager, Metacity. Matchbox was designed for small devices; it forces ''all'' applications to run maximized. Sugar can be run on devices with much larger screens, and while activities native to Sugar are designed to be run maximized (full screen), some applications not specifically designed for Sugar can behave in unexpected ways when run with Matchbox. The switch to Metacity means that many unsugarized applications will run better inside of Sugar (e.g. Inkscape, Gimp). We endeavor to ensure that traditional desktop applications run well in Sugar, without requiring programming or behavioral changes. === Flash Activities === Gnash has been added to the Sugar Platform, meaning that authors of education content can use Flash tools to create first class activities for Sugar. === Tabs in Browse === Some web pages contain links that are designed to be opened in a new window. The Browse Activity now opens these links in new tabs inside the main activity window, similar to the behavior of most common web browsers, thus providing a better browsing experience. Note that this feature does not yet allow the user to explicitly open any link in a new tab or explicitly create a new tab. === Ad hoc Networking === New ad-hoc networking facilities allows you to connect with other Sugar users over wireless in an ad-hoc manner without relying on any wireless networking infrastructure. This is the so called under-a-tree scenario, where children can work, play, and learn collaboratively in any place imaginable, without requiring any wireless access point, which for many children is unavailable or only available at school. (The One Laptop per Child XO-1 computer provides similar functionality with its firmware-based 802.11s (mesh) network.) Ad-hoc networking allows Sugar to use this feature with most of the wireless hardware commonly found on computers. Furthermore it allows one to share an Internet connection using the same mechanism. === Read === The Read Activity now has support for Epub files. Epub is a standard format for ebooks which is gaining fast acceptance in the (e)book publishing and distribution community. A number of websites such as feedbooks.com, epubbooks.com and Google Books provide high-quality, Epub books for download at no charge. In addition to Epub support, this release of the Read Activity also lets one associate (add and edit) notes with bookmarks, and it has a more useful full-screen view that roughly indicates battery life without requiring the invocation of the Sugar Frame. === Software Update === The software-update control panel is now included in standard Sugar. It uses the Sugar Activity Library at http://activities.sugarlabs.org to check for and install the latest Activity updates available. This makes it easier for users to update to the latest version of a given Activity, and makes smoother for developers to publish and distribute newer version of Activities. === Improved Accessibility === Some parts of Sugar (Journal and Home list view) have been modified to use Gtk+ widgets, instead of HippoCanvas, which had no accessibility support. This is a part of an
[IAEP] [ANNOUNCE] Slip of Sucrose 0.86 by one week
Dear Sugar community, today at the Developers Meeting it was decided to enact a one week slip of the 0.86 Sucrose release. = 0.86 Final release the 25th September = This is due to the remaining bugs in the stable branch and some regressions, for example introduced by the switch to Metacity. We still think that switch is the right thing to do, so we want to move forward with this. As well the new toolbar design was a lot of work, but we are really convinced that it is worth it. We checked the deadlines of the distributions (Fedora, Ubuntu, Mandriva etc) and this one week slip will not introduce any missed boats. The new release date is September 25th. = Hard Code Freeze = At Monday the 21th of September we will enter Hard code freeze. No source code changes can be made without approval from the release-team. Translation and documentation can continue. The Hard code freeze will end with the 24th, but other freezes remain in effect for the stable branch. This freeze should help to avoid sudden last-minute accidents which could risk the stability that should have been reached at this point. = Bug Fix releases terminated = After our final release we will have two bugfix releases, one and two weeks after the release date. We can add anther coordinated bugfix release later, when there is feedback from the distributions shipping Sugar. Of course individual module updates can happen as well. = 0.85.7 = We added another development release for tomorrow, so people can test the latest tarballs and report back. The updated schedule can be found at http://wiki.sugarlabs.org/go/0.86/Roadmap#Schedule In the name of the Sugar community, Your release team ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] The Future of Sugar on a Stick
On 09/15/2009 10:24 AM, Tomeu Vizoso wrote: FWIW, as a (upstream) Sugar developer what I would like to see is: == Further separation between upstream and downstreams == Without artificially privileging nor discriminating any downstream. So a big +1 to giving a stronger identity to the SoaS project and to creating a separate mailing list. We already have de...@lists.laptop.org for OLPC, fedora-olpc-l...@redhat.com and others for Fedora, debian-olpc-de...@lists.alioth.debian.org for Debian, ubuntu-sugart...@lists.ubuntu.com for Ubuntu. Why SoaS would be different and share the mailing list with the upstream developers? As I'm also personally involved in SoaS (because as an individual I chose to) I will subscribe to the new SoaS ml and will crosspost as I see fit, but I don't think this should be SLs policy. == SLs to decide if it wants to produce an end-user product == If we agree on this, then I think it will be easier to decide if there's value in designating one as the preferred consumer-oriented product and which distro that would be. I always argued that SL should not do products, and I will still argue the same. Soas should have it's own identity. If SL people feel passionate about that idea, they can contribute to that project. For me SL is *just* a gathering place and we can coordinate our efforts. Soas should in my opinion work like any other open source project, like sugar for example. If olpc-uruguay is interested in sugar, they contribute to the upstream project, if GPA is, they do the same, if I as a developer am, I do the same. We had the same situation a few weeks ago, when it came to the sucrose schedule. It is good to be aware of each projects schedule, SL can not choose to decide when Sucrose is released. This needs to be decided by the people that know the impact of such a decision (aligned to distribution schedules). Of course people can make suggestions. Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] Road to Sucrose 0.86 - status report (2)
Hi, we are making good progress towards our release. Here are some status updates: b) Release notes: - I have started the work here: http://wiki.sugarlabs.org/go/0.86/Notes - Fructose activity authors have been invited to use the template [1] and add their individual notes [2]. [1] http://wiki.sugarlabs.org/go/0.86/Activity_Template [2] http://wiki.sugarlabs.org/go/0.86/Notes#Fructose_2 c) Make rpms: - Fedora 12 rpms are done (all Sucrose) Aleksey reports: - Latest packages for Ubuntu karmic can be tried out at: https://launchpad.net/~alsroot/+archive/sugar-0.86, instructions are at: http://wiki.sugarlabs.org/go/Community/Distributions/Ubuntu#Using_sugar_PPAs - 0.86 is available for Gentoo as well, instructions are at http://wiki.sugarlabs.org/go/Community/Distributions/Gentoo d) Sebastian is working on a new Soas release, stay tuned for an announcement. e) Announce widely as soon as possible: Please jump in here. f) Triaging: So far nobody has been found to lead this error. Thanks to Tomeu, Aleksey we were able to assign a milestone to each Sucrose bug yesterday. We started to set priorities as well and identified the ones that should be fixed first. Triaging is an ongoing effort, so help is still more then needed! Check out the constant bug workflow of Gary for example. He does not only file bugs, he follows up on questions from the developers and he helps triaging. A good start is to follow up on the bugs you filed, see if it is still valid, if the developer has requested more information and to follow up on bugs assigned to you. g) Testing plans: A new policy has been added. As we are in our critical phase to stabilize the 0.86 release (less than 1 week to go) [1], we request every bug fix to be tight to a ticket including a testing plan [2]. You can help to aggregate those testing plans. [1] http://wiki.sugarlabs.org/go/0.86/Roadmap#Schedule [2] http://wiki.sugarlabs.org/go/Development_Team/Release#Stabilizing h) Testing teams Do we have any teams here, besides the awesome Wellington NZ testing team? i) Bug-fix team Help is always welcome here, too! j) Plan the bug fix releases ...to be done! On behalf of the Sugar community, Your release team ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] Sucrose 0.85.6 Development Release
Dear Sugar Community,
This is the last development release in the 0.86 release cycle - see the
0.86 schedule [1] for more details. Note, that we are one week away from
our final release!
Please test the landed features [2] carefully (the individual Feature
pages contain test cases). Please report any bug and workflow issue you
find to get them in good shape for the final release. A friendly
BugSquad [3] will be available to triage those bugs accordingly and the
developers can never have enough bug food. If you have non-bug feedback
about features you can use the sugar-devel mailing list to share it with
us.
* Compatibility
There are no known compatibility issues, as of today.
Update to this version
* Update to this version
Please use the instructions for your distribution (Fedora, Ubuntu,
Debian etc) of choice to upgrade to this release.
Full 0.86 can be found at 0.86/Notes [4] soon.
On behalf of the sugar community,
Your Release Team
[1] Schedule: http://wiki.sugarlabs.org/go/0.86/Roadmap#Schedule
[2] http://wiki.sugarlabs.org/go/0.86/Feature_List
[3] BugSquad: http://wiki.sugarlabs.org/go/BugSquad
[4] http://wiki.sugarlabs.org/go/0.86/Notes
== Glucose modules==
*
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit/sugar-toolkit-0.85.7.tar.bz2
*
http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.85.7.tar.bz2
*
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.85.3.tar.bz2
*
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-base/sugar-base-0.85.5.tar.bz2
*
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-datastore/sugar-datastore-0.85.2.tar.bz2
*
http://download.sugarlabs.org/sources/sucrose/glucose/sugar-presence-service/sugar-presence-service-0.85.2.tar.bz2
*
http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-4.0.2279.tar.gz
== Glucose news ==
=== sugar ===
* Journal list view: jumping back to first page when popping up a
palette {{Bug|1235}}
* Do not re-query if visibility wasn't changed {{Bug|1250}}
* alt key gets stuck in favorites view {{Bug|1311}}
* Hidden decorations of corner frame buttons {{Bug|1294}}
* Visual artifacts on highlighted frame buttons {{Bug|1285}}
* Journal title editing unexpected behavior requires two clicks to edit
{{Bug|1283}}
* Details dialog blinks while re-query {{Bug|1271}}
* Process non-ds object in the right way in Journal {{Bug|1262}}
* Show selecting status of favorite check box in journal list view even
if start is prelighted {{Bug|1247}}
* Journal list view: jumping back to first page when popping up a
palette {{Bug|1235}}
* Fix minor issues to cleanup sugar log {{Bug|1267}}
* Allow sugar on non-XO hardware to register with an XS server {{Bug|916}}
* Do not fail on tree-model switching {{Bug|1318}}
=== sugar-toolkit ===
* Palette isn't being closed after activating some kinds of sub-widgets
{{Bug|1301}}
* Palette will fail to open if you have just 'scrubbed' over some number
of icons quickly {{Bug|1312}}
* Secondary toolbar widget should set a minimum height {{Bug|1304}}
* Activity entry icons in Journal should not be pre-lighting on rollover
(fill/stroke colour reverses) {{Bug|1313}}
* Hide palette group before immediate popup {{Bug|1291}}
* Simple scheme for hiding ToolbarBox sub-palettes {{Bug|1300}}
* Stop all animators on poup/popdown invoking {{Bug|1310}}
* Show selecting status of favorite check box in journal list view even
if start is prelighted {{Bug|1247}}
* Close previous palette on reseting palette property in invoker
{{Bug|1299}}
* Do not fail on immediate second palette opening for bottom icons
{{Bug|1292}}
* ObjectChooser displays USB media files, but fails to access file
(datastore traceback) {{Bug|1241}}
* Fullscreen resizing issues {{Bug|1263}}
* Wrong calculated positions for palettes {{Bug|1268}}
* Primary palette redraw glitch after secondary palette exposed when
rolling cursor between buttons {{Bug|1135}}
* Stop all animators while deleting palettes {{Bug|1265}}
=== sugar-artwork ===
* Wrong focus border in list view's title column {{Bug|1261}}
=== sugar-datastore ===
* Memory leaks after many get_properties() ds calls {{Bug|1240}}
=== sugar-presence-service ===
* Deal with unicode nick names (erikos) {{Bug|889}}
=== sugar-base ===
* ObjectChooser displays USB media files, but fails to access file
(datastore traceback) {{Bug|1241}}
=== etoys ===
* fix saving issues under Sugar (thanks dgd)
* fix Save button balloon help under Sugar
* support publishing to squeakland gallery
* make look-like only available for SketchMorphs to fix various isssues
* show crosshair feedback during patch-grabbing
* no longer write out the gif thumbnail when saving a project
* send utf-8 to SuperSwikiServer
* adjust toolbar under Sugar (show Next button, hide Fullscreen button)
* add display-mode menu to the world's halo
* fix ctrl/alt shortcuts under
[IAEP] [ANNOUNCE] Road to Sucrose 0.86
Hi, in today's developers meeting we made a plan on how to make Sucrose 0.86 a good and solid release. And of course we need YOU to make it a success. Here are the items with their champions and where we need help: a) Get the tarballs of the 0.85.6 release out tonight [erikos, tomeu] b) Make good release notes [erikos with community help] c) Make rpms [tomeu for Fedora, Aleksey for jhconvert, YOU for your distribution of choice] d) New Soas release [Sebastian] e) Announce widely as soon as possible [YOU can help here to announce for your distribution where the release is packaged, i.e. distribution's planets, mailing lists] f) Get the triagers ready [To be determined] We are looking for a champion of this item. Duties: Organize daily, or every second day meetings for triaging bugs with your squad. Mainly being responsive to incoming bugs. You can read more about how cool the BugSquad is at: http://wiki.sugarlabs.org/go/BugSquad page and erikos himself is happy to answer any questions to how we did rock back in the days ;p g) Testing plans [To be determined] Each feature that landed in 0.86 contains a test plan http://wiki.sugarlabs.org/go/0.86/Feature_List. Some of the tickets that got fixed do contain test cases as well. Basically we are looking for someone or a group of people that arrange those items on a wiki page so that testers can test them. h) Testing teams Once we have the packages in the distributions, we will announce it on the mailing list. You are welcome to report bugs you find into our bug tracker. Of course we would welcome any efforts to form testing teams or arrange for testing days! Best to use the mailing list to coordinate those efforts - so as many people as possible can join. i) Bug-fix team Work closely together with the triaging and testing team to get all the bugs out. You don't have to be as quick as Aleksey to contribute, just pick one of the bugs intended for 0.86 and submit the patch following the guidelines at: http://wiki.sugarlabs.org/go/Development_Team/Code_Review j) Plan the bug fix releases We will announce a plan for the time after the 0.86 release http://wiki.sugarlabs.org/go/0.86/Roadmap#Schedule We will definitely have 1 or two bug fix releases. So stay tuned. Happy bug-fixing, testing, triaging, packaging and releasing to everyone, Your release team ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Remove the naming alert in 0.86
Hi Gary, On 09/03/2009 01:21 AM, Gary C Martin wrote: Hi Simon, On 2 Sep 2009, at 16:35, Simon Schampijer wrote: On 09/02/2009 01:32 PM, Christoph Derndorfer wrote: On Wed, Sep 2, 2009 at 3:36 AM, Simon Schampijersi...@schampijer.dewrote: Hi, some of you may know, I am doing a Sugar Pilot here in Germany. I try to keep my blog (listed on the sugarlabs planet as well) about my findings up to date [1]. For technical findings (how to setup nfs, ldap on Fedora for example) the plan is to use the wiki. 'Debatable things' I will try to bring up on the mailing list as well. Regards, Simon [1] http://erikos.sweettimez.de/ --- Categories: Sugar, Deployment and Teaching [2] http://planet.sugarlabs.org/ +1 on removing the “naming alert”, this has been bugging me since the day it's been introduced. Adding “rewards” to the Journal is something that David Van Assche and Gary C Martin discussed quite a bit Paris. Unfortunately nobody had the time to really follow up on these discussions with some actual code... :-/ Looking forward to the next blog posts about your experiences in the school! Christoph Let me post here from my blog post why I think it is important: As much as I am a friend of highlighting the naming, tagging and description purposes, I don’t think the alert is a good way to ‘enforce’ this. I think those actions are not first class ones. I am happy when the kids understood the concept of the Journal a bit, but they will not start to make better descriptions in the first Sugar days or weeks, with or without the alert. For now, it is just a confusing dialog that pops up when you close an activity. And later, once the kids would know about the importance they would be better served with other tools. For example an option in the activity toolbar (like we have for the title already). From my experience I highly recommend to remove the alert, +1 when for 0.86 already. Personally I'm not keen on it either. I pretty well always skip past it myself and have learnt to click Stop and tap return. But, being neither qualified on the pedagogical needs, nor having seen actual learners of out target age, I didn't want to rush forward and +1 Simon's proposal. I have seen only one kid typing in the description field over the last 3 days. Not sure, she understood the bigger picture though. I did not explain the concept of the Journal too much, I must admit. I think often when it comes to observation-driven assessment, that the long term user should be in the main focus. But in this case, I think the dialog does help much for neither of the users, first time nor long term ones. I think adding the ability to add tags and a description in the activity toolbar would be a big step forward. The main goal as I remember was to try and combat the slew of un-named Journal entries, but a good chunk of this was likely due to the Home favourite view always starting new activity instances. Now that it resumes by default, the Journal 'spam' has been cut down quite significantly (for me). Agreed. Perhaps we drop this dialogue and then seriously take another look at improving the names automatically generated for new activity entries? Regards, --Gary That would be a nice addition - not sure yet how that will look like in detail ;D. Though, the title is not only the most important descriptor. If the tags support land maybe people will start to use this to order their Journal entries. Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Remove the naming alert in 0.86
On 09/03/2009 10:36 AM, Sascha Silbe wrote: Posting to iaep only since cross-posting doesn't work for me anymore (non-subscribed email addresses get rejected) and it's more than just a technical issue (so sugar-devel isn't enough). On Thu, Sep 03, 2009 at 12:21:46AM +0100, Gary C Martin wrote: Perhaps we drop this dialogue and then seriously take another look at improving the names automatically generated for new activity entries? +1 on that, even though I don't have direct experience with learners (other than myself) either. I'd like to toss another idea into the room: Show the naming dialog directly after _startup_ of a new instance. Ask the user what (s)he's intending to do when the decision is fresh and the user is focussed on the current activity, instead of getting in the way on closing, when the user is likely to already be focussing on the _next_ activity (whether real-world or Sugar). Not sure, the student always know in advance what it does in TA for example. Anyway, my main problem is the forcing, I guess. When the learner knows in advance about the importance if giving good names and descriptions and add easy to reach tools, maybe that is enough. I disabled the alert for tomorrows class. I can explain the Journal concept and the importance before starting and see if the students would do pay attention to naming etc then. Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] Remove the naming alert in 0.86
On 09/02/2009 01:32 PM, Christoph Derndorfer wrote: On Wed, Sep 2, 2009 at 3:36 AM, Simon Schampijersi...@schampijer.dewrote: Hi, some of you may know, I am doing a Sugar Pilot here in Germany. I try to keep my blog (listed on the sugarlabs planet as well) about my findings up to date [1]. For technical findings (how to setup nfs, ldap on Fedora for example) the plan is to use the wiki. 'Debatable things' I will try to bring up on the mailing list as well. Regards, Simon [1] http://erikos.sweettimez.de/ --- Categories: Sugar, Deployment and Teaching [2] http://planet.sugarlabs.org/ +1 on removing the “naming alert”, this has been bugging me since the day it's been introduced. Adding “rewards” to the Journal is something that David Van Assche and Gary C Martin discussed quite a bit Paris. Unfortunately nobody had the time to really follow up on these discussions with some actual code... :-/ Looking forward to the next blog posts about your experiences in the school! Christoph Let me post here from my blog post why I think it is important: As much as I am a friend of highlighting the naming, tagging and description purposes, I don’t think the alert is a good way to ‘enforce’ this. I think those actions are not first class ones. I am happy when the kids understood the concept of the Journal a bit, but they will not start to make better descriptions in the first Sugar days or weeks, with or without the alert. For now, it is just a confusing dialog that pops up when you close an activity. And later, once the kids would know about the importance they would be better served with other tools. For example an option in the activity toolbar (like we have for the title already). From my experience I highly recommend to remove the alert, +1 when for 0.86 already. I think we had some discussion on that one already. Let's decide if we do it or not. At least this is direct feedback from the field. Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [OLPC-DE] Pilot in Berlin, Germany
On 09/02/2009 12:29 PM, Holger Levsen wrote: Hi Simon, (full quote for the benefit of olpc...@l.d.o) On Dienstag, 1. September 2009, Simon Schampijer wrote: some of you may know, I am doing a Sugar Pilot here in Germany. I try to keep my blog (listed on the sugarlabs planet as well) about my findings up to date [1]. Oh, great!! Is there any information about the pilot available in German? Hi Holger, thanks for the interest. There is no information in german yet, besides a description what Sugar is. I guess I will start to add it to the Sugarlabs wiki, as I do not have other resources yet. As I it is a one person pilot for the moment (teaching, deploying, development), it might take a moment. But I will post links once I have something. In the meantime I will keep on posting my daily findings in my blog. Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] Pilot in Berlin, Germany
Hi, some of you may know, I am doing a Sugar Pilot here in Germany. I try to keep my blog (listed on the sugarlabs planet as well) about my findings up to date [1]. For technical findings (how to setup nfs, ldap on Fedora for example) the plan is to use the wiki. 'Debatable things' I will try to bring up on the mailing list as well. Regards, Simon [1] http://erikos.sweettimez.de/ --- Categories: Sugar, Deployment and Teaching [2] http://planet.sugarlabs.org/ ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] deployment team meeting?
On 08/30/2009 10:16 PM, Dennis Daniels wrote: Greetings, I will be traveling and do not know if I'll be able to attend the meeting. re: Launchpad as bug tracker for Sugar, as mentioned, is a great option. I do believe LP supports submitting bug reports straight to the LP server which, if true, would relieve users of the burden of digging around for logs thereby hopefully increasing the rate of reporting and the quality of the report itself. Lat's consider this after 0.86 is done. As we moved the soas bug tracker to Launchpad already we have a good testbed. Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] Sucrose 0.85.2 Development Release
Dear Sugar Community, This is the second development release in the 0.86 release cycle - see the schedule [1] for more details. Note, that we are two weeks late with this release, as we wanted to land some of the features so we can get feedback on, especially the toolbar redesign. This will have no effect on the final release date, though. We are getting closer to the feature freeze and a few features have been landed in this release. Please test them carefully and report any bug and workflow issues you find to get them in good shape for the release. A friendly BugSquad [2] will be available to triage those bugs accordingly and the developers can never have enough bug food. If you have non-bug feedback about features you can use the sugar-devel mailing list to share it with us. From a user point of view we want to highlight the following changes that have been made: === Switch to Metacity window manager=== Sugar switches the window manager from Matchbox to Metacity. Matchbox is designed for small devices that run all applications maximized. Sugar can run in devices with bigger screens and some applications break when run in Matchbox. Using Metacity instead means that some unsugarized apps would run better inside Sugar and that Sugar activities would behave better when run outside Sugar. === Flash Activities === Gnash has been added to the Sugar Platform, meaning that authors of educative content can use Flash tools [3] to create activities for Sugar. === Activity Toolbar redesign === The activity toolbar has been redesigned, since the design of using tabs to group options, an activity can have, did not turn out to work so well. More details about the new toolbar design [4]. The redesign gives a solution for the stop activity issue pointed out in #452. Browse and Write have been ported to use the new Toolbar design. === Tabs in Browse === Links that would open in a new window now open in new tabs inside the main activity window similar to the behavior in other browsers. Though this feature [5] isn't proposing any way for the user to explicitly open any link in a new tab, or explicitly create a new tab. === Ad hoc Networking === The new ad hoc networking facilities allows users to connect with each other over wireless in an ad hoc manner without infrastructure like an Access Point. This is the so called under a tree scenario. OLPC provided that functionality based on hardware mesh. This feature allows to provide that functionality with nearly all the wireless hardware. Furthermore it allows you to do share an internet connection using the same mechanism. === Read === The read activity does support now Epub files. For getting epubs, http://www.feedbooks.com and http://www.epubbooks.com/ can be recommended. Furthermore this version will let you associate (add and edit) notes with your bookmarks, and has a slightly more useful fullscreen view (you can now get a rough idea of how much battery is left in your laptop/netbook without invoking the frame). == Compatibility == There are no known compatibility issues, as of today. == Update to this version == Please use the instructions for your distribution (Fedora, Ubuntu, Debian etc) of choice to update to this release. == What is new for packagers == Please see the details at [7]. The locations of the tarballs are listed in the release notes as well. Thanks everyone for your great contributions! You can find more infos and pictures at [8]. In behalf of the sugar community, Your Release Team [1] Schedule: http://wiki.sugarlabs.org/go/0.86/Roadmap#Schedule [2] BugSquad: http://wiki.sugarlabs.org/go/BugSquad [3] Flash Activities: http://wiki.sugarlabs.org/go/Features/Flash_Activities [4] Toolbar: http://wiki.sugarlabs.org/go/Features/New Toolbar Design [5] Tabs: http://wiki.sugarlabs.org/go/Features/Tabs_In_Browse [6] Ad hoc Networking: http://wiki.sugarlabs.org/go/Features/Ad_hoc_Networking [7] Packagers info: http://wiki.sugarlabs.org/go/0.86/0.85.2_Notes#What_is_new_for_packagers [8] Notes: http://wiki.sugarlabs.org/go/0.86/0.85.2_Notes ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Cleaning up 0.86 Roadmap page
On 07/12/2009 11:20 AM, Simon Schampijer wrote: Hi, many good ideas have been added to the http://wiki.sugarlabs.org/go/0.86/Roadmap#Ideas section. We used this at the beginning to track our features for this release. We have been moving now to a new policy to track Features. Please use the policy described at http://wiki.sugarlabs.org/go/Features/Policy to track your features. Move the items you have been adding to this list to separate feature pages. Make sure to follow the guidelines http://wiki.sugarlabs.org/go/Features/Policy#What_does_the_feature_process_look_like.3F if you want to ask your Feature to be included in the 0.86 release. Thanks, Simon Thanks for those that did the work already. I have moved the left over items to the talk page - to not clutter the roadmap. Please keep on cleaning this page and move items to the feature pages or delete them if not applicable anymore. Our 0.86 feature page is getting into shape as well. From the proposed features (following the policy at http://wiki.sugarlabs.org/go/Features/Policy) these have been accepted already http://wiki.sugarlabs.org/go/0.86/Feature_List Some still pending. Keep on the good work. Thanks, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Sugarcamp - November 7th-12th 2009 ?
On 07/05/2009 10:14 PM, Simon Schampijer wrote: On 07/01/2009 05:38 PM, David Farning wrote: On Wed, Jul 1, 2009 at 6:41 AM, Simon Schampijersi...@schampijer.de wrote: On 07/01/2009 12:49 AM, David Farning wrote: On Tue, Jun 30, 2009 at 5:45 PM, Simon Schampijersi...@schampijer.de wrote: On 06/29/2009 10:09 PM, David Farning wrote: On Mon, Jun 29, 2009 at 9:55 AM, Simon Schampijersi...@schampijer.de wrote: Hi, the SFScon 2009 will be held in Bolzano [1]. As part of that the TIS[2] would be willing host a Sugarcamp. The camp would be part of the free software week [3], where a GNOME Hackfest will happen as well. It fits quite well in our release cycle (0.88 planning/hacking) and having the GNOME Hackfest next door would create nice synergies. We would start on a weekend to have better chances on getting (students and people who have to work during the week) everyone a chance to attend. How does that sound? Sounds good. Any one in mind to champion the event? Do you have a point of contact with event organizers so we can start working on the admin? I'll help. But based on LinuxTag you seem to have event organization pretty much figured out. david The Sugarcamp will be a different event than Linuxtag. Linuxtag was a show where you have to setup gear and get promotion material together, the camp is more planning what you want to discuss during those days. Having participated in SugarCamp Paris and some FudCons. How do you feel about the participant led format of the event? FWIW, SugarCamp Paris was intentional in it's lack of pre-organization to break from the 'Sage on Stage' broadcasting to the unwashed masses nature of previous Sugar Labs meetings. I like how Fudcon handles it - that would be a good way to go for me. It is good to announce some topics - so interested people have the possibility to join. And - we should see what the GNOME people are up to, too. http://fedoraproject.org/wiki/FUDCon/Organization Regards, Simon We have an initial page up with some information. http://wiki.sugarlabs.org/go/Marketing_Team/Events/Sugarcamp_Bolzano_2009 You can put your name there - depending on how we handle registration there might be some additions later. Thanks, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Sugarcamp - November 7th-12th 2009 ?
On 07/01/2009 05:38 PM, David Farning wrote: On Wed, Jul 1, 2009 at 6:41 AM, Simon Schampijersi...@schampijer.de wrote: On 07/01/2009 12:49 AM, David Farning wrote: On Tue, Jun 30, 2009 at 5:45 PM, Simon Schampijersi...@schampijer.de wrote: On 06/29/2009 10:09 PM, David Farning wrote: On Mon, Jun 29, 2009 at 9:55 AM, Simon Schampijersi...@schampijer.de wrote: Hi, the SFScon 2009 will be held in Bolzano [1]. As part of that the TIS[2] would be willing host a Sugarcamp. The camp would be part of the free software week [3], where a GNOME Hackfest will happen as well. It fits quite well in our release cycle (0.88 planning/hacking) and having the GNOME Hackfest next door would create nice synergies. We would start on a weekend to have better chances on getting (students and people who have to work during the week) everyone a chance to attend. How does that sound? Sounds good. Any one in mind to champion the event? Do you have a point of contact with event organizers so we can start working on the admin? I'll help. But based on LinuxTag you seem to have event organization pretty much figured out. david The Sugarcamp will be a different event than Linuxtag. Linuxtag was a show where you have to setup gear and get promotion material together, the camp is more planning what you want to discuss during those days. Having participated in SugarCamp Paris and some FudCons. How do you feel about the participant led format of the event? FWIW, SugarCamp Paris was intentional in it's lack of pre-organization to break from the 'Sage on Stage' broadcasting to the unwashed masses nature of previous Sugar Labs meetings. I like how Fudcon handles it - that would be a good way to go for me. It is good to announce some topics - so interested people have the possibility to join. And - we should see what the GNOME people are up to, too. http://fedoraproject.org/wiki/FUDCon/Organization Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Communicating project goals and Roadmap
On 07/02/2009 12:27 PM, Tomeu Vizoso wrote: On Wed, Jul 1, 2009 at 18:18, David Farningdfarn...@sugarlabs.org wrote: On Wed, Jul 1, 2009 at 7:14 AM, Tomeu Vizosoto...@sugarlabs.org wrote: On Wed, Jul 1, 2009 at 00:40, David Farningdfarn...@sugarlabs.org wrote: This thread is an attempt to help clean up a couple of issues that have been cropping up over the past couple of months. There have been a couple of instances of suboptimal communication between different parts of the project. Several times recently, external organizations have been looking for a big picture view of what is happening at Sugar Labs. The .84 release was pretty easy to coordinate. The development team picked a release date about six months after .82. The developers followed the time line pretty well. Simon did a fantastic just with just a stick and a handful of carrots as release manager getting getting the release shipped on time. The only two external organizations we worked with closely were Fedora and OLPC. With the midterm release of Strawberry, we have seen the importance of improving communication with more internal groups and external organizations. Internally, we have seen the importance of synchronizing development, marketing, and the project as a whole's time lines and goals. Externally, we have seen a significant increase in external organization participation. Several university have express interested in working with SL. Several distributions are becoming more involved. Several new pilots and deployments are participating in Sugar development rather than just consuming Sugar. A first step will be to start working on project and team level road maps which assign dates and champions to significant events. Sugar Labs and each team already have roadmap pages listed. Over the next couple of weeks, I would like to work with the development, SoaS, marketing, infrastructure teams to create roadmaps and goals. (This is not to exclude any other teams participation.) Then using iteration and project level goals we can start linking the roadmaps together. Sounds great! Tomeu There is now a very rough draft/outline at http://wiki.sugarlabs.org/go/Sugar_Labs/Roadmap . First of all, you mention several times a release but don't specify what gets released. Also, is the Sugar Learning Platform the upstream project? What about SoaS? Also, what is Unified SoaS? Release dates up to and including .86 have been determined by the development team. Starting with .88, the release schedule will be determined by the Sugar Labs oversight board. Is this picking a date for the release or deciding what goes into a release? For the date - we have picked it to align to our downstream projects - the linux distributions. So far this worked quite well. So the current dates are not picked arbitrary. Features: Depending on the Fedora policy I hacked up this one for features: http://wiki.sugarlabs.org/go/Features/Policy To reduce overhead, like an engineering steering commitee I took out the Fesco part. I think for the near future we are fine with such a 'simple' policy. I didn't knew that the oversight board was supposed to take such day-to-day decisions. In any case, I hope that the date that the SLOBs decide for the Sugar Learning Platform is the same as the development team decides, because otherwise we are going to have a big conflict here. +1 Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Sugarcamp - November 7th-12th 2009 ?
On 07/01/2009 12:49 AM, David Farning wrote: On Tue, Jun 30, 2009 at 5:45 PM, Simon Schampijersi...@schampijer.de wrote: On 06/29/2009 10:09 PM, David Farning wrote: On Mon, Jun 29, 2009 at 9:55 AM, Simon Schampijersi...@schampijer.de wrote: Hi, the SFScon 2009 will be held in Bolzano [1]. As part of that the TIS[2] would be willing host a Sugarcamp. The camp would be part of the free software week [3], where a GNOME Hackfest will happen as well. It fits quite well in our release cycle (0.88 planning/hacking) and having the GNOME Hackfest next door would create nice synergies. We would start on a weekend to have better chances on getting (students and people who have to work during the week) everyone a chance to attend. How does that sound? Sounds good. Any one in mind to champion the event? Do you have a point of contact with event organizers so we can start working on the admin? I'll help. But based on LinuxTag you seem to have event organization pretty much figured out. david The Sugarcamp will be a different event than Linuxtag. Linuxtag was a show where you have to setup gear and get promotion material together, the camp is more planning what you want to discuss during those days. That time we have local help from the freesoftwareweek people, that I guess take care of the rooms etc. The actual work is then staying in contact with them regarding our needs, setting up a wiki, getting in contact with the GNOME organizers... I would like someone else to champion that (better two people so they can discuss things) - as I want to focus on 0.86. Should not be too time consuming, maybe a nice way to start contributing to the project. Thanks, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Sugarcamp - November 7th-12th 2009 ?
On 06/29/2009 10:09 PM, David Farning wrote: On Mon, Jun 29, 2009 at 9:55 AM, Simon Schampijersi...@schampijer.de wrote: Hi, the SFScon 2009 will be held in Bolzano [1]. As part of that the TIS[2] would be willing host a Sugarcamp. The camp would be part of the free software week [3], where a GNOME Hackfest will happen as well. It fits quite well in our release cycle (0.88 planning/hacking) and having the GNOME Hackfest next door would create nice synergies. We would start on a weekend to have better chances on getting (students and people who have to work during the week) everyone a chance to attend. How does that sound? Sounds good. Any one in mind to champion the event? Do you have a point of contact with event organizers so we can start working on the admin? Yes, I am in contact with the organizers. Would be awesome if there was someone willing to help with the organization. Please get in contact with me. I see we are already list on http://www.freesoftwareweek.org/index.html Yes, they are really interested in getting us there ;p Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] Linuxtag - Résumée
Hi, Linuxtag ( http://wiki.sugarlabs.org/go/Marketing_Team/Events/LinuxTag2009 ) is over - time for a résumée: I am very happy about how the conference went. The Sugar Labs booth team were good representatives of a community that is easy to approach. I want to thank the team in spreading the word: * Tony Anderson (deployment expert, hacking ShowNTell in the last minute to give a demo) * David Van Assche (the OpenSuse link, more than 50 activities in the OpenSuse Soas version) * Sean Daly (marketing expert, table full of netbooks and XOs) * Sebastian Dziallas (Mister Strawberry) * Bert and Eva Freudenberg and the Squeak Team (Etoys can do more than the car example) * Adam Holt (OLPC XO 1.5 expert) * James Zaki (a constant in demonstrating the learning platform ) Many thanks to Harald and all of the Skolelinux team, X2GO and Linux4Afrika for being our friendly booth partners. And one thing I was really happy about was the booth material we had available. Two banners, two posters, branded balloons, Flyers in a href=http://wiki.sugarlabs.org/images/0/02/Flyer_englisch.pdf;English/a and a href=http://wiki.sugarlabs.org/images/c/c4/Flyer_deutsch.pdf;German/a, generic business cards, a table full of different laptops running Sugar and a wide screen demo. Marketing wise this was a big step forward. - If you have some pictures from Linuxtag please add links here: http://wiki.sugarlabs.org/go/Marketing_Team/Events/LinuxTag2009#Impressions And feel free to add some comments if you liked it - what was great about it and what did not work, what could be enhanced next time. Thanks, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Linuxtag - Résumée
On 06/29/2009 03:15 PM, Simon Schampijer wrote: Hi, Linuxtag ( http://wiki.sugarlabs.org/go/Marketing_Team/Events/LinuxTag2009 ) is over - time for a résumée: I am very happy about how the conference went. The Sugar Labs booth team were good representatives of a community that is easy to approach. I want to thank the team in spreading the word: * Tony Anderson (deployment expert, hacking ShowNTell in the last minute to give a demo) * David Van Assche (the OpenSuse link, more than 50 activities in the OpenSuse Soas version) * Sean Daly (marketing expert, table full of netbooks and XOs) * Sebastian Dziallas (Mister Strawberry) * Bert and Eva Freudenberg and the Squeak Team (Etoys can do more than the car example) Of course I meant Rita Freudenberg here :) Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] LinuxTag
On 06/21/2009 06:34 PM, Tony Anderson wrote: Hi, I am in Berlin and will be through June 28. I plan to attend LinuxTag. If there is anything I can do to help, please let me know. Yours, Tony Hi Tony, that is awesome. Best is to get your name on: http://wiki.sugarlabs.org/go/Marketing_Team/Events/LinuxTag2009 Help at the booth would be welcome for example: http://wiki.sugarlabs.org/go/Marketing_Team/Events/LinuxTag2009#Sugar_Booth Thanks, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Linuxtag - What is left to do to make it a success?
On 06/18/2009 11:13 AM, Simon Schampijer wrote: On 06/18/2009 10:57 AM, Sascha Silbe wrote: On Thu, Jun 18, 2009 at 08:59:53AM +0200, Simon Schampijer wrote: http://wiki.sugarlabs.org/go/Marketing_Team/Events/LinuxTag2009 Quoting that page: Not permitted by Linuxtag: * wireless access points (You are not permitted to operate your private wireless LAN. Please take this serious. There will be several site surveys to ensure this.) * connect visitors to the project's network Does this mean you can't show off collaboration? CU Sascha I sent that question to the Linuxtag team this morning. Will post here the results. Cheers, Simon We are ok for the mesh. We don't want to much traffic in the dedicated Exhibition Network, because we want to prevent problems at the booth with slow internet access. But if you want to create a WLAN without a connection to the exibition network e.g. to create a mash network, so feel free to do this. Everything is fine then, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Linuxtag - What is left to do to make it a success?
On 06/21/2009 03:55 PM, Caroline Meeks wrote: Don't forget to have a supply of boot-helper CDs. It can be much less frustrating then trying to figure out the Bios for some machines. /me has 15 boot helper cds with latest kernel cheers, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] USA PTA Study: Dads significantly more engaged in child’s education
On 06/18/2009 10:20 AM, Sean DALY wrote: http://www.pwrnewmedia.com/2009/pta_90612/index.html For once a positive sounding study. Thanks for sharing, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Linuxtag - What is left to do to make it a success?
On 06/18/2009 10:57 AM, Sascha Silbe wrote: On Thu, Jun 18, 2009 at 08:59:53AM +0200, Simon Schampijer wrote: http://wiki.sugarlabs.org/go/Marketing_Team/Events/LinuxTag2009 Quoting that page: Not permitted by Linuxtag: * wireless access points (You are not permitted to operate your private wireless LAN. Please take this serious. There will be several site surveys to ensure this.) * connect visitors to the project's network Does this mean you can't show off collaboration? CU Sascha I sent that question to the Linuxtag team this morning. Will post here the results. Cheers, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Show Must Go On - SoaS for the XO-1
On 06/17/2009 11:34 AM, Tomeu Vizoso wrote: On Wed, Jun 17, 2009 at 11:30, Sean DALYsdaly...@gmail.com wrote: In my view it's never a mistake to indicate that a procedure will wipe all data. We all have a learning curve and the first time I lost all my Journal entries including photos on an XO I wasn't happy about it. I think we shouldn't put the burden of communicating with the general public on the developers. Sebastian is doing an awesome amount of work and he may not have too many spare cycles to think about everything that is required to communicate to the different people. What if we developers only announce in developer-oriented forums and someone else (marketing team?) takes the task of communicating it to end users? Regards, Tomeu That sounds like a very good idea to me. We need to split the workload and try to let people do mostly (of course ideally one should know what is happening a bit in all the teams) what they are good in. +1 from my side, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Linuxtag - Getting involved [---Update---]
On 06/12/2009 06:49 PM, David Farning wrote: Has Rita from Etoys gotten a hold of you? I believe that she was interested in having some of the squeak developers stay with the Sugar team? You mean a hacking session? Have not heard anything about this yet. We share the same booth if you mean that. Secondly, should we redirect the SugarCamp Berlin page to FudCon Berlin?Are there any logistical considerations that you might want to keep separate? No, I think that is absolutely appropriate. Just open the sessions on their wiki. Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Linuxtag - Getting involved [---Update---]
On 06/08/2009 01:56 PM, Simon Schampijer wrote: Hi, Linuxtag [1] is getting closer. If you are attending please add your name here: http://wiki.sugarlabs.org/go/Marketing_Team/Events/LinuxTag2009#Attendees As some of you may have heard we will be having a booth there. Please take shifts at our booth. Ideally a shift is two persons. Helping at the booth means answering questions regarding Sugar and Sugar Labs, demoing Sugar and flashing Soas on request. http://wiki.sugarlabs.org/go/Marketing_Team/Events/LinuxTag2009#Sugar_Booth I have started to put up information on lodging. Hotel Funkturm sounds quite interesting. I have called them Saturday - and one 4-6 person room was left. http://wiki.sugarlabs.org/go/Marketing_Team/Events/LinuxTag2009#Lodging Thanks, Simon [1] 24.-27. Juni: http://www.linuxtag.org/2009/en.html http://www.linuxtag.org/2009/dl/projekte/Halle7.2a/198-50198--72a110a.pdf This is what our booth looks like at Linuxtag. Remember we have this area with 5 other projects. We will occupy one of the info centers. Additionally we will get a little table right next to it to demo the sugar software - one bigger screen should be enough here (I have that device already). The classroom is of skolinux. But if we arrange with them we can use it as well - we should have a concept though of course. Check with me for further discussions. Please take shifts at http://wiki.sugarlabs.org/go/Marketing_Team/Events/LinuxTag2009#Sugar_Booth You will get a Linuxtag ticket in exchange from me ;p Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] linuxtag 2009
On 06/09/2009 09:45 PM, Max Spevack wrote: On Tue, 9 Jun 2009, David Farning wrote: True to the type of response I have grown the expect (and greatly appreaciate), Max basically said the more the merrier at FudCon. Lets see what sort of good things we can make happen. I'll let Max explain what he has to offer:) Thanks, David. Here's what I wrote to David privately: === The short answer is bring your people, and make use of our hackfest and BarCamp infrastructure. Our house is your house. FUDCon is Friday, Saturday, and Sunday. On Friday and Saturday, you need a LinuxTag ticket to get into FUDCon. I should have enough e-tickets to cover 15 people for 2 days (30 etickets). Have folks sign up here: https://fedoraproject.org/wiki/FUDCon:Berlin_2009_attendees https://fedoraproject.org/wiki/FUDConBerlin2009#BarCamp_and_Hackfests I probably don't have enough etickets to get people into LinuxTag on Wednesday and Thursday as well, which aren't official FUDCon days anyway. So in short, I can provide: * Etickets on Fri and Sat for 15 people (85% sure of this) * FUDCon infrstructure of participation (100% sure) * Opportunity to interact with various Fedora folks (100% sure) === How's this all sound? --Max Awesome, thanks Max - does all sound great. For the tickets. I have 12 tickets left for all-time Linuxtag. These are for people helping at the Sugar Labs booth mostly. Please drop me a line and I can send a ticket to your email address. Of course - don't forget to take a shift in the schedule at http://wiki.sugarlabs.org/go/Marketing_Team/Events/LinuxTag2009#Sugar_Booth ;) Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] linuxtag 2009
On 06/09/2009 05:36 PM, David Farning wrote: On Tue, Jun 9, 2009 at 7:41 AM, Sean DALYsdaly...@gmail.com wrote: Hi Tomeu, I've updated the wiki with my name, shifts, and banner info I too am interested in the 4-6 pers. room crashpad I like the idea of colocating with FUDCon, if that's not complicated; I would very much like to see that. I am pinging Max Spevack the event coordinator from Fedora/RedHat Awesome. Collaborating with FUDCon would be the best imho. Room wise, people wise and I guess working wise. We could for example work on the things we are highly dependent on Fedora, like Soas for example. LTSP might be another interesting one. Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] Linuxtag - Getting involved
Hi, Linuxtag [1] is getting closer. If you are attending please add your name here: http://wiki.sugarlabs.org/go/Marketing_Team/Events/LinuxTag2009#Attendees As some of you may have heard we will be having a booth there. Please take shifts at our booth. Ideally a shift is two persons. Helping at the booth means answering questions regarding Sugar and Sugar Labs, demoing Sugar and flashing Soas on request. http://wiki.sugarlabs.org/go/Marketing_Team/Events/LinuxTag2009#Sugar_Booth I have started to put up information on lodging. Hotel Funkturm sounds quite interesting. I have called them Saturday - and one 4-6 person room was left. http://wiki.sugarlabs.org/go/Marketing_Team/Events/LinuxTag2009#Lodging Thanks, Simon [1] 24.-27. Juni: http://www.linuxtag.org/2009/en.html ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [ANNOUNCE] Bug tracker housekeeping
On 05/25/2009 12:25 PM, Martin Langhoff wrote: On Fri, May 22, 2009 at 4:54 PM, Simon Schampijersi...@schampijer.de wrote: Submitters: Please go through all the open bugs you have submitted. If BTW, if there's any guidance for the test team in Bxl on how to tag the bugs found against latest SoaS, we'll be happy to follow... This search shows most (all?) the bugs we filed... http://dev.sugarlabs.org/query?status=acceptedstatus=assignedstatus=newstatus=reopenedorder=prioritycol=idcol=summarycol=statuscol=ownercol=typemilestone=soas_fossvtdistribution=SoaS cheers, m The bug tracker housekeeping was meant mostly for Sugar 0.84-0.86. We want to do the same for Soas when it is released. http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap In general - of course the work flow I described above would be good to do on a regular basis - chacking that the tickets I filed are valid, someone has followed up:) Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] Bug tracker housekeeping
Dear Sugar Community, After the dust of the 0.84 release has been settled we like to clean up the database. With each new Sucrose release comes some bug tracker housekeeping. This e-mail is designed to let you know about the things we ask you to do until May 27, 2009: Submitters: Please go through all the open bugs you have submitted. If some information has been requested - please provide this information. If the bug does not apply anymore - feel free to close it and leave a short note. Owners: Please go through the bugs you own and update them accordingly. If the bugs marked 0.84 still apply - please move them to the 0.86 milestone. __ Triage day: Wednesday - 27th of May 2009 - 16.00 (UTC) - going through the list of 0.86 bugs and see if there are things that needs to be added explicitly to the Roadmap. - cleaning up left overs Thanks for reading, Simon (for the BugSquad Team [1]) [1] http://wiki.sugarlabs.org/go/BugSquad ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Marketing] Usage scenarios for Sugar?
On 05/22/2009 08:03 PM, Sean DALY wrote: Hi everyone, we have been contacted by a monthly tech publication in Europe willing to devote several pages to Sugar in their summer issue! More specifically, advising parents how to download run SoaS and do educational stuff with their kids during the summer holidays. Off the top of my head I suggested a scenario where Memorize is customized with family photos, a Turtle Art lesson, ... Suggestions please! Using Memorize looks like a good choice. I will use it during my upcoming Project day. The idea is that the kids will create games using all the other available tools - like the camera, turtle art, paint... The material I collect here can be recycled of course. I will keep you posted. Have a nice weekend, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Pangaean
On 05/20/2009 11:48 AM, Bernie Innocenti wrote: This project is in many ways complementary to Sugar: http://www.pangaean.org I'd like to know what people think about it. The software appears to be Windows based, but perhaps it's built with portable technologies. If not, we might want to pick up the basic idea of communicating through pictons. In the resources section, there are several academic papers on this research. I would love to see a pictogram based language used in Sugar. This would also help for handicapped people or of course people that do not know how to read and write yet. Would be nice to use pictograms in help sections as well. Out of curiosity I looked once at possibilities. It seems that Bliss-Symbols [1] was once a standard. For 'talkers' today the ones from Prentke Romich [2] seems to be common - but I am not sure if those pictograms are available for use. Maybe someone else knows more in this area. Regards, Simon [1] http://en.wikipedia.org/wiki/Bliss-Symbol [2] http://www.prentrom.com ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [PATCH] add clock frame device
Martin Dengler wrote: The below patch adds a clock device to the frame: http://www.martindengler.com/tmp/screenshot_clock_device_frame-06_a6_a689bf1e-3f34-4da3-afed-aa910ab4f677.png http://www.martindengler.com/tmp/screenshot_clock_device_frame-07_84_841da15d-9bd7-4fe4-aada-8e8ab723f806.png http://www.martindengler.com/tmp/screenshot_clock_device_frame-08_4b_4ba1059e-4db9-4f22-8661-7916f6a167f8.png The patch incorporates almost all of the feedback already received. Feedback welcome. Martin Nice! Two things: a) this could be a good moment to get the infrastructure on activities.sugarlabs.org for device extensions up - or at least to think about how we can realize that. b) fuzzy clock - I guess this can be done optionally and made available in (a) - or in the settings option described by Eben Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Fwd: [Sur] Labyrinth 6
Gary C Martin wrote: On 17 Apr 2009, at 08:15, Tomeu Vizoso wrote: Congratulations to Gary and Aleksey. Paola is a teacher from .uy and has already tried the new version of Labyrinth and written a small tutorial about how to create mind maps with it, see link in the forwarded email below. Thanks Tomeu, very open to feedback (have a long list myself also), so please do feel free bounce any feedback you see my way. Regards, -Gary Hi Gary, awesome work - of course a big thank to Aleksey as well. Had fun creating a map with Labyrinth today - some thoughts: - zooming shortcuts: In Browse we use (ctrl++ and ctrl+-) for zoom in and zoom out. Write does the same. Not sure what Read does - at least ctrl++ does not work. Would be cool to settle on some short cuts. (Btw: the wheel on a mouse does work as well for zooming) - zoom: is there a way that when I zoomed in, that I move to another area of the canvas? (hope it is clear what I mean here) - scaling of images: when an image is scaled moving it does take very very long - I guess it is re-rendered - translations: is labyrinth up in pootle? Thanks, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Fwd: [Sur] Labyrinth 6
Simon Schampijer wrote: Gary C Martin wrote: On 17 Apr 2009, at 08:15, Tomeu Vizoso wrote: Congratulations to Gary and Aleksey. Paola is a teacher from .uy and has already tried the new version of Labyrinth and written a small tutorial about how to create mind maps with it, see link in the forwarded email below. Thanks Tomeu, very open to feedback (have a long list myself also), so please do feel free bounce any feedback you see my way. Regards, -Gary Hi Gary, awesome work - of course a big thank to Aleksey as well. Had fun creating a map with Labyrinth today - some thoughts: - zooming shortcuts: In Browse we use (ctrl++ and ctrl+-) for zoom in and zoom out. Write does the same. Not sure what Read does - at least ctrl++ does not work. Would be cool to settle on some short cuts. (Btw: the wheel on a mouse does work as well for zooming) - zoom: is there a way that when I zoomed in, that I move to another area of the canvas? (hope it is clear what I mean here) - scaling of images: when an image is scaled moving it does take very very long - I guess it is re-rendered - translations: is labyrinth up in pootle? Just seen that this is already the case - and that we have the German translations even done already. Maybe we can do a release with the translations? Is the translation team aware that Labyrinth is ready to be translated? No spanish translation yet - as of today. I guess the teacher from Uruguay who has been doing the tutorial will have it done in 5 minutes ;) Cheers, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Fwd: [Sur] Labyrinth 6
Tomeu Vizoso wrote: On Fri, May 8, 2009 at 11:44, Simon Schampijer si...@schampijer.de wrote: Simon Schampijer wrote: Gary C Martin wrote: On 17 Apr 2009, at 08:15, Tomeu Vizoso wrote: Congratulations to Gary and Aleksey. Paola is a teacher from .uy and has already tried the new version of Labyrinth and written a small tutorial about how to create mind maps with it, see link in the forwarded email below. Thanks Tomeu, very open to feedback (have a long list myself also), so please do feel free bounce any feedback you see my way. Regards, -Gary Hi Gary, awesome work - of course a big thank to Aleksey as well. Had fun creating a map with Labyrinth today - some thoughts: - zooming shortcuts: In Browse we use (ctrl++ and ctrl+-) for zoom in and zoom out. Write does the same. Not sure what Read does - at least ctrl++ does not work. Would be cool to settle on some short cuts. (Btw: the wheel on a mouse does work as well for zooming) - zoom: is there a way that when I zoomed in, that I move to another area of the canvas? (hope it is clear what I mean here) - scaling of images: when an image is scaled moving it does take very very long - I guess it is re-rendered - translations: is labyrinth up in pootle? Just seen that this is already the case - and that we have the German translations even done already. Maybe we can do a release with the translations? Is the translation team aware that Labyrinth is ready to be translated? No spanish translation yet - as of today. I guess the teacher from Uruguay who has been doing the tutorial will have it done in 5 minutes ;) Sounds like a good idea. Could someone who is in this list and also in olpc-sur ask there for a translation? Thanks, Tomeu Yeah that would be awesome. Otherwise I would have to write me a Translate-Activity to write the request myself :) BTW, a teacher request for the labyrinth activity: Can I print that out? Would be cool to be able to export the diagram to pdf or a png (not only handy for printing). Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] wiki - openid login error
Ivan Krstić wrote: Hi Simon, On Mar 15, 2009, at 11:31 PM, Simon Schampijer wrote: I get this error when trying to login using openid. The regular login does work fine. Can you try now and let me know if it's fixed? Awesome! Works again. (By the way, the best way to bring this stuff to the attention of the infrastructure team is to mail systems -at- lists.sugarlabs.org.) Sounds good, will do next time. Thanks, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] wiki - openid login error
Hi, error:Invalid AuthRequest: 769: Realm verification failed for: http://sugarlabs.org/ I get this error when trying to login using openid. The regular login does work fine. Thanks, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] wiki - openid login error
Sean DALY wrote: Simon - keep in mind the wiki is now wiki.sugarlabs.org to aid navigation, does that work? Sean Nope, same error. Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Linuxtag 2009 - how do we want to promote Sugar Labs
Rita Freudenberg wrote: Am 12.02.2009 um 12:41 schrieb Holger Levsen: Hi, On Dienstag, 10. Februar 2009, Simon Schampijer wrote: I would like us to be present at LinuxTag (24-27 June 2009) [1]. What do you think about a shared booth with the german OLPC association, OLPC Deutschland e.V.? Hi all, while we're at it, how about Squeak joining you at LinuxTag at the booth, too? One of the members of the german Squeak association could be there for each day and show the Etoys activity working within Sugar at the OLPC-Laptop ... Best Regards, Rita Ok, the call for projects is out [1]. We have to submit until the 24th of March. Looking at the submission form we need quite some discussion with the marketing team. Should we make it an item on next week's Tuesdays at 15 UTC meeting - or is it packed with 0.84 already and we should find another date? Thanks, Simon [1] http://wiki.linuxtag.org/w/fp:Call_for_Projects ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Linuxtag 2009 - how do we want to promote Sugar Labs
Sean DALY wrote: Hi Simon no problem let's put it on the agenda Part of the meeting will be either laughing in celebration or crying in desolation, depending on how the press reacts or doesn't to Monday's media launch ;-) Sean Awesome, either works fine for me - positive and negative emotions are close together :) I will try to be prepared and study the application form to come up with concrete points we can discuss. Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] 'Job positions' in Getting Involved page
Various people beat me to do it! Should we list certain 'Job positions' similar to those for companies in the Getting Involved page? These are volunteer tasks of course - but maybe we find easier people taking over certain tasks. For example: Buildbot maintenance, sugar-jhbuild maintenance Regards, Simon PS: Of course, those needs to be updated etc - maybe the first Job position would be to find someone doing just this. ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] [ANNOUNCE] 0.84 Activity Release Notes
Simon Schampijer wrote: Dear Activity Maintainers, for the 0.84 Release notes I need your help. It would be awesome to get detailed notes for each activity. Definitely the Fructose ones - as well the Honey activities are welcome. Please use the Template [1] to create a page and link it appropriately at [2]. The template contains comments for each section. As an example you can look at the Browse release notes [3] as well. Deadline: Friday, March 13th as our big Marketing Press campaign will start the 16th of March. Of course, the sooner this gets in the better, as it will be a starting point for the FLOSS Manual efforts as well. Thanks, Your Release Team [1] http://sugarlabs.org/go/DevelopmentTeam/Release/Releases/Sucrose/0.84/ActivityTeamplate [2] http://sugarlabs.org/go/DevelopmentTeam/Release/Releases/Sucrose/0.84#Fructose_2 [3] http://sugarlabs.org/go/DevelopmentTeam/Release/Releases/Sucrose/0.84/Browse Another ping on this one. 3 more days left. # Terminal # Read # Chat # Imageviewer # Jukebox And if you want to be proactive having an activity site like the TurtelArt one around does not hurt :D http://sugarlabs.org/go/Activities/Turtle_Art Go guys Go - we are so close! Thanks, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] [ANNOUNCE] 0.84 Activity Release Notes
Bert Freudenberg wrote: On 11.03.2009, at 15:13, Simon Schampijer wrote: Simon Schampijer wrote: Dear Activity Maintainers, for the 0.84 Release notes I need your help. It would be awesome to get detailed notes for each activity. Definitely the Fructose ones - as well the Honey activities are welcome. Please use the Template [1] to create a page and link it appropriately at [2]. The template contains comments for each section. As an example you can look at the Browse release notes [3] as well. Deadline: Friday, March 13th as our big Marketing Press campaign will start the 16th of March. Of course, the sooner this gets in the better, as it will be a starting point for the FLOSS Manual efforts as well. Thanks, Your Release Team [1] http://sugarlabs.org/go/DevelopmentTeam/Release/Releases/Sucrose/0.84/ActivityTeamplate [2] http://sugarlabs.org/go/DevelopmentTeam/Release/Releases/Sucrose/0.84#Fructose_2 [3] http://sugarlabs.org/go/DevelopmentTeam/Release/Releases/Sucrose/0.84/Browse Another ping on this one. 3 more days left. I added http://sugarlabs.org/go/DevelopmentTeam/Release/Releases/Sucrose/0.84/Etoys - Bert - Awesome. I did not make an entry as I thought we could add the changes to the Glucose section as well. But looks more than perfect like that. Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] 0.84 Activity Release Notes
Dear Activity Maintainers, for the 0.84 Release notes I need your help. It would be awesome to get detailed notes for each activity. Definitely the Fructose ones - as well the Honey activities are welcome. Please use the Template [1] to create a page and link it appropriately at [2]. The template contains comments for each section. As an example you can look at the Browse release notes [3] as well. Deadline: Friday, March 13th as our big Marketing Press campaign will start the 16th of March. Of course, the sooner this gets in the better, as it will be a starting point for the FLOSS Manual efforts as well. Thanks, Your Release Team [1] http://sugarlabs.org/go/DevelopmentTeam/Release/Releases/Sucrose/0.84/ActivityTeamplate [2] http://sugarlabs.org/go/DevelopmentTeam/Release/Releases/Sucrose/0.84#Fructose_2 [3] http://sugarlabs.org/go/DevelopmentTeam/Release/Releases/Sucrose/0.84/Browse ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] [ANNOUNCE] 0.84 Activity Release Notes
Simon Schampijer wrote: Dear Activity Maintainers, for the 0.84 Release notes I need your help. It would be awesome to get detailed notes for each activity. Definitely the Fructose ones - as well the Honey activities are welcome. Please use the Template [1] to create a page and link it appropriately at [2]. The template contains comments for each section. As an example you can look at the Browse release notes [3] as well. Of course you are encouraged to use screenshots in your notes. Spread the word shiny! Regards, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [ANNOUNCE] Sucrose 0.84.0 Final Release
Bernie Innocenti wrote: On 03/05/09 10:56, Tomeu Vizoso wrote: So, how are we going to celebrate it? As 0.84.1 is going to be on, we could do a bug fix sprint during a weekend. Should we get the marketing team to prepare a press release? Did we announce it on Freshmeat? Slashdot? LWN? OLPCNews? The marketing team is already working on it. 2 things I think are left. Good release notes and a well enough working Soas for people to try out. Both will be available in the next days - at least that is the plan. Cheers, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] New Soas-1 Image containing Sucrose 0.84.0
Hi, we have another Soas-1 image (based on F10). It contains the latest Glucose and Fructose packages from the 0.84.0 release [1]. You can download the image at [2]. Give it a try and report bugs at [3]. Please use the Soas component for issues related to the image - like booting, not correct keyboard detected and use the Sugar and Activity components to report bugs regarding the UI. Thanks, Your Soas Team [1] http://sugarlabs.org/go/DevelopmentTeam/Release/Releases/Sucrose/0.84.0 [2] http://download.sugarlabs.org/soas/snapshots/1/Soas-200903051021.iso [3] dev.sugarlabs.org ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] Sucrose 0.84 - Bugfix Release Schedule
Hi, to get bug fixes in after our 0.84.0 release we have scheduled two more coordinated releases for the next 4 weeks [1]. Mar 20 Sucrose 0.84.1 Apr 3 Sucrose 0.84.2 Furthermore we will do weekly Glucose releases to keep the tarballs up to date. The dates were picked in coordination with the upcoming Fedora 11 [2] and Ubuntu Jaunty [3] release. We hope to stabilize our 0.84 Release like that. So the upcoming weeks, Testers, the BugSquad and Developers need to work together closely to polish everything up. Main testing environment will be Sugar on a Stick [4] and your distribution of choice. Happy polishing everyone - we are getting close now! Your Release Team [1] http://sugarlabs.org/go/DevelopmentTeam/Release/Roadmap#Schedule [2] https://fedoraproject.org/wiki/Releases/11/Schedule [3] https://wiki.ubuntu.com/JauntyReleaseSchedule [4] http://sugarlabs.org/go/Sugar_on_a_Stick ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] [ANNOUNCE] Sucrose 0.84.0 Final Release
Dear Sugar Community,
this is the Final Release in our 0.84 development cycle [1]! Thanks to
our testers the developers were able to bring in bug fixes to stabilize
the platform. And the translators were busy to get all the strings
translated. All the details what have changed from a user point of view
will be handled in the detailed 0.84 release notes.
Thanks everyone for your great contributions!
In behalf of the sugar community,
Your Release Team
[1] The Sucrose Release Schedule can be found here
http://sugarlabs.org/go/DevelopmentTeam/Release/Roadmap#Schedule
[2] You can find more details at
http://sugarlabs.org/go/DevelopmentTeam/Release/Releases/Sucrose/0.84.0
== Glucose news ==
=== sugar ===
*Focus rectangle corners should be rounded {{Bug|406}}
* Restore minimal .xol support {{Bug|459}}
* Check the activity version and replace an older version upon download
{{Bug|464}}
* Friendstray: icon reacting to right click {{Bug|441}}
* Network device icons don't react on right click {{Bug|463}}
* Don't open a launcher window when that activity is already running
{{Bug|426}}
* Fall back to application-octet-stream for unknown types {{Bug|458}}
* Show a generic icon for clippings, if available {{Bug|454}}
* Don’t add_bundle on activity dir change when installed already {{Bug|442}}
* Make mute sound code togglable
* Keyhandler: Map XF86Search to the journal search
* Keyhandler: Catch all exceptions (thanks to Sascha Silbe)
* Give time for exit to execute when closing the emulator {{Bug|435}}
* Dont hardcode the maximum amount of entries to cache in the journal
{{Bug|72}}
* Add standard ‘Print’ shortcut to take a screenshot
* Use keyboard specific keys to set the volume {{Bug|430}}
* Update to new DBus policy {{Bug|307}}
* Fix palette appearance on right-click {{Bug|403}}
* Switch to existing instance of an activity if it’s already running
{{Bug|410}}
=== sugar-toolkit ===
* Catch all exceptions while saving {{Bug|224}}
* Listen for map in Window instead of in Canvas (alsroot) {{Bug|428}}
* Restore minimal .xol support {{Bug|459}}
* Use the same font size independent from scaling
* Don't recursively clean an activity if it's a symbolic link {{Bug|444}}
* Add extension to temp icon file names {{Bug|458}}
* Process .py files in subdirectories './setup genplot' (alsroot)
{{Bug|391}}
* Improve error handling of calls to XGrabKey {{Bug|431}}
* Cleanup temp files at exit {{Bug|435}}
* Let activities provide their own implementation of get_preview()
{{Bug|152}}
* Show/Hide the color palette correctly {{Bug|374}}
* Support setting None as the secondary text {{Bug|384}}
* Only display one line in the secondary text of a clipping palette
{{Bug|384}}
* Switch to existing instance of an activity if it’s already running
{{Bug|410}}
* Reveal the palette on right click on an activity icon {{Bug|409}}
=== sugar-base ===
* 2*42=84
=== sugar-presence-service ===
* 0.84.0 Final release
* No changes since 0.83.3
=== sugar-datastore ===
* Nice, cool-looking 0.84.0 version number ;)
=== sugar-artwork ===
* This component release is part of the effort: Make Sugar 0.84 appear
up here: http://en.wikipedia.org/wiki/84_(number)#In_other_fields
=== etoys ===
* updated translations de, el, fr, sv, tr, vi
* fixed 'bearing to' and 'distance to' tiles
== Fructose news ==
=== terminal ===
* Change default font size to 10 from 8
* New translations
=== read ===
* Sucrose 0.84.0 release
* Translation updates: pt, de, sv, ne
=== browse ===
* new translations
=== chat ===
* Sucrose 0.84.0 Release
* Translation updates: pt, ne
=== write ===
* Update to API change, render_page_to_image starts now with 1 {{Bug|152}}
* Override get_preview {{Bug|152}}
* Deprecation fix: Use bundle_id instead od service_name
* Updated translations
=== imageviewer ===
* Remove hacks needed because of d.sl.o (Tomeu) {{Bug|258}}
* New languages and translations
=== jukebox ===
* share/keep button hidden
* new translations added
=== turtleart ===
* updated de, it and sv artwork
___
IAEP -- It's An Education Project (not a laptop project!)
IAEP@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/iaep
[IAEP] New Sugar on a Stick image available
Weeeh! A new Soas-1 is out. It contains all the bug fixes that made it into head in the last days. And you can use Wade Brainerd's fabulous Typing Turtle to get you going in 10 finger typing - /me won already a Gold Medal. Get it [1] when it is still sticky! News: Sugar - Don't add_bundle on activity dir change when installed already #442 - Make mute sound code togglable - Keyhandler: Map XF86Search to the journal search - Keyhandler: Catch all exceptions (thanks to silbe) - Give time for atexit to execute when closing the emulator #435 - Dont hardcode the maximum amount of entries to cache in the journal #72 - Add standard 'Print' shortcut to take a screenshot - Use keyboard specific keys to set the volume #430 - Update to new DBus policy #307 - Fix palette appearance on right-click #403 - Switch to existing instance of an activity if it's already running #410 Sugar-toolkit - Process .py files in subdirectories './setup genplot' #391 (alsroot) - Improve error handling of calls to XGrabKey #431 - Cleanup temp files at exit #435 - Let activities provide their own implementation of get_preview() #152 - Show/Hide the color palette correctly (#374) - Support setting None as the secondary text #384 - Only display one line in the secondary text of a clipping palette #384 - Switch to existing instance of an activity if it's already running #410 - Reveal the palette on right click on an activity icon #409 [1] http://download.sugarlabs.org/soas/snapshots/1/Soas-200902271904.iso In behalf of the Sugar community, Your Soas Team ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] SoaS - moving onward...
Sebastian Dziallas wrote: Hi all, and here's another announcement for Sugar on a Stick! You can grab your updated version now directly from here: http://download.sugarlabs.org/soas/snapshots/1/latest.iso How does the link gets created. It got killed when syncing with the last image - since it did not exist in the source repository. Thanks, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Sucrose 0.83.6 in Soas
Tomeu Vizoso wrote: On Tue, Feb 24, 2009 at 15:13, Simon Schampijer si...@schampijer.de wrote: Hi, Sucrose 0.83.6 - the 0.84 Release Candidate 2 has find it's way into Sugar on a Stick. Get the latest image at: http://download.sugarlabs.org/soas/snapshots/1/Soas-200902231225.iso Does it work in XOs? Regards, Tomeu No, we have a kernel issue (Bernie has pinged the right people) that needs to be fixed first to be able to build XO images. Cheers, Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
