Re: [IAEP] [Sugar-devel] Help wanted remixing the Help Activity
On Wed, May 27, 2009 at 6:27 AM, Caroline Meeks carol...@solutiongrove.com wrote: The Help Activity gives us a place to tell Users that Sugar is a Community Project run by volunteers and we welcome them, their questions and their help That great message also belongs in the Browse home page, http://git.sugarlabs.org/projects/browse/repos/mainline/blobs/master/data/index.html which could usefully link to online help and/or the local help files. ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] NYSCATE - Nov 2009 in Rochester NY
last time I talked to the NYSCATE folks I had a booth for the RIT game dept again this year. Last year and this year I will be showcasing our OLPC efforts in that booth and am happy to use it to support the efforts in any way I can. Sent from my iPhone On Jun 1, 2009, at 7:50 AM, Karlie Robinson karlie_robin...@webpath.net wrote: Caroline Meeks wrote: Hi Karlie, Its looking like Rochester is going to be a hotbed of Sugar development. We are hoping to co-locate a Sugar conference with NYSCATE. Given that I think we should really go for it on in terms of presentations. My thought is lets propose two hands on 3 hour workshops. Using Sugar in the Elementary School Classroom and another specializing in Using Sugar in Math Instruction. Lets also sign up for a 1 hour lecture format session on Sugar. Who else is going to be there? Is there someone from Math4 group who can be Presentor 1 for the Math Class? Of course I'll be in town and I've done a 50 minute presentation on Math4 at Ithaca EdTech day and Bar Camp Rochester[1]. I was the one who got everyone going on Math4 in Rochester (Fedora XO donation to RIT and liaison work). We also have Steve Jacobs the RIT professor who ran with my suggestion to teach Open Source development. And last but not least, Fred Grose who'll be overseeing the RIT Co- ops this summer, Wiki Magician, and the guy who's been beyond helpful filling in our knowledge gaps concerning OLPC and Sugar Labs. Steve and Fred were also the driving force behind an OLPC Grass Roots group in Rochester. I just happened to come to the first meeting as a Fedora-OLPC SIG rep. The rest is kismet. (Rochester NY is a hot bed for FOSS to begin with LUG of Rochester is one of the oldest Linux User Groups in the world running continuously for 15 years) ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [FM Discuss] FM--DocBook (was Fwd: Fwd: [Sugar-devel] Documentation ...)
We discussed Docbook quite a bit in March and made one or two limp attempts at conversion. For example: http://lists.flossmanuals.net/pipermail/discuss-flossmanuals.net/2009-March/001157.html There are just two things preventing us from offering automatically generated docbook: 1. Nobody has come up with a concrete enough need for it to even say what good FM docbook would look like (until now?). 2. The source is html written by over 700 people using a mix of wysiwyg editors, twiki markup, hand coding, and cut-and-paste from word processors. It would be easier to concentrate on the first problem. We won't know if the books' source needs a manual clean-up until it is shown to be broken. Douglas ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] OLPC Volunteer Infrastructure Group Meeting: [Today]
The Volunteer Infrastructure Group (/gang) Meeting is today (June 2th) at 4pm (EST) The Volunteer Infrastructure Group is a team of Volunteer Sysadmins who help maintain services and systems around OLPC and the OLPC/SugarLabs community. The weekly VIG meeting is an excellent chance to get involved, or to be aware of upcoming projects. http://wiki.laptop.org/go/OLPC:Volunteer_Infrastructure_Group http://vig.laptop.org/wiki/index.php/User:Dogi http://idea.laptop.org/ideatorrent/ideatorrent/vig/ http://embed.mibbit.com/?server=irc.oftc.netchannel=%23olpc-adminsettings=12a698505c860f99a6ad1051c57975f9noServerTab=falsenoServerNotices=truenoServerMotd=truenick=Guest Agenda: * backup: new VM for streaming to a robot tape solution * pinguin: new www * meeting: new structure and meeting.sugarlabs.org * vig and wiki (testwiki): migration plan * idea: help promote this idea function * rt: migration plan * maps: there new datas on deployments * bigsister: new VM on w91 Meeting Details: Date: June 2th, 2009 Time: 16:00 EST Location: irc.oftc.net #olpc-admin or click on - http://embed.mibbit.com/?server=irc.oftc.netchannel=%23olpc-adminsettings=12a698505c860f99a6ad1051c57975f9noServerTab=falsenoServerNotices=truenoServerMotd=truenick=Guest ciao dogi ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] new sugarSUSE Vbox and VMplayer auto builds of sugarSUSE 30.1 Ready made appliances for download
new sugarSUSE Vbox and VMplayer auto builds of sugarSUSE 30.1 Ready made appliances for download Look at http://download.opensuse.org/repositories/Education/images/ http://download.opensuse.org/repositories/Education/images/iso/ contacts cyberorg and nubae on #opensuse-edu or #sugar Tom Gilliard satellit also usb images as of 5/31/2009 ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Marketing] Michael Trucano, World Bank EduTech blog: What have we learned from OLPC pilots to date?
Dear Readers, Please don't open the attachment because if you click on attachment link it will automatically send your email address and password to the sender. Sincerely, Hi, 2009/6/2 Caroline Meeks carol...@solutiongrove.com: Has anyone been able to get to this document? The Australian Council for Educational Research has produced perhaps the most useful literature review of the�Evaluation of OLPC programs globally. enjoy... On Tue, Jun 2, 2009 at 7:10 AM, Sean DALY sdaly...@gmail.com wrote: http://blogs.worldbank.org/edutech/what-have-we-learned-from-olpc-pilots-to-date ___ Marketing mailing list market...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/marketing -- Caroline Meeks Solution Grove carol...@solutiongrove.com 617-500-3488 - Office 505-213-3268 - Fax ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep -- Maria del Pilar S�enz Sugar Labs Colombia ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Marketing] [Sugar-devel] [SoaS] Request for Artwork: Boot Screen
http://wiki.sugarlabs.org/go/Marketing_Team/Boot_Logo Christian - I myself prefer the rays to dots which I feel too closely resemble networks in the Neighborhood view, confusion is possible (networks being connected to at startup?) Fred - I'm willing to try that sunrise metaphor, tonight if I can (travelling today) Re splash page with logo: in my next mockup I'll leave off the example school logo.and move that frame to the end. It might be better to reserve a frame for customizable logo or message, before or after the Sugar spash page Version info: In fact I feel strongly about showing version information... or its corollary, making it easy to find. Teachers, parents, admins, G1G1 donors unfamiliar with Sugar will not have the foggiest idea how to hunt down version information (Learners might not have trouble finding it - they will explore their machines ad infinitum - but they can't be expected to know about versioning). We are about to embark on hundreds of thousands of XO-1.5s running v0..84 which will coexist with a huge installed base of v0.82 (and many earlier); SoaS with its simplified numbering scheme will (we hope) sow the seeds for preinstalled Sugar in distributions for education projects. We may be deploying v0.86 at the end of the year... aside from how we manage the Activity compatibility matrix, we need to make such info *extremely* easy to track down for someone interested in checking if Sugar + Activities are up-to-date. Our strategy for teacher buy-in is star marketing on Activities (see press releases); making Activity installation/upgrade simple this summer is part of what we need to do to make SoaS possible in the classroom. Helping users understand what version they have (of Sugar, of each Activity) is a key aspect of that. I agree that it's unpleasant to see numbers at boot time (especially a datestamped snapshot number). Why don't we borrow an idea from Apple? They have a tiny apple icon in the upper-left corner of the screen; clicking on it opens a window with the processor, RAM and OSX version number. In addition to the About my computer section in the Control Panel, perhaps we could show the version in the Frame? The bottom bar has room I think. When we start to get consolidated feedback, we will know if difficult-to-find version info is a problem for Sugar / Activity updaters or not. I feel sure it is and showing the version in the Frame (the one-glance status communicator) seems to me a good approach which would let us skip info in the splash screen. Nota: my idea would be for each version to change the Sugar logo color too... potentially allowing troubleshooters to ask what color is the Sugar logo? and match that to the version number. thanks Sean On Thu, Jun 4, 2009 at 5:00 AM, Frederick Grose fgr...@gmail.com wrote: Please indulge me to make another pitch for the 'sunrise' metaphor for the growing ring. Using the same color locations, the ring would build from sunrise orange to midday yellow to afternoon greens and blues to dusky red-violets (perhaps the darker one last). These are just common earth metaphors that might come to mind as children worldwide--who may have never seen a analog or digital clock--anticipate what may be waiting for them in their day ahead of them. The ring would also build from one foot, and end symmetrically on the other--a growth surrounding the nascent learner like a cover--a home--a safe shelter for learning or a shower of celestial opportunities. Will I grow too like the graphic is suggesting? OK, these are just potential metaphors... On Wed, Jun 3, 2009 at 10:17 PM, Frederick Grose fgr...@gmail.com wrote: I like that a lot. I'm with others on leaving the version number as well to the 'About my Computer' panel. (It can be referenced and then read as needed after booting, whereas the vanishing boot image just makes me nervous about writing down or memorizing a long number.) The Green Hornet, would of course only appear on a 'Graphic guidelines' page for deployments and packagers. I suggest you try this sequence: 1. a short, blank white field (infinite potential) 2. the small xo figure (just possibly me in a big universe) 3. the building ring and figure (what might be building for me? Will I grow too as suggested?) 4. the Sugar, and optional custom graphic, pausing, usually a machine-dependent variable time, allowing for reading (fixing the name of this tool and those who built it for me) Do we want a gray Sugar Labs opposite the fedora remix? (5. the living, playable, ready-to-open door to Learning--the Sugar Home view.) Thanks everyone! --Fred On Wed, Jun 3, 2009 at 8:50 PM, Sean DALY sdaly...@gmail.com wrote: Fred - I have uploaded a new variant to the wiki: http://wiki.sugarlabs.org/go/Marketing_Team/Boot_Logo#Eleven_Color_Ray_Variant.2C_Growing_XO_Avatar.2C_No_Prior_Outlines.2C_Starts_With_Logo_Splash_Page On Tue, Jun 2, 2009 at 4:37 AM, Frederick Grose fgr...@gmail.com
Re: [IAEP] [Marketing] [Sugar-devel] [SoaS] Request for Artwork: Boot Screen
On Thu, Jun 04, 2009 at 01:24:26PM +0200, Sean DALY wrote: http://wiki.sugarlabs.org/go/Marketing_Team/Boot_Logo Christian - I myself prefer the rays to dots which I feel too closely resemble networks in the Neighborhood view, confusion is possible (networks being connected to at startup?) The rays are too dominant, IMHO. The circles suffer from the confusion you mention, and the dots (gray) are just right. Re splash page with logo: in my next mockup I'll leave off the example school logo.and move that frame to the end. It might be better to reserve a frame for customizable logo or message, before or after the Sugar spash page I think that information is great to work in, but it won't be too visible (thus useful) in just one frame, will it? Version info: In fact I feel strongly about showing version information...or its corollary, making it easy to find. +1 I agree that it's unpleasant to see numbers at boot time (especially a datestamped snapshot number). In grey it's not, IMHO. Nota: my idea would be for each version to change the Sugar logo color too... Much less obtrusive, perhaps, and still effective. I guess we'll run out of easily-differentiable fill colours in a few years, but that's a different bridge... thanks Sean Martin pgpaZ8VP66WVS.pgp Description: PGP signature ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Marketing] [Sugar-devel] [SoaS] Request for Artwork: Boot Screen
On 4 Jun 2009, at 12:24, Sean DALY wrote: http://wiki.sugarlabs.org/go/Marketing_Team/Boot_Logo Christian - I myself prefer the rays to dots which I feel too closely resemble networks in the Neighborhood view, confusion is possible (networks being connected to at startup?) Coloured dots resembling access-point icons, hadn't twigged with, me but I do see your point now you've mentioned it. I'm still playing safe with a simple all grey vote at the moment ;-) http://wiki.sugarlabs.org/go/Image:Refined-XO-sugar-boot.gif Fred - I'm willing to try that sunrise metaphor, tonight if I can (travelling today) Re splash page with logo: in my next mockup I'll leave off the example school logo.and move that frame to the end. It might be better to reserve a frame for customizable logo or message, before or after the Sugar spash page Hmmm, think this will destroy the whole idea of making the boot process animation a transition into a working user interface. If it's just going to show some random branding at the end, there's little benefit in trying to initially transition gracefully (might as well make the whole sequence some branding message). Version info: In fact I feel strongly about showing version information... or its corollary, making it easy to find. Teachers, parents, admins, G1G1 donors unfamiliar with Sugar will not have the foggiest idea how to hunt down version information (Learners might not have trouble finding it - they will explore their machines ad infinitum - but they can't be expected to know about versioning). We are about to embark on hundreds of thousands of XO-1.5s running v0..84 which will coexist with a huge installed base of v0.82 (and many earlier); SoaS with its simplified numbering scheme will (we hope) sow the seeds for preinstalled Sugar in distributions for education projects. We may be deploying v0.86 at the end of the year... aside from how we manage the Activity compatibility matrix, we need to make such info *extremely* easy to track down for someone interested in checking if Sugar + Activities are up-to-date. Our strategy for teacher buy-in is star marketing on Activities (see press releases); making Activity installation/upgrade simple this summer is part of what we need to do to make SoaS possible in the classroom. Helping users understand what version they have (of Sugar, of each Activity) is a key aspect of that. I agree that it's unpleasant to see numbers at boot time (especially a datestamped snapshot number). Why don't we borrow an idea from Apple? They have a tiny apple icon in the upper-left corner of the screen; clicking on it opens a window with the processor, RAM and OSX version number. In addition to the About my computer section in the Control Panel, perhaps we could show the version in the Frame? The bottom bar has room I think. -1, to misc numbers in the frame. When we start to get consolidated feedback, we will know if difficult-to-find version info is a problem for Sugar / Activity updaters or not. We really need to solve this technically (as best we can), not make folks need hunt through compatibility lists to see if their Sugar version number allows them to install and run some Activity. Regards, --Gary I feel sure it is and showing the version in the Frame (the one-glance status communicator) seems to me a good approach which would let us skip info in the splash screen. Nota: my idea would be for each version to change the Sugar logo color too... potentially allowing troubleshooters to ask what color is the Sugar logo? and match that to the version number. thanks Sean On Thu, Jun 4, 2009 at 5:00 AM, Frederick Grose fgr...@gmail.com wrote: Please indulge me to make another pitch for the 'sunrise' metaphor for the growing ring. Using the same color locations, the ring would build from sunrise orange to midday yellow to afternoon greens and blues to dusky red-violets (perhaps the darker one last). These are just common earth metaphors that might come to mind as children worldwide--who may have never seen a analog or digital clock--anticipate what may be waiting for them in their day ahead of them. The ring would also build from one foot, and end symmetrically on the other--a growth surrounding the nascent learner like a cover--a home--a safe shelter for learning or a shower of celestial opportunities. Will I grow too like the graphic is suggesting? OK, these are just potential metaphors... On Wed, Jun 3, 2009 at 10:17 PM, Frederick Grose fgr...@gmail.com wrote: I like that a lot. I'm with others on leaving the version number as well to the 'About my Computer' panel. (It can be referenced and then read as needed after booting, whereas the vanishing boot image just makes me nervous about writing down or memorizing a long number.) The Green Hornet, would of course only appear on a 'Graphic guidelines' page for
Re: [IAEP] [Marketing] [Sugar-devel] [SoaS] Request for Artwork: Boot Screen
Sorry, meant to reply-all! Comment below: On Thu, Jun 4, 2009 at 7:55 AM, Martin Dengler mar...@martindengler.com wrote: On Thu, Jun 04, 2009 at 01:24:26PM +0200, Sean DALY wrote: http://wiki.sugarlabs.org/go/Marketing_Team/Boot_Logo Christian - I myself prefer the rays to dots which I feel too closely resemble networks in the Neighborhood view, confusion is possible (networks being connected to at startup?) The rays are too dominant, IMHO. The circles suffer from the confusion you mention, and the dots (gray) are just right. I agree--the rays don't feel like they are part of the same visual language as the rest of the UI, since they break the square grid that other icons succumb to. I'm not sure about the confusion regarding the color circles and access points; maybe we should ask around and see what other people think? Maybe we could also just choose a single color (the colors you have set for your XO) to avoid any confusion. Otherwise, I'm also perfectly happy sticking to gray dots, and coloring the XO as I mentioned earlier. Re splash page with logo: in my next mockup I'll leave off the example school logo.and move that frame to the end. It might be better to reserve a frame for customizable logo or message, before or after the Sugar spash page I think that information is great to work in, but it won't be too visible (thus useful) in just one frame, will it? Version info: In fact I feel strongly about showing version information...or its corollary, making it easy to find. +1 I agree that it's unpleasant to see numbers at boot time (especially a datestamped snapshot number). In grey it's not, IMHO. Nota: my idea would be for each version to change the Sugar logo color too... Much less obtrusive, perhaps, and still effective. I guess we'll run out of easily-differentiable fill colours in a few years, but that's a different bridge... thanks Sean Martin -- anyth...@christianmarcschmidt.com http://www.christianmarcschmidt.com 917/ 575 0013 ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Marketing] [Sugar-devel] [SoaS] Request for Artwork: Boot Screen
On Thu, Jun 4, 2009 at 9:15 AM, Christian Marc Schmidt christianm...@gmail.com wrote: Sorry, meant to reply-all! Comment below: On Thu, Jun 4, 2009 at 7:55 AM, Martin Dengler mar...@martindengler.com wrote: On Thu, Jun 04, 2009 at 01:24:26PM +0200, Sean DALY wrote: http://wiki.sugarlabs.org/go/Marketing_Team/Boot_Logo Christian - I myself prefer the rays to dots which I feel too closely resemble networks in the Neighborhood view, confusion is possible (networks being connected to at startup?) The rays are too dominant, IMHO. The circles suffer from the confusion you mention, and the dots (gray) are just right. I agree--the rays don't feel like they are part of the same visual language as the rest of the UI, since they break the square grid that other icons succumb to. I'm not sure about the confusion regarding the color circles and access points; maybe we should ask around and see what other people think? Maybe we could also just choose a single color (the colors you have set for your XO) to avoid any confusion. Otherwise, I'm also perfectly happy sticking to gray dots, and coloring the XO as I mentioned earlier. I agree about the rays not feeling like the fit. It feels like its not part of Sugar. I haven't been following carefully but my favorite idea was grey dots getting colored in as you go. Re splash page with logo: in my next mockup I'll leave off the example school logo.and move that frame to the end. It might be better to reserve a frame for customizable logo or message, before or after the Sugar spash page I think that information is great to work in, but it won't be too visible (thus useful) in just one frame, will it? Version info: In fact I feel strongly about showing version information...or its corollary, making it easy to find. +1 I agree that it's unpleasant to see numbers at boot time (especially a datestamped snapshot number). In grey it's not, IMHO. Nota: my idea would be for each version to change the Sugar logo color too... Much less obtrusive, perhaps, and still effective. I guess we'll run out of easily-differentiable fill colours in a few years, but that's a different bridge... thanks Sean Martin -- anyth...@christianmarcschmidt.com http://www.christianmarcschmidt.com 917/ 575 0013 ___ Marketing mailing list market...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/marketing -- Caroline Meeks Solution Grove carol...@solutiongrove.com 617-500-3488 - Office 505-213-3268 - Fax ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Unbootable machine
On 06/02/09 07:10, H. Peter Anvin wrote: Bernie Innocenti wrote: On 06/02/09 03:43, H. Peter Anvin wrote: Bernie Innocenti wrote: Disk /dev/sdb: 2055 MB, 2055208960 bytes 221 heads, 2 sectors/track, 9081 cylinders I don't know where fdisk, the Linux kernel, or whatever come up with these kinds of geometries. They're almost universally non-bootable. Ok, I wiped mbr and made fdisk create a new one: Disk /dev/sdb: 2055 MB, 2055208960 bytes 64 heads, 62 sectors/track, 1011 cylinders ^^ Equally weird. The only standard ones are 64 heads, 32 sectors and 255 heads, 63 sectors. Indeed, repartitioning the USB stick with 32 sectors and 255 heads fixed boot for a previously unbootable computer. Thanks, Peter. I think we should document this tip in the Sugar on a Stick wiki page and perhaps change the Fedora livecd-iso-to-disk script to create the MBR with parted rather than fdisk. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] Fwd: [Edu-sig] Python flavoured Scratch
This might interest some of the Pythonistas ... - Bert - Begin forwarded message: From: Jurgis Pralgauskis jurgis.pralgaus...@gmail.com Date: 3. Juni 2009 23:45:21 MESZ To: edu-...@python.org edu-...@python.org Subject: [Edu-sig] Python flavoured Scratch Hi, probably most of You know Scratch http://info.scratch.mit.edu/Educators I thought it has quite some pythonic approach (especially, because it is easy to learn), so I tried to localize it to Python ;)... You can see the results (and comparison screenshots) http://files.akl.lt/users/jurgis/scratch/python_flavour/ well, parentheses seem to get in a way a bit.. value assignment = and += looks ok also clauses look nice -- other languages wouldn't manage this ;) there are problems with placeholders order for lists, but it will be fixed for Scratch 1.4 (comming in 2 weeks) http://scratch.mit.edu/forums/viewtopic.php?pid=130068 also there is problem with logical equality comparison it is hardcoded somewhere, so I can't change = to == :/ (but Scratch is opensourced, so this is quite feasible :)) Also Scratch uses messages instead of functions. this is more like throwing/catching exceptions, but still different so I left this as is When message blabla received ps.: What's the use of all this? well, students could get more used to python while Scratching then it is possible to export Scratch scripts to xml with Chirp http://www.chirp.scratchr.org/ so one can translate them to python Scratch quite follows LOGO paradigm, so xturtle could be mapped to it somehow, I guess.. by the way, XO TurtleArt has python bindings http://tonyforster.blogspot.com/2009/02/using-python-blocks-in-turtleart.html -- Jurgis Pralgauskis Don't worry, be happy and make things better ;) http://sagemath.visiems.lt ___ Edu-sig mailing list edu-...@python.org http://mail.python.org/mailman/listinfo/edu-sig ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] Introducing kids to Sugar
There's a possibility for a class of five graders in Florence to pilot SoaS next year. Our friends of OLPC Italia came up with a good question: how would an introductory class for Sugar work in practice? Both teachers and kids will be present to learn simultaneously, which makes things more interesting. Who actually went through such experience already? How was the class organized? What materials were used? And, more importantly, ware there any issues to watch out for? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Marketing] [Sugar-devel] [SoaS] Request for Artwork: Boot Screen
On Thu, Jun 4, 2009 at 7:24 AM, Sean DALY sdaly...@gmail.com wrote: http://wiki.sugarlabs.org/go/Marketing_Team/Boot_Logo Christian - I myself prefer the rays to dots which I feel too closely resemble networks in the Neighborhood view, confusion is possible (networks being connected to at startup?) Fred - I'm willing to try that sunrise metaphor, tonight if I can (travelling today) Re splash page with logo: in my next mockup I'll leave off the example school logo.and move that frame to the end. It might be better to reserve a frame for customizable logo or message, before or after the Sugar spash page Yes, in that mockup the first screen is kind of overwhelming with several logos and a few pieces of textual information. At the same time, we tried very hard to eliminate the slideshow effect that feels (well, is) like a bunch of marketing material that detracts from the UI. I think the Sugar logo should stand alone, so it reads powerfully, and then be replaced in short order by the XO. Perhaps we could entertain a text only solution to identifying the school, in gray beneath the sugar logo. Thoughts? Version info: In fact I feel strongly about showing version information... or its corollary, making it easy to find. Teachers, I think it's more important that we make it easy to find in the UI. Kids won't reboot that often, and it would be silly to reboot just to find that info. parents, admins, G1G1 donors unfamiliar with Sugar will not have the foggiest idea how to hunt down version information (Learners might not have trouble finding it - they will explore their machines ad infinitum - but they can't be expected to know about versioning). We are about to embark on hundreds of thousands of XO-1.5s running v0..84 which will coexist with a huge installed base of v0.82 (and many earlier); SoaS with its simplified numbering scheme will (we hope) sow the seeds for preinstalled Sugar in distributions for education projects. We may be deploying v0.86 at the end of the year... aside from how we manage the Activity compatibility matrix, we need to make such info *extremely* easy to track down for someone interested in checking if Sugar + Activities are up-to-date. Our strategy for teacher buy-in is star marketing on Activities (see press releases); making Activity installation/upgrade simple this summer is part of what we need to do to make SoaS possible in the classroom. Helping users understand what version they have (of Sugar, of each Activity) is a key aspect of that. I agree that it's unpleasant to see numbers at boot time (especially a datestamped snapshot number). Why don't we borrow an idea from Apple? We basically have this already. We ust happen to have an XO in the center of the screen, instead of an apple icon in the upper left. The info is actually in the About my XO section of the settings, which might be one step too far. We could go back to an earlier design for the XO menu and have a direct About my XO menu item which jumps directly to the correct settings panel. We could also separate the About my XO panel from settings, removing it from the settings panel completely and showing it as it's own modal dialog accessible via an About my XO menu item. I would be fine with either approach. They have a tiny apple icon in the upper-left corner of the screen; clicking on it opens a window with the processor, RAM and OSX version number. In addition to the About my computer section in the Control Panel, perhaps we could show the version in the Frame? The bottom bar has room I think. There's no need to expose this information directly. It will only be needed on occasion, and the Frame is designed for the information you want to carry with you all the time. When we start to get consolidated feedback, we will know if difficult-to-find version info is a problem for Sugar / Activity updaters or not. I feel sure it is and showing the version in the Frame (the one-glance status communicator) seems to me a good approach which would let us skip info in the splash screen. Nota: my idea would be for each version to change the Sugar logo color too... potentially allowing troubleshooters to ask what color is the Sugar logo? and match that to the version number. I would much rather see the logo change colors with each boot, but changing with each release is a pretty cool idea. I would support that. I think there are enough of combinations to make wrapping around a non-issue, as long as we only change the color for major releases (2 per year, on average). Finally, regarding the animation itself: I Think the gray dots are still the best option, and the clearest. They fit the style, but won't be confused with APs. If we can in any way manage it, coloring the XO in the child's chosen colors is really the way that color should be introduced. The colored dots seem to undermine the importance of that metaphor, for me. Everywhere else in the UI, color relates to
Re: [IAEP] Introducing kids to Sugar
On Thu, Jun 04, 2009 at 04:28:27PM +0200, Bernie Innocenti wrote: There's a possibility for a class of fifth graders in Florence to pilot SoaS next year. [...] Who actually went through such experience already? How was the class organized? What materials were used? And, more importantly, ware there any issues to watch out for? We in the UK are in almost exactly the same situation and would love to hear any answers to those questions. Martin pgp2o8oMefPhA.pgp Description: PGP signature ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Marketing] [Sugar-devel] [SoaS] Request for Artwork: Boot Screen
I agree with Eben's points below... Maybe it would help if one of us mocked up the alternative he is describing? Christian On Jun 4, 2009, at 10:35 AM, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 10:31 AM, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 7:24 AM, Sean DALY sdaly...@gmail.com wrote: http://wiki.sugarlabs.org/go/Marketing_Team/Boot_Logo Christian - I myself prefer the rays to dots which I feel too closely resemble networks in the Neighborhood view, confusion is possible (networks being connected to at startup?) Fred - I'm willing to try that sunrise metaphor, tonight if I can (travelling today) Re splash page with logo: in my next mockup I'll leave off the example school logo.and move that frame to the end. It might be better to reserve a frame for customizable logo or message, before or after the Sugar spash page Yes, in that mockup the first screen is kind of overwhelming with several logos and a few pieces of textual information. At the same time, we tried very hard to eliminate the slideshow effect that feels (well, is) like a bunch of marketing material that detracts from the UI. I think the Sugar logo should stand alone, so it reads powerfully, and then be replaced in short order by the XO. Perhaps we could entertain a text only solution to identifying the school, in gray beneath the sugar logo. Thoughts? Version info: In fact I feel strongly about showing version information... or its corollary, making it easy to find. Teachers, I think it's more important that we make it easy to find in the UI. Kids won't reboot that often, and it would be silly to reboot just to find that info. parents, admins, G1G1 donors unfamiliar with Sugar will not have the foggiest idea how to hunt down version information (Learners might not have trouble finding it - they will explore their machines ad infinitum - but they can't be expected to know about versioning). We are about to embark on hundreds of thousands of XO-1.5s running v0..84 which will coexist with a huge installed base of v0.82 (and many earlier); SoaS with its simplified numbering scheme will (we hope) sow the seeds for preinstalled Sugar in distributions for education projects. We may be deploying v0.86 at the end of the year... aside from how we manage the Activity compatibility matrix, we need to make such info *extremely* easy to track down for someone interested in checking if Sugar + Activities are up-to-date. Our strategy for teacher buy-in is star marketing on Activities (see press releases); making Activity installation/upgrade simple this summer is part of what we need to do to make SoaS possible in the classroom. Helping users understand what version they have (of Sugar, of each Activity) is a key aspect of that. I agree that it's unpleasant to see numbers at boot time (especially a datestamped snapshot number). Why don't we borrow an idea from Apple? We basically have this already. We ust happen to have an XO in the center of the screen, instead of an apple icon in the upper left. The info is actually in the About my XO section of the settings, which might be one step too far. We could go back to an earlier design for the XO menu and have a direct About my XO menu item which jumps directly to the correct settings panel. We could also separate the About my XO panel from settings, removing it from the settings panel completely and showing it as it's own modal dialog accessible via an About my XO menu item. I would be fine with either approach. They have a tiny apple icon in the upper-left corner of the screen; clicking on it opens a window with the processor, RAM and OSX version number. In addition to the About my computer section in the Control Panel, perhaps we could show the version in the Frame? The bottom bar has room I think. There's no need to expose this information directly. It will only be needed on occasion, and the Frame is designed for the information you want to carry with you all the time. When we start to get consolidated feedback, we will know if difficult-to-find version info is a problem for Sugar / Activity updaters or not. I feel sure it is and showing the version in the Frame (the one-glance status communicator) seems to me a good approach which would let us skip info in the splash screen. Nota: my idea would be for each version to change the Sugar logo color too... potentially allowing troubleshooters to ask what color is the Sugar logo? and match that to the version number. I would much rather see the logo change colors with each boot, but I meant to take this back before sending, and forgot to. I actually think changing the colors with each release is a pretty awesome idea. Eben changing with each release is a pretty cool idea. I would support that. I think there are enough of combinations to make wrapping around
Re: [IAEP] [Marketing] [Sugar-devel] [SoaS] Request for Artwork: Boot Screen
Yes that would be very helpful I think If we can reach consensus by tomorrow and finish the actual PNG frames over the weekend we will meet the deadline but, we need a volunteer to do the frames (unless Gary what you have is nearly ready; my stuff is cut/pasted mockup no color control etc) thanks Sean On Thu, Jun 4, 2009 at 4:40 PM, Christian Marc Schmidt christianm...@gmail.com wrote: I agree with Eben's points below... Maybe it would help if one of us mocked up the alternative he is describing? Christian On Jun 4, 2009, at 10:35 AM, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 10:31 AM, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 7:24 AM, Sean DALY sdaly...@gmail.com wrote: http://wiki.sugarlabs.org/go/Marketing_Team/Boot_Logo Christian - I myself prefer the rays to dots which I feel too closely resemble networks in the Neighborhood view, confusion is possible (networks being connected to at startup?) Fred - I'm willing to try that sunrise metaphor, tonight if I can (travelling today) Re splash page with logo: in my next mockup I'll leave off the example school logo.and move that frame to the end. It might be better to reserve a frame for customizable logo or message, before or after the Sugar spash page Yes, in that mockup the first screen is kind of overwhelming with several logos and a few pieces of textual information. At the same time, we tried very hard to eliminate the slideshow effect that feels (well, is) like a bunch of marketing material that detracts from the UI. I think the Sugar logo should stand alone, so it reads powerfully, and then be replaced in short order by the XO. Perhaps we could entertain a text only solution to identifying the school, in gray beneath the sugar logo. Thoughts? Version info: In fact I feel strongly about showing version information... or its corollary, making it easy to find. Teachers, I think it's more important that we make it easy to find in the UI. Kids won't reboot that often, and it would be silly to reboot just to find that info. parents, admins, G1G1 donors unfamiliar with Sugar will not have the foggiest idea how to hunt down version information (Learners might not have trouble finding it - they will explore their machines ad infinitum - but they can't be expected to know about versioning). We are about to embark on hundreds of thousands of XO-1.5s running v0..84 which will coexist with a huge installed base of v0.82 (and many earlier); SoaS with its simplified numbering scheme will (we hope) sow the seeds for preinstalled Sugar in distributions for education projects. We may be deploying v0.86 at the end of the year... aside from how we manage the Activity compatibility matrix, we need to make such info *extremely* easy to track down for someone interested in checking if Sugar + Activities are up-to-date. Our strategy for teacher buy-in is star marketing on Activities (see press releases); making Activity installation/upgrade simple this summer is part of what we need to do to make SoaS possible in the classroom. Helping users understand what version they have (of Sugar, of each Activity) is a key aspect of that. I agree that it's unpleasant to see numbers at boot time (especially a datestamped snapshot number). Why don't we borrow an idea from Apple? We basically have this already. We ust happen to have an XO in the center of the screen, instead of an apple icon in the upper left. The info is actually in the About my XO section of the settings, which might be one step too far. We could go back to an earlier design for the XO menu and have a direct About my XO menu item which jumps directly to the correct settings panel. We could also separate the About my XO panel from settings, removing it from the settings panel completely and showing it as it's own modal dialog accessible via an About my XO menu item. I would be fine with either approach. They have a tiny apple icon in the upper-left corner of the screen; clicking on it opens a window with the processor, RAM and OSX version number. In addition to the About my computer section in the Control Panel, perhaps we could show the version in the Frame? The bottom bar has room I think. There's no need to expose this information directly. It will only be needed on occasion, and the Frame is designed for the information you want to carry with you all the time. When we start to get consolidated feedback, we will know if difficult-to-find version info is a problem for Sugar / Activity updaters or not. I feel sure it is and showing the version in the Frame (the one-glance status communicator) seems to me a good approach which would let us skip info in the splash screen. Nota: my idea would be for each version to change the Sugar logo color too... potentially allowing troubleshooters to ask what color is the Sugar logo? and match that to the version number. I would
Re: [IAEP] Introducing kids to Sugar
On Thu, 2009-06-04 at 16:28 +0200, Bernie Innocenti wrote: There's a possibility for a class of five graders in Florence to pilot SoaS next year. Our friends of OLPC Italia came up with a good question: how would an introductory class for Sugar work in practice? Both teachers and kids will be present to learn simultaneously, which makes things more interesting. Who actually went through such experience already? How was the class organized? What materials were used? And, more importantly, ware there any issues to watch out for? 1. Outside a class a introduced XO's a group of 6 kids. I used a freeform (no structure). Kids when to youtube and hyves and both sites did not work. Kids got frustrated of the XO's slowness. 2. I an class with only one XO we told the teacher let kids play as a bonus and ask afterward what they discovered. Here the kid like the XO a lot. My recommondation would are: guide form: - no internet first time - make groups with tasks - let childeren tell their experiance - Let the teacher not to be in charge off the class (take over control) - short time (one hour max) - make clear choise what to discover, - have goals per session (measuring succes) or if use free form: - no internet - limited time - no questions for teacher or guiders. - no active interventions, - no active observation, (do sometime else). - afterwards let kids tell - what not worked - what worked 2ct, Marten -- http://martenvijn.nl Marten Vijn http://martenvijn.nl/trac/wiki/soas Sugar on a Stick http://bsd.wifisoft.org/nek/ The Network Event Kit http://har2009.org 13th-16th August http://opencommunitycamp.org 26th Jul - 2nd August ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Marketing] Michael Trucano, World Bank EduTech blog: What have we learned from OLPC pilots to date?
Hi Mohammad, 2009/6/4 Mohammad Hamed m.ha...@paiwastoon.com.af: Dear Readers, Please don't open the attachment because if you click on attachment link it will automatically send your email address and password to the sender. I just attached the file that i get from olpc wiki 2 months ago. The original link is http://wiki.laptop.org/images/f/fb/Literature_Review_040309.pdf I didn't get any email address or password. Sincerely, Hi, 2009/6/2 Caroline Meeks carol...@solutiongrove.com: Has anyone been able to get to this document? The Australian Council for Educational Research has produced perhaps the most useful literature review of the�Evaluation of OLPC programs globally. enjoy... On Tue, Jun 2, 2009 at 7:10 AM, Sean DALY sdaly...@gmail.com wrote: http://blogs.worldbank.org/edutech/what-have-we-learned-from-olpc-pilots-to-date ___ Marketing mailing list market...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/marketing -- Caroline Meeks Solution Grove carol...@solutiongrove.com 617-500-3488 - Office 505-213-3268 - Fax ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep -- Maria del Pilar S�enz Sugar Labs Colombia ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep -- Pilar ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Marketing] [Sugar-devel] [SoaS] Request for Artwork: Boot Screen
On Thu, Jun 4, 2009 at 11:07 AM, Walter Bender walter.ben...@gmail.com wrote: On Thu, Jun 4, 2009 at 10:31 AM, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 7:24 AM, Sean DALY sdaly...@gmail.com wrote: http://wiki.sugarlabs.org/go/Marketing_Team/Boot_Logo Christian - I myself prefer the rays to dots which I feel too closely resemble networks in the Neighborhood view, confusion is possible (networks being connected to at startup?) Fred - I'm willing to try that sunrise metaphor, tonight if I can (travelling today) Re splash page with logo: in my next mockup I'll leave off the example school logo.and move that frame to the end. It might be better to reserve a frame for customizable logo or message, before or after the Sugar spash page Yes, in that mockup the first screen is kind of overwhelming with several logos and a few pieces of textual information. At the same time, we tried very hard to eliminate the slideshow effect that feels (well, is) like a bunch of marketing material that detracts from the UI. I think the Sugar logo should stand alone, so it reads powerfully, and then be replaced in short order by the XO. Perhaps we could entertain a text only solution to identifying the school, in gray beneath the sugar logo. Thoughts? +1 I don't have an XO nearby my to try this, so perhaps someone could investigate for me. We also need to decide how many frames we show the Sugar logo for before switching over to the XO. One frame might not be long enough. This is important because the number of dots shown (if we do dots) will be directly impacted. I'd wager that the Sugar logo should remain for perhaps somewhere from 10% to 25% of the boot duration (which may or may not be anything close to 1/10 or 1/4 of the frames). Eben Version info: In fact I feel strongly about showing version information... or its corollary, making it easy to find. Teachers, I think it's more important that we make it easy to find in the UI. Kids won't reboot that often, and it would be silly to reboot just to find that info. parents, admins, G1G1 donors unfamiliar with Sugar will not have the foggiest idea how to hunt down version information (Learners might not have trouble finding it - they will explore their machines ad infinitum - but they can't be expected to know about versioning). We are about to embark on hundreds of thousands of XO-1.5s running v0..84 which will coexist with a huge installed base of v0.82 (and many earlier); SoaS with its simplified numbering scheme will (we hope) sow the seeds for preinstalled Sugar in distributions for education projects. We may be deploying v0.86 at the end of the year... aside from how we manage the Activity compatibility matrix, we need to make such info *extremely* easy to track down for someone interested in checking if Sugar + Activities are up-to-date. Our strategy for teacher buy-in is star marketing on Activities (see press releases); making Activity installation/upgrade simple this summer is part of what we need to do to make SoaS possible in the classroom. Helping users understand what version they have (of Sugar, of each Activity) is a key aspect of that. I agree that it's unpleasant to see numbers at boot time (especially a datestamped snapshot number). Why don't we borrow an idea from Apple? We basically have this already. We ust happen to have an XO in the center of the screen, instead of an apple icon in the upper left. The info is actually in the About my XO section of the settings, which might be one step too far. We could go back to an earlier design for the XO menu and have a direct About my XO menu item which jumps directly to the correct settings panel. We could also separate the About my XO panel from settings, removing it from the settings panel completely and showing it as it's own modal dialog accessible via an About my XO menu item. I would be fine with either approach. They have a tiny apple icon in the upper-left corner of the screen; clicking on it opens a window with the processor, RAM and OSX version number. In addition to the About my computer section in the Control Panel, perhaps we could show the version in the Frame? The bottom bar has room I think. There's no need to expose this information directly. It will only be needed on occasion, and the Frame is designed for the information you want to carry with you all the time. When we start to get consolidated feedback, we will know if difficult-to-find version info is a problem for Sugar / Activity updaters or not. I feel sure it is and showing the version in the Frame (the one-glance status communicator) seems to me a good approach which would let us skip info in the splash screen. Nota: my idea would be for each version to change the Sugar logo color too... potentially allowing troubleshooters to ask what color is the Sugar logo? and match that to the version number. I would much rather see the
Re: [IAEP] [Marketing] [Sugar-devel] [SoaS] Request for Artwork: Boot Screen
On 4 Jun 2009, at 15:45, Sean DALY wrote: Yes that would be very helpful I think I was just going to start tinkering again, I'll make an animated version of Eben's XO and progress-bar for evaluation. If we can reach consensus by tomorrow and finish the actual PNG frames over the weekend we will meet the deadline but, we need a volunteer to do the frames (unless Gary what you have is nearly ready; my stuff is cut/pasted mockup no color control etc) Sure, getting a series of PNGs from any of my mock-ups is just a save for web away. Regards, --Gary thanks Sean On Thu, Jun 4, 2009 at 4:40 PM, Christian Marc Schmidt christianm...@gmail.com wrote: I agree with Eben's points below... Maybe it would help if one of us mocked up the alternative he is describing? Christian On Jun 4, 2009, at 10:35 AM, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 10:31 AM, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 7:24 AM, Sean DALY sdaly...@gmail.com wrote: http://wiki.sugarlabs.org/go/Marketing_Team/Boot_Logo Christian - I myself prefer the rays to dots which I feel too closely resemble networks in the Neighborhood view, confusion is possible (networks being connected to at startup?) Fred - I'm willing to try that sunrise metaphor, tonight if I can (travelling today) Re splash page with logo: in my next mockup I'll leave off the example school logo.and move that frame to the end. It might be better to reserve a frame for customizable logo or message, before or after the Sugar spash page Yes, in that mockup the first screen is kind of overwhelming with several logos and a few pieces of textual information. At the same time, we tried very hard to eliminate the slideshow effect that feels (well, is) like a bunch of marketing material that detracts from the UI. I think the Sugar logo should stand alone, so it reads powerfully, and then be replaced in short order by the XO. Perhaps we could entertain a text only solution to identifying the school, in gray beneath the sugar logo. Thoughts? Version info: In fact I feel strongly about showing version information... or its corollary, making it easy to find. Teachers, I think it's more important that we make it easy to find in the UI. Kids won't reboot that often, and it would be silly to reboot just to find that info. parents, admins, G1G1 donors unfamiliar with Sugar will not have the foggiest idea how to hunt down version information (Learners might not have trouble finding it - they will explore their machines ad infinitum - but they can't be expected to know about versioning). We are about to embark on hundreds of thousands of XO-1.5s running v0..84 which will coexist with a huge installed base of v0.82 (and many earlier); SoaS with its simplified numbering scheme will (we hope) sow the seeds for preinstalled Sugar in distributions for education projects. We may be deploying v0.86 at the end of the year... aside from how we manage the Activity compatibility matrix, we need to make such info *extremely* easy to track down for someone interested in checking if Sugar + Activities are up-to-date. Our strategy for teacher buy-in is star marketing on Activities (see press releases); making Activity installation/upgrade simple this summer is part of what we need to do to make SoaS possible in the classroom. Helping users understand what version they have (of Sugar, of each Activity) is a key aspect of that. I agree that it's unpleasant to see numbers at boot time (especially a datestamped snapshot number). Why don't we borrow an idea from Apple? We basically have this already. We ust happen to have an XO in the center of the screen, instead of an apple icon in the upper left. The info is actually in the About my XO section of the settings, which might be one step too far. We could go back to an earlier design for the XO menu and have a direct About my XO menu item which jumps directly to the correct settings panel. We could also separate the About my XO panel from settings, removing it from the settings panel completely and showing it as it's own modal dialog accessible via an About my XO menu item. I would be fine with either approach. They have a tiny apple icon in the upper-left corner of the screen; clicking on it opens a window with the processor, RAM and OSX version number. In addition to the About my computer section in the Control Panel, perhaps we could show the version in the Frame? The bottom bar has room I think. There's no need to expose this information directly. It will only be needed on occasion, and the Frame is designed for the information you want to carry with you all the time. When we start to get consolidated feedback, we will know if difficult-to-find version info is a problem for Sugar / Activity updaters or not. I
Re: [IAEP] Introducing kids to Sugar
On 06/04/09 17:05, Marten Vijn wrote: 1. Outside a class a introduced XO's a group of 6 kids. I used a freeform (no structure). Kids when to youtube and hyves and both sites did not work. Kids got frustrated of the XO's slowness. 2. I an class with only one XO we told the teacher let kids play as a bonus and ask afterward what they discovered. Here the kid like the XO a lot. My recommondation would are: guide form: - no internet first time - make groups with tasks - let childeren tell their experiance - Let the teacher not to be in charge off the class (take over control) - short time (one hour max) - make clear choise what to discover, - have goals per session (measuring succes) or if use free form: - no internet - limited time - no questions for teacher or guiders. - no active interventions, - no active observation, (do sometime else). - afterwards let kids tell - what not worked - what worked Thanks, that's very valuable information. Did in either the kids require any initial training or assistance to get started? How old were they? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Sugar Labs meet H-FOSS
On Thu, Jun 4, 2009 at 03:36, Frederick Grose fgr...@sugarlabs.org wrote: Credit Greg Dekoenigsberg for introducing some of us to Ralph Morelli, Heidi Ellis, and Trishan de Lanerolle, who have established the Humanitarian FOSS Project, http://www.hfoss.org/, growing out of Trinity College, Wesleyan University, and Connecticut College in the USA. David Farning suggested that we hold a conference call to share experiences about summer institutes, such as their http://www.hfoss.org/index.php?page=hfoss-summer-institute, and our http://wiki.sugarlabs.org/go/Sugar_Summer_Program. Then, Kevin Cole posted a referral, http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg04175.html, to Paul Flint's Barre Open Systems Institute, http://www.bosivt.org/, in Barre, Vermont USA. Karlie Robinson and I have been supporting Stephen Jacobs' Honors Seminar at the Rochester Institute of Technology, http://wiki.laptop.org/go/RIT_honors_seminar,_developing_for_the_OLPC_XO, the Math4 Project, http://wiki.sugarlabs.org/go/Math4Team, and Co-ops in the Rochester Sugar Summer Program. So today, we (David, Ralph, Heidi, Trishan, Stephen, Karlie, Paul, Fred) joined in a conference call to introduce ourselves and learn more about the project and programs. (A collection of web links are available from our conference at http://meeting.sugarlabs.org/sugar-meeting.minutes.20090603_1310.html, from a short irc log, http://meeting.sugarlabs.org/sugar-meeting.log.20090603_1310.html.) Ralph shared some history of the H-FOSS project, pretty much as reported on their home page, and Heidi pointed us to her SoftHum wiki, http://edudev.hfoss.org/index.php/Main_Page. Paul described his proposal for a small workshop in Barre, http://docbox.flint.com:8081/maple, (perhaps the weekend of 17-21 July 2009) to test install Sugar on a Stick on several old computers in schoolroom so they can support a team programming room for FOSS projects in the Barre Institute. Paul reports that Jeff Elkner with http://wiki.sugarlabs.org/go/Sugar_Labs_DC will be attending. In Rochester, we have a nascent Sugar Institute, http://wiki.sugarlabs.org/go/Sugar_Summer_Program/Ideas, with 3 full-time Co-ops and other members of the http://wiki.laptop.org/go/OLPC_Rochester,_NY grassroots special interest group, and we are open to more participants and guests willing to help build the program. This posting is to intended to expose the Sugar Labs community to our projects, and to invite a continuing discussion of how we all can contribute to building the Sugar and FOSS ecosystems. Thank you for reading, and we hope you are inspired to join in some way. Sounds great! Bring coders to sugar-devel and #sugar for help when they need it. Congratulations, Tomeu --Fred ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] SugarCamp Berlin
Hey all, We have just created at wiki page for coordinating events at SugarCamp Berlin[1] It looks like the best day for the formal SugarCamp will be on Sunday the 28th of June. This is going to be a interesting test of the how SugarCamp scales. Like SugarCamp Paris, I hope that this event is not viewed as a time for Sugar Labs to 'project its vision.' Instead, I hope that it can be used as a time for individuals and organizations interested in technology and early childhood education can come together and learn from each other and determine how we can build on each others work to make advances in technology available to Learners everywhere. Please add you name to the list so we can help set up room arrangements. david 1. http://wiki.sugarlabs.org/go/Marketing_Team/Events/SugarCamp_Berlin_2009 ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Marketing] [Sugar-devel] [SoaS] Request for Artwork: Boot Screen
58 posts in this thread and climbing:) I think that is a new Sugar Labs record. The results are looking great and getting better everyday. david On Thu, Jun 4, 2009 at 10:38 AM, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 11:07 AM, Walter Bender walter.ben...@gmail.com wrote: On Thu, Jun 4, 2009 at 10:31 AM, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 7:24 AM, Sean DALY sdaly...@gmail.com wrote: http://wiki.sugarlabs.org/go/Marketing_Team/Boot_Logo Christian - I myself prefer the rays to dots which I feel too closely resemble networks in the Neighborhood view, confusion is possible (networks being connected to at startup?) Fred - I'm willing to try that sunrise metaphor, tonight if I can (travelling today) Re splash page with logo: in my next mockup I'll leave off the example school logo.and move that frame to the end. It might be better to reserve a frame for customizable logo or message, before or after the Sugar spash page Yes, in that mockup the first screen is kind of overwhelming with several logos and a few pieces of textual information. At the same time, we tried very hard to eliminate the slideshow effect that feels (well, is) like a bunch of marketing material that detracts from the UI. I think the Sugar logo should stand alone, so it reads powerfully, and then be replaced in short order by the XO. Perhaps we could entertain a text only solution to identifying the school, in gray beneath the sugar logo. Thoughts? +1 I don't have an XO nearby my to try this, so perhaps someone could investigate for me. We also need to decide how many frames we show the Sugar logo for before switching over to the XO. One frame might not be long enough. This is important because the number of dots shown (if we do dots) will be directly impacted. I'd wager that the Sugar logo should remain for perhaps somewhere from 10% to 25% of the boot duration (which may or may not be anything close to 1/10 or 1/4 of the frames). Eben Version info: In fact I feel strongly about showing version information... or its corollary, making it easy to find. Teachers, I think it's more important that we make it easy to find in the UI. Kids won't reboot that often, and it would be silly to reboot just to find that info. parents, admins, G1G1 donors unfamiliar with Sugar will not have the foggiest idea how to hunt down version information (Learners might not have trouble finding it - they will explore their machines ad infinitum - but they can't be expected to know about versioning). We are about to embark on hundreds of thousands of XO-1.5s running v0..84 which will coexist with a huge installed base of v0.82 (and many earlier); SoaS with its simplified numbering scheme will (we hope) sow the seeds for preinstalled Sugar in distributions for education projects. We may be deploying v0.86 at the end of the year... aside from how we manage the Activity compatibility matrix, we need to make such info *extremely* easy to track down for someone interested in checking if Sugar + Activities are up-to-date. Our strategy for teacher buy-in is star marketing on Activities (see press releases); making Activity installation/upgrade simple this summer is part of what we need to do to make SoaS possible in the classroom. Helping users understand what version they have (of Sugar, of each Activity) is a key aspect of that. I agree that it's unpleasant to see numbers at boot time (especially a datestamped snapshot number). Why don't we borrow an idea from Apple? We basically have this already. We ust happen to have an XO in the center of the screen, instead of an apple icon in the upper left. The info is actually in the About my XO section of the settings, which might be one step too far. We could go back to an earlier design for the XO menu and have a direct About my XO menu item which jumps directly to the correct settings panel. We could also separate the About my XO panel from settings, removing it from the settings panel completely and showing it as it's own modal dialog accessible via an About my XO menu item. I would be fine with either approach. They have a tiny apple icon in the upper-left corner of the screen; clicking on it opens a window with the processor, RAM and OSX version number. In addition to the About my computer section in the Control Panel, perhaps we could show the version in the Frame? The bottom bar has room I think. There's no need to expose this information directly. It will only be needed on occasion, and the Frame is designed for the information you want to carry with you all the time. When we start to get consolidated feedback, we will know if difficult-to-find version info is a problem for Sugar / Activity updaters or not. I feel sure it is and showing the version in the Frame (the one-glance status communicator) seems to me a good approach which would let us skip info in the
Re: [IAEP] Introducing kids to Sugar
Most kids in developed countries know that some computers perform better than others, and use their favorite YouTube video as an informal benchmark. They are also exposed to the gadget culture of cellphones as MP3 players, videogame consoles, GPS car systems, and so on. An XO-1 faces stiff competition. My two older kids (12 and 10 at the time) immediately sussed out the most interesting functions the XO-1 offers: the Record Activity, and Chat over the mesh network. I deliberately kept them off the Internet and was in the room, but not looking over their shoulders. An XO-1 by itself lacks the collaboration aspect so central to the Sugar experience... need at least a pair to show what it can do :-) I showed SoaS to a friend recently, connected to his wireless network and the Neighborhood View filled up with friends from the jabber server. His eyes popped and he got really excited but then asked questions about how that will scale if hundreds/thousands of classrooms start using it ;-) Sean On Thu, Jun 4, 2009 at 6:07 PM, Bernie Innocenti ber...@codewiz.org wrote: On 06/04/09 17:05, Marten Vijn wrote: 1. Outside a class a introduced XO's a group of 6 kids. I used a freeform (no structure). Kids when to youtube and hyves and both sites did not work. Kids got frustrated of the XO's slowness. 2. I an class with only one XO we told the teacher let kids play as a bonus and ask afterward what they discovered. Here the kid like the XO a lot. My recommondation would are: guide form: - no internet first time - make groups with tasks - let childeren tell their experiance - Let the teacher not to be in charge off the class (take over control) - short time (one hour max) - make clear choise what to discover, - have goals per session (measuring succes) or if use free form: - no internet - limited time - no questions for teacher or guiders. - no active interventions, - no active observation, (do sometime else). - afterwards let kids tell - what not worked - what worked Thanks, that's very valuable information. Did in either the kids require any initial training or assistance to get started? How old were they? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Introducing kids to Sugar
On 06/04/09 21:05, Sean DALY wrote: I showed SoaS to a friend recently, connected to his wireless network and the Neighborhood View filled up with friends from the jabber server. His eyes popped and he got really excited but then asked questions about how that will scale if hundreds/thousands of classrooms start using it ;-) Darn engineers! They always have to be so picky and find logic flaws when you tell them about something wonderful like the World Wide Mesh, thus dispelling all the magic you believed in. :-) -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Marketing] [Sugar-devel] [SoaS] Request for Artwork: Boot Screen
Eben - it's not clear how many frames the plymouth boot sequencer needs or allows; it seems possible that (similar to animated GIFs) a frame duration can be set for some parts of the sequence, while others are related to the booting itself. Even the frame size may be variable; I've been using the XO-1.5's 425x425px. It's our wish to contact the lead plymouth developer, Ray Strode of Fedora, who I believe has stated he wishes plymouth to work on other distros Sean On Thu, Jun 4, 2009 at 5:38 PM, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 11:07 AM, Walter Bender walter.ben...@gmail.com wrote: On Thu, Jun 4, 2009 at 10:31 AM, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 7:24 AM, Sean DALY sdaly...@gmail.com wrote: http://wiki.sugarlabs.org/go/Marketing_Team/Boot_Logo Christian - I myself prefer the rays to dots which I feel too closely resemble networks in the Neighborhood view, confusion is possible (networks being connected to at startup?) Fred - I'm willing to try that sunrise metaphor, tonight if I can (travelling today) Re splash page with logo: in my next mockup I'll leave off the example school logo.and move that frame to the end. It might be better to reserve a frame for customizable logo or message, before or after the Sugar spash page Yes, in that mockup the first screen is kind of overwhelming with several logos and a few pieces of textual information. At the same time, we tried very hard to eliminate the slideshow effect that feels (well, is) like a bunch of marketing material that detracts from the UI. I think the Sugar logo should stand alone, so it reads powerfully, and then be replaced in short order by the XO. Perhaps we could entertain a text only solution to identifying the school, in gray beneath the sugar logo. Thoughts? +1 I don't have an XO nearby my to try this, so perhaps someone could investigate for me. We also need to decide how many frames we show the Sugar logo for before switching over to the XO. One frame might not be long enough. This is important because the number of dots shown (if we do dots) will be directly impacted. I'd wager that the Sugar logo should remain for perhaps somewhere from 10% to 25% of the boot duration (which may or may not be anything close to 1/10 or 1/4 of the frames). Eben Version info: In fact I feel strongly about showing version information... or its corollary, making it easy to find. Teachers, I think it's more important that we make it easy to find in the UI. Kids won't reboot that often, and it would be silly to reboot just to find that info. parents, admins, G1G1 donors unfamiliar with Sugar will not have the foggiest idea how to hunt down version information (Learners might not have trouble finding it - they will explore their machines ad infinitum - but they can't be expected to know about versioning). We are about to embark on hundreds of thousands of XO-1.5s running v0..84 which will coexist with a huge installed base of v0.82 (and many earlier); SoaS with its simplified numbering scheme will (we hope) sow the seeds for preinstalled Sugar in distributions for education projects. We may be deploying v0.86 at the end of the year... aside from how we manage the Activity compatibility matrix, we need to make such info *extremely* easy to track down for someone interested in checking if Sugar + Activities are up-to-date. Our strategy for teacher buy-in is star marketing on Activities (see press releases); making Activity installation/upgrade simple this summer is part of what we need to do to make SoaS possible in the classroom. Helping users understand what version they have (of Sugar, of each Activity) is a key aspect of that. I agree that it's unpleasant to see numbers at boot time (especially a datestamped snapshot number). Why don't we borrow an idea from Apple? We basically have this already. We ust happen to have an XO in the center of the screen, instead of an apple icon in the upper left. The info is actually in the About my XO section of the settings, which might be one step too far. We could go back to an earlier design for the XO menu and have a direct About my XO menu item which jumps directly to the correct settings panel. We could also separate the About my XO panel from settings, removing it from the settings panel completely and showing it as it's own modal dialog accessible via an About my XO menu item. I would be fine with either approach. They have a tiny apple icon in the upper-left corner of the screen; clicking on it opens a window with the processor, RAM and OSX version number. In addition to the About my computer section in the Control Panel, perhaps we could show the version in the Frame? The bottom bar has room I think. There's no need to expose this information directly. It will only be needed on occasion, and the Frame is designed for the information you want to carry with you
Re: [IAEP] [Marketing] [Sugar-devel] [SoaS] Request for Artwork: Boot Screen
On Thu, Jun 4, 2009 at 16:35, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 10:31 AM, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 7:24 AM, Sean DALY sdaly...@gmail.com wrote: http://wiki.sugarlabs.org/go/Marketing_Team/Boot_Logo Christian - I myself prefer the rays to dots which I feel too closely resemble networks in the Neighborhood view, confusion is possible (networks being connected to at startup?) Fred - I'm willing to try that sunrise metaphor, tonight if I can (travelling today) Re splash page with logo: in my next mockup I'll leave off the example school logo.and move that frame to the end. It might be better to reserve a frame for customizable logo or message, before or after the Sugar spash page Yes, in that mockup the first screen is kind of overwhelming with several logos and a few pieces of textual information. At the same time, we tried very hard to eliminate the slideshow effect that feels (well, is) like a bunch of marketing material that detracts from the UI. I think the Sugar logo should stand alone, so it reads powerfully, and then be replaced in short order by the XO. Perhaps we could entertain a text only solution to identifying the school, in gray beneath the sugar logo. Thoughts? Version info: In fact I feel strongly about showing version information... or its corollary, making it easy to find. Teachers, I think it's more important that we make it easy to find in the UI. Kids won't reboot that often, and it would be silly to reboot just to find that info. parents, admins, G1G1 donors unfamiliar with Sugar will not have the foggiest idea how to hunt down version information (Learners might not have trouble finding it - they will explore their machines ad infinitum - but they can't be expected to know about versioning). We are about to embark on hundreds of thousands of XO-1.5s running v0..84 which will coexist with a huge installed base of v0.82 (and many earlier); SoaS with its simplified numbering scheme will (we hope) sow the seeds for preinstalled Sugar in distributions for education projects. We may be deploying v0.86 at the end of the year... aside from how we manage the Activity compatibility matrix, we need to make such info *extremely* easy to track down for someone interested in checking if Sugar + Activities are up-to-date. Our strategy for teacher buy-in is star marketing on Activities (see press releases); making Activity installation/upgrade simple this summer is part of what we need to do to make SoaS possible in the classroom. Helping users understand what version they have (of Sugar, of each Activity) is a key aspect of that. I agree that it's unpleasant to see numbers at boot time (especially a datestamped snapshot number). Why don't we borrow an idea from Apple? We basically have this already. We ust happen to have an XO in the center of the screen, instead of an apple icon in the upper left. The info is actually in the About my XO section of the settings, which might be one step too far. We could go back to an earlier design for the XO menu and have a direct About my XO menu item which jumps directly to the correct settings panel. We could also separate the About my XO panel from settings, removing it from the settings panel completely and showing it as it's own modal dialog accessible via an About my XO menu item. I would be fine with either approach. They have a tiny apple icon in the upper-left corner of the screen; clicking on it opens a window with the processor, RAM and OSX version number. In addition to the About my computer section in the Control Panel, perhaps we could show the version in the Frame? The bottom bar has room I think. There's no need to expose this information directly. It will only be needed on occasion, and the Frame is designed for the information you want to carry with you all the time. When we start to get consolidated feedback, we will know if difficult-to-find version info is a problem for Sugar / Activity updaters or not. I feel sure it is and showing the version in the Frame (the one-glance status communicator) seems to me a good approach which would let us skip info in the splash screen. Nota: my idea would be for each version to change the Sugar logo color too... potentially allowing troubleshooters to ask what color is the Sugar logo? and match that to the version number. I would much rather see the logo change colors with each boot, but I meant to take this back before sending, and forgot to. I actually think changing the colors with each release is a pretty awesome idea. So awesome that it may solve the controversial issue of naming releases: Banana-Chocolate Sugar, Cherry-Oak Sugar, etc Regards, Tomeu Eben changing with each release is a pretty cool idea. I would support that. I think there are enough of combinations to make wrapping around a non-issue, as long as we only change the
Re: [IAEP] [Marketing] [Sugar-devel] [SoaS] Request for Artwork: Boot Screen
On 4 Jun 2009, at 16:35, Gary C Martin wrote: On 4 Jun 2009, at 15:45, Sean DALY wrote: Yes that would be very helpful I think I was just going to start tinkering again, I'll make an animated version of Eben's XO and progress-bar for evaluation. Just uploaded an animated version showing Eben's boot with progress bar treatment: http://wiki.sugarlabs.org/go/Image:XO-sugar-boot-with-progress-bar.gif FWIW: +1 on Eben's suggestion for changing the colour of the Sugar logo for each major new Sugar release. It nicely avoids what looks like jumping through lot's of technical burning hoops of fire, trying to set up a boot anim that dynamically changes to match the owners own colours (nice idea but I think a big ask at this point in time). FWIW2: Just incase any one was wondering, the colour dot versions were based on the 1-12 official Sugar Logo treatment colour pairs, i.e definitely not not random :-) Regards, --Gary If we can reach consensus by tomorrow and finish the actual PNG frames over the weekend we will meet the deadline but, we need a volunteer to do the frames (unless Gary what you have is nearly ready; my stuff is cut/pasted mockup no color control etc) Sure, getting a series of PNGs from any of my mock-ups is just a save for web away. Regards, --Gary thanks Sean On Thu, Jun 4, 2009 at 4:40 PM, Christian Marc Schmidt christianm...@gmail.com wrote: I agree with Eben's points below... Maybe it would help if one of us mocked up the alternative he is describing? Christian On Jun 4, 2009, at 10:35 AM, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 10:31 AM, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 7:24 AM, Sean DALY sdaly...@gmail.com wrote: http://wiki.sugarlabs.org/go/Marketing_Team/Boot_Logo Christian - I myself prefer the rays to dots which I feel too closely resemble networks in the Neighborhood view, confusion is possible (networks being connected to at startup?) Fred - I'm willing to try that sunrise metaphor, tonight if I can (travelling today) Re splash page with logo: in my next mockup I'll leave off the example school logo.and move that frame to the end. It might be better to reserve a frame for customizable logo or message, before or after the Sugar spash page Yes, in that mockup the first screen is kind of overwhelming with several logos and a few pieces of textual information. At the same time, we tried very hard to eliminate the slideshow effect that feels (well, is) like a bunch of marketing material that detracts from the UI. I think the Sugar logo should stand alone, so it reads powerfully, and then be replaced in short order by the XO. Perhaps we could entertain a text only solution to identifying the school, in gray beneath the sugar logo. Thoughts? Version info: In fact I feel strongly about showing version information... or its corollary, making it easy to find. Teachers, I think it's more important that we make it easy to find in the UI. Kids won't reboot that often, and it would be silly to reboot just to find that info. parents, admins, G1G1 donors unfamiliar with Sugar will not have the foggiest idea how to hunt down version information (Learners might not have trouble finding it - they will explore their machines ad infinitum - but they can't be expected to know about versioning). We are about to embark on hundreds of thousands of XO-1.5s running v0..84 which will coexist with a huge installed base of v0.82 (and many earlier); SoaS with its simplified numbering scheme will (we hope) sow the seeds for preinstalled Sugar in distributions for education projects. We may be deploying v0.86 at the end of the year... aside from how we manage the Activity compatibility matrix, we need to make such info *extremely* easy to track down for someone interested in checking if Sugar + Activities are up-to-date. Our strategy for teacher buy-in is star marketing on Activities (see press releases); making Activity installation/upgrade simple this summer is part of what we need to do to make SoaS possible in the classroom. Helping users understand what version they have (of Sugar, of each Activity) is a key aspect of that. I agree that it's unpleasant to see numbers at boot time (especially a datestamped snapshot number). Why don't we borrow an idea from Apple? We basically have this already. We ust happen to have an XO in the center of the screen, instead of an apple icon in the upper left. The info is actually in the About my XO section of the settings, which might be one step too far. We could go back to an earlier design for the XO menu and have a direct About my XO menu item which jumps directly to the correct settings panel. We could also separate the About my XO panel from settings, removing it from the settings panel completely and showing it as it's own modal dialog
Re: [IAEP] [Marketing] [Sugar-devel] [SoaS] Request for Artwork: Boot Screen
Flavors - now that's a horse of a different color :D Yes, it may yet help us - the whole point of beta and v1 of SoaS was to simplify the arcane mysterious Sugar Labs / OLPC version numbering system :-) Sean On Thu, Jun 4, 2009 at 9:24 PM, Tomeu Vizoso to...@sugarlabs.org wrote: On Thu, Jun 4, 2009 at 16:35, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 10:31 AM, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 7:24 AM, Sean DALY sdaly...@gmail.com wrote: http://wiki.sugarlabs.org/go/Marketing_Team/Boot_Logo Christian - I myself prefer the rays to dots which I feel too closely resemble networks in the Neighborhood view, confusion is possible (networks being connected to at startup?) Fred - I'm willing to try that sunrise metaphor, tonight if I can (travelling today) Re splash page with logo: in my next mockup I'll leave off the example school logo.and move that frame to the end. It might be better to reserve a frame for customizable logo or message, before or after the Sugar spash page Yes, in that mockup the first screen is kind of overwhelming with several logos and a few pieces of textual information. At the same time, we tried very hard to eliminate the slideshow effect that feels (well, is) like a bunch of marketing material that detracts from the UI. I think the Sugar logo should stand alone, so it reads powerfully, and then be replaced in short order by the XO. Perhaps we could entertain a text only solution to identifying the school, in gray beneath the sugar logo. Thoughts? Version info: In fact I feel strongly about showing version information... or its corollary, making it easy to find. Teachers, I think it's more important that we make it easy to find in the UI. Kids won't reboot that often, and it would be silly to reboot just to find that info. parents, admins, G1G1 donors unfamiliar with Sugar will not have the foggiest idea how to hunt down version information (Learners might not have trouble finding it - they will explore their machines ad infinitum - but they can't be expected to know about versioning). We are about to embark on hundreds of thousands of XO-1.5s running v0..84 which will coexist with a huge installed base of v0.82 (and many earlier); SoaS with its simplified numbering scheme will (we hope) sow the seeds for preinstalled Sugar in distributions for education projects. We may be deploying v0.86 at the end of the year... aside from how we manage the Activity compatibility matrix, we need to make such info *extremely* easy to track down for someone interested in checking if Sugar + Activities are up-to-date. Our strategy for teacher buy-in is star marketing on Activities (see press releases); making Activity installation/upgrade simple this summer is part of what we need to do to make SoaS possible in the classroom. Helping users understand what version they have (of Sugar, of each Activity) is a key aspect of that. I agree that it's unpleasant to see numbers at boot time (especially a datestamped snapshot number). Why don't we borrow an idea from Apple? We basically have this already. We ust happen to have an XO in the center of the screen, instead of an apple icon in the upper left. The info is actually in the About my XO section of the settings, which might be one step too far. We could go back to an earlier design for the XO menu and have a direct About my XO menu item which jumps directly to the correct settings panel. We could also separate the About my XO panel from settings, removing it from the settings panel completely and showing it as it's own modal dialog accessible via an About my XO menu item. I would be fine with either approach. They have a tiny apple icon in the upper-left corner of the screen; clicking on it opens a window with the processor, RAM and OSX version number. In addition to the About my computer section in the Control Panel, perhaps we could show the version in the Frame? The bottom bar has room I think. There's no need to expose this information directly. It will only be needed on occasion, and the Frame is designed for the information you want to carry with you all the time. When we start to get consolidated feedback, we will know if difficult-to-find version info is a problem for Sugar / Activity updaters or not. I feel sure it is and showing the version in the Frame (the one-glance status communicator) seems to me a good approach which would let us skip info in the splash screen. Nota: my idea would be for each version to change the Sugar logo color too... potentially allowing troubleshooters to ask what color is the Sugar logo? and match that to the version number. I would much rather see the logo change colors with each boot, but I meant to take this back before sending, and forgot to. I actually think changing the colors with each release is a pretty awesome idea. So awesome that it may solve the
Re: [IAEP] [Marketing] [Sugar-devel] [SoaS] Request for Artwork: Boot Screen
Actually the logo color linked to a version idea was in my long mail the other day about communicating the version :-) I too think 2 changes a year will give us time to cycle through the twelve variants. To make that work, the actual place where the version number is communicated (Control Panel / About my computer) would need to have the matching color Sugar Labs (not just Sugar) logo. I like this progress bar boot screen because: * ultrasimple, unobtrusive, fits perfectly with Sugar HIG * bar is universally easy to understand, no possibility of confusion with graphic elements. * keeping logo around that long=strong branding, which is vital for Sugar to be recognized by name rather than just the system running on XOs, netbooks, etc. I miss the iconic ring treatment though. And, no matter how clean we would like it to be, we still need to address the questions of school/sponsor co-branding (if they have a logo, they won't feel like jst putting their name in grey) and distro co-branding. Perhaps we could solve those problems by putting them in the About my computer page as well? Awful as far as co-branding goes (partners would not be happy), but will keep boot minimalist and functional. For a shining example of how more-is-less packaging is ruinous, may I direct your attention to: http://www.youtube.com/watch?v=EUXnJraKM3k Sean On Thu, Jun 4, 2009 at 9:44 PM, Gary C Martin g...@garycmartin.com wrote: On 4 Jun 2009, at 16:35, Gary C Martin wrote: On 4 Jun 2009, at 15:45, Sean DALY wrote: Yes that would be very helpful I think I was just going to start tinkering again, I'll make an animated version of Eben's XO and progress-bar for evaluation. Just uploaded an animated version showing Eben's boot with progress bar treatment: http://wiki.sugarlabs.org/go/Image:XO-sugar-boot-with-progress-bar.gif FWIW: +1 on Eben's suggestion for changing the colour of the Sugar logo for each major new Sugar release. It nicely avoids what looks like jumping through lot's of technical burning hoops of fire, trying to set up a boot anim that dynamically changes to match the owners own colours (nice idea but I think a big ask at this point in time). FWIW2: Just incase any one was wondering, the colour dot versions were based on the 1-12 official Sugar Logo treatment colour pairs, i.e definitely not not random :-) Regards, --Gary If we can reach consensus by tomorrow and finish the actual PNG frames over the weekend we will meet the deadline but, we need a volunteer to do the frames (unless Gary what you have is nearly ready; my stuff is cut/pasted mockup no color control etc) Sure, getting a series of PNGs from any of my mock-ups is just a save for web away. Regards, --Gary thanks Sean On Thu, Jun 4, 2009 at 4:40 PM, Christian Marc Schmidt christianm...@gmail.com wrote: I agree with Eben's points below... Maybe it would help if one of us mocked up the alternative he is describing? Christian On Jun 4, 2009, at 10:35 AM, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 10:31 AM, Eben Eliason eben.elia...@gmail.com wrote: On Thu, Jun 4, 2009 at 7:24 AM, Sean DALY sdaly...@gmail.com wrote: http://wiki.sugarlabs.org/go/Marketing_Team/Boot_Logo Christian - I myself prefer the rays to dots which I feel too closely resemble networks in the Neighborhood view, confusion is possible (networks being connected to at startup?) Fred - I'm willing to try that sunrise metaphor, tonight if I can (travelling today) Re splash page with logo: in my next mockup I'll leave off the example school logo.and move that frame to the end. It might be better to reserve a frame for customizable logo or message, before or after the Sugar spash page Yes, in that mockup the first screen is kind of overwhelming with several logos and a few pieces of textual information. At the same time, we tried very hard to eliminate the slideshow effect that feels (well, is) like a bunch of marketing material that detracts from the UI. I think the Sugar logo should stand alone, so it reads powerfully, and then be replaced in short order by the XO. Perhaps we could entertain a text only solution to identifying the school, in gray beneath the sugar logo. Thoughts? Version info: In fact I feel strongly about showing version information... or its corollary, making it easy to find. Teachers, I think it's more important that we make it easy to find in the UI. Kids won't reboot that often, and it would be silly to reboot just to find that info. parents, admins, G1G1 donors unfamiliar with Sugar will not have the foggiest idea how to hunt down version information (Learners might not have trouble finding it - they will explore their machines ad infinitum - but they can't be expected to know about versioning). We are about to embark on hundreds of thousands of XO-1.5s running v0..84 which will coexist with a huge installed base of v0.82 (and many
Re: [IAEP] OLPC Volunteer Infrastructure Group Meeting: [Today]
http://wiki.laptop.org/go/OLPC:Volunteer_Infrastructure_Group#Meeting_Minutes_and_Logsis the location. On Thu, Jun 4, 2009 at 2:31 PM, David Farning dfarn...@sugarlabs.orgwrote: Dogi, Can you post a link to the logs? david On Tue, Jun 2, 2009 at 1:05 PM, Stefan Unterhauser d...@laptop.org wrote: The Volunteer Infrastructure Group (/gang) Meeting is today (June 2th) at 4pm (EST) The Volunteer Infrastructure Group is a team of Volunteer Sysadmins who help maintain services and systems around OLPC and the OLPC/SugarLabs community. The weekly VIG meeting is an excellent chance to get involved, or to be aware of upcoming projects. http://wiki.laptop.org/go/OLPC:Volunteer_Infrastructure_Group http://vig.laptop.org/wiki/index.php/User:Dogi http://idea.laptop.org/ideatorrent/ideatorrent/vig/ http://embed.mibbit.com/?server=irc.oftc.netchannel=%23olpc-adminsettings=12a698505c860f99a6ad1051c57975f9noServerTab=falsenoServerNotices=truenoServerMotd=truenick=Guest Agenda: * backup: new VM for streaming to a robot tape solution * pinguin: new www * meeting: new structure and meeting.sugarlabs.org * vig and wiki (testwiki): migration plan * idea: help promote this idea function * rt: migration plan * maps: there new datas on deployments * bigsister: new VM on w91 Meeting Details: Date: June 2th, 2009 Time: 16:00 EST Location: irc.oftc.net #olpc-admin or click on - http://embed.mibbit.com/?server=irc.oftc.netchannel=%23olpc-adminsettings=12a698505c860f99a6ad1051c57975f9noServerTab=falsenoServerNotices=truenoServerMotd=truenick=Guest ciao dogi ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ 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] Introducing kids to Sugar
Ask the olpc_bos...@lists.laptop.org list - they just did this with 6th graders in Cambridge. If you find me on IRC, I can tell you what I know as well. (Hm. Must prod Harvard students to post more notes about how this went.) --Mel ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [SoaS] New Snapshot: Activity Updates
On Wed, Jun 3, 2009 at 4:18 PM, Sebastian Dziallas sebast...@when.comwrote: Hi everybody, I'm really happy to announce this new snapshot, which brings you quite some changes, compared to the last version. So what's waiting for you? * Fixed DPI size issue on the XO - should look better now Does not boot on XO, hangs after message about loading initrd. Can anyone duplicate or get it to boot on XO? Use LiveUSB creator on F11 Preview. Identical model USB stick with 20090528 created the same way boots on the XO. /boot/olpc.fth exists (obviously since it gets to the initrd stage). Dave * Included Library and Tux Paint; updated Record activity * updated Turtle Art to the latest version - thanks to Bryan Walter As always, please report issues you encounter. Here are the new links: Live Image: http://download.sugarlabs.org/soas/snapshots/2/Soas2-200906031834.iso Virtual Appliance: http://download.sugarlabs.org/soas/appliances/soas2-20090603.zip Boot Helper: http://people.sugarlabs.org/sdz/soas-boot-20090603.iso Thanks and happy testing, --Sebastian ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep -- Dave Bauer d...@solutiongrove.com http://www.solutiongrove.com ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [SoaS] New Snapshot: Activity Updates
On Wed, Jun 3, 2009 at 4:18 PM, Sebastian Dziallas sebast...@when.comwrote: Hi everybody, I'm really happy to announce this new snapshot, which brings you quite some changes, compared to the last version. So what's waiting for you? * Fixed DPI size issue on the XO - should look better now * Included Library and Tux Paint; updated Record activity Record on eeepc 901! Photo and video work. Audio works but volume is very low even with volume control all the way up. Still very cool! Dave * updated Turtle Art to the latest version - thanks to Bryan Walter As always, please report issues you encounter. Here are the new links: Live Image: http://download.sugarlabs.org/soas/snapshots/2/Soas2-200906031834.iso Virtual Appliance: http://download.sugarlabs.org/soas/appliances/soas2-20090603.zip Boot Helper: http://people.sugarlabs.org/sdz/soas-boot-20090603.iso Thanks and happy testing, --Sebastian ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep -- Dave Bauer d...@solutiongrove.com http://www.solutiongrove.com ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] OLPC Volunteer Infrastructure Group Meeting: [Today]
Dogi, Can you post a link to the logs? david On Tue, Jun 2, 2009 at 1:05 PM, Stefan Unterhauser d...@laptop.org wrote: The Volunteer Infrastructure Group (/gang) Meeting is today (June 2th) at 4pm (EST) The Volunteer Infrastructure Group is a team of Volunteer Sysadmins who help maintain services and systems around OLPC and the OLPC/SugarLabs community. The weekly VIG meeting is an excellent chance to get involved, or to be aware of upcoming projects. http://wiki.laptop.org/go/OLPC:Volunteer_Infrastructure_Group http://vig.laptop.org/wiki/index.php/User:Dogi http://idea.laptop.org/ideatorrent/ideatorrent/vig/ http://embed.mibbit.com/?server=irc.oftc.netchannel=%23olpc-adminsettings=12a698505c860f99a6ad1051c57975f9noServerTab=falsenoServerNotices=truenoServerMotd=truenick=Guest Agenda: * backup: new VM for streaming to a robot tape solution * pinguin: new www * meeting: new structure and meeting.sugarlabs.org * vig and wiki (testwiki): migration plan * idea: help promote this idea function * rt: migration plan * maps: there new datas on deployments * bigsister: new VM on w91 Meeting Details: Date: June 2th, 2009 Time: 16:00 EST Location: irc.oftc.net #olpc-admin or click on - http://embed.mibbit.com/?server=irc.oftc.netchannel=%23olpc-adminsettings=12a698505c860f99a6ad1051c57975f9noServerTab=falsenoServerNotices=truenoServerMotd=truenick=Guest ciao dogi ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Unbootable machine
Bernie Innocenti wrote: Equally weird. The only standard ones are 64 heads, 32 sectors and 255 heads, 63 sectors. Indeed, repartitioning the USB stick with 32 sectors and 255 heads fixed boot for a previously unbootable computer. 32x255? That's an odd mix? Does 32x64 work on that machine, too? -hpa ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Unbootable machine
Bernie Innocenti wrote: Sorry, I mistyped the numbers. It was really 255 heads, 63 sectors: (parted) p Model: LEXAR JD EXPRESSION (scsi) Disk /dev/sdb: 123,86,26 Sector size (logical/physical): 512B/512B BIOS cylinder,head,sector geometry: 123,255,63. Each cylinder is 8225kB. Partition Table: msdos Ah, okay. Does 64x32 work, too? I'm trying to gather as much information about what makes sticks boot... -hpa ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] Fwd: [Nsdl-all] ECDL 2009 - STUDENT SCHOLARSHIPS
It would be great to have a representative of the Sugar community there. -- Forwarded message -- From: Tsakonas Giannis j...@lis.upatras.gr Date: Thu, Jun 4, 2009 at 4:26 PM Subject: [Nsdl-all] ECDL 2009 - STUDENT SCHOLARSHIPS To: nsdl-...@nsdl.org ---Apologies for cross-posting--- 13th European Conference on Digital Libraries (ECDL 2009): Digital Societies September 27 - October 2, 2009, Corfu, Greece http://www.ecdl2009.eu --STUDENT SCHOLARSHIPS-- The Organizing Committee of ECDL 2009, with the valuable assistance of sponsoring organizations, will provide the following scholarships: * Conference fees for three (3) students * Conference fees and travel support for two (2) students Additional sources for support are being sought for students not covered by any of these options. Please, note that students selected for support may be asked to spend some fraction of their time onsite helping the Organizing Committee as student volunteers. Priority will be given to authors of papers in the Doctoral Consortium, the main conference or even the Workshops. If interested, please email Mrs. Ntina Kakali (nka...@panteion.gr), your (1) vita with contact details, (2) roles in the conference (e.g., author, attendee, reviewer, etc.) and (3) a description of your financial circumstances, and in particular, whether your department or advisor can provide partial support (e.g., matching funds) until Sunday, June 21. The results will be announced through this page until July 10. ___ Nsdl-all mailing list nsdl-...@nsdl.org http://comm.nsdl.org/mailman/listinfo/nsdl-all -- Caroline Meeks Solution Grove carol...@solutiongrove.com 617-500-3488 - Office 505-213-3268 - Fax ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] collaboration testing session
Hi folks, We are having a collaborative sugar testing session next week Wednesday 10th June at 20:00 UTC (That is 4 pm EDT, 3pm EST, 2 pm CST, 1 pm MST, and 12 pm PST, most of Europe that will be 9 pm, 8 pm for the UK) So far we have 5 people signed up, but more are welcome as we really want to see how collaboration works on many activities where it isn't quite obvious. We will be taking notes and storing log files of the sessions, and will suggest ways in which the activity in question might be more collaborative, or may need less of it (who knows :-) We will be testing the activities that come preinstalled on the openSUSE sugar images, but we'd like to test various distribution methods (virtual appliance, cd, usb, hd) and various distros (at least Fedora SoaS, openSUSE sugar, Mandriva or Caixa Magica) I dont believe 0.82 images are compatible with 0.84 for collaboration, so am afraid this is for 0.84 only... Please post your willingness to participate so we have an idea on who/how many will be collaborating. We also need a volunteer to take notes, and a volunteer to store logs files. There will of course be a transcript of the irc session too (we will meet at #sugar-collaboration) We forsee this taking between 1 and 2 hours... Here is the list of activities we will be testing, so make sure you have them installed if you plan to take part (not all have collaborative abilities, and for those that don't it can be a brainstorming session on whether/how we can make them collaborative: sugar-finance sugar-flipsticks-activity sugar-freecell sugar-imageviewer sugar-implode sugar-infoslicer sugar-jigsaw-puzzle-activity sugar-joke-machine-activity sugar-jukebox sugar-labyrinth sugar-maze sugar-memorize sugar-moon sugar-paint-activity sugar-pippy sugar-playgo sugar-read sugar-readetexts-activity sugar-record sugar-slider-puzzle-activity sugar-speak sugar-storybuilder sugar-tamtam-common sugar-tamtam-edit sugar-tamtam-jam sugar-tamtam-mini sugar-tamtam-synthlab sugar-analyze sugar-turtleart sugar-typing-turtle sugar-viewslides sugar-write sugar-browse sugar-irc sugar-calculate sugar-xomail (sugar-sweetmail) sugar-cartoonbuilder sugar-clock sugar-colors sugar-connect sugar-drgeo-activity xoEditor sugar-evince sugar-fiftytwo sugar-chat sugar-terminal sugar-journal sugar-physics sugar-library sugar-poll sugar-tuxpaint kind Regards, David (nubae) Van Assche www.nubae.com ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] ASLO - rebranding
Hi everyone, I've been working on the css for ASLO, you can see where I'm at http://activities-devel.sugarlabs.org/en-US/sugar/ . I've tried to make this fairly consistent with the design of sugarlabs.org. If any developers would be kind enough to upload some activities it would help with checking for inconsistencies it would be greatly appreciated. I'd like to push this to the live site in the near future, so please let me know what you think. Cheers, Josh ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
