[IAEP] Calendar
Hi, I'm trying to setup a calendar for Squeakland like the one you are using on the sugar labs wiki. I do have some questions about that. So if the person, who did the sugar labs calendar, is reading this, please send me a short notice if you have time to help me! To have a calendar overview for Squeakland events could help to better coordinate Sugar Labs and Squeakland events Greetings, Rita Squeakland Foundation http://www.squeakland.org ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] Interaction Design and Children - conference
There is a conference in Barcelona in June called Interaction Design and Children http://www.iua.upf.es/idc2010/call.htm Is anyone here interested in attending? Greetings, Rita Squeakland Foundation http://www.squeakland.org ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Mockup for collab.sugarlabs.org
On Wed, Jan 6, 2010 at 12:24 PM, Aleksey Lim alsr...@member.fsf.org wrote: http://wiki.sugarlabs.org/go/Collab_mockup I see that you are pointing to Ubuntu's brainstorm, which has a huge overlap with the wiki-ish blueprints and tasks/bugs as tracked in launchpad/malone. Comparing Ubuntu's brainstorm with their own use of blueprints+bugtracker, the blueprints+bugtracker win big time. Brainstorm takes a lot of page / screen real state for very few tasks, and the quality of discussion/interaction isn't very high. Maybe a better path for users to get into the wikipages that Walter mentioned (Feature Request, etc) would work? cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Mockup for collab.sugarlabs.org
On Thu, Jan 07, 2010 at 12:22:55PM +0100, Martin Langhoff wrote: On Wed, Jan 6, 2010 at 12:24 PM, Aleksey Lim alsr...@member.fsf.org wrote: http://wiki.sugarlabs.org/go/Collab_mockup I see that you are pointing to Ubuntu's brainstorm, which has a huge overlap with the wiki-ish blueprints and tasks/bugs as tracked in launchpad/malone. it was just a possible way to go Comparing Ubuntu's brainstorm with their own use of blueprints+bugtracker, the blueprints+bugtracker win big time. Brainstorm takes a lot of page / screen real state for very few tasks, and the quality of discussion/interaction isn't very high. Maybe a better path for users to get into the wikipages that Walter mentioned (Feature Request, etc) would work? well, as was mentioned in this thread, collab.sl.o is not intended to do something unique(but maybe unique view), everything could be done reusing existed infrastructure. The problem with existed methods could be costs of supporting, keeping in mind casual and decentralized sugar nature. Well other FOSS projects have these issues as well but do we have many community coordinators who will, on regular bases, track various sources like dozen of wiki pages (on several servers), dozen emails(on several servers) to coordinate all these efforts. Also collab.sl.o is not intended to be organisation driven portal but community driven. For example OLPC could have more effective ways to treat all these issues due to having administrative resources, collab.sl.o could give community replacement of OLPC's administrative resource. Another possible issue is not friendly to non-tech and casual sugar users, with collab.sl.o's requester mode, it could be more useful for people who lacks of some feature and wants to: expose this, track progress of implementation w/o UI which encumbered with many development related components. Possible analogy is wiki.laptop.org vs. ASLO. -- Aleksey ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Mockup for collab.sugarlabs.org
On Thu, Jan 07, 2010 at 12:20:30PM +, Aleksey Lim wrote: On Thu, Jan 07, 2010 at 12:22:55PM +0100, Martin Langhoff wrote: On Wed, Jan 6, 2010 at 12:24 PM, Aleksey Lim alsr...@member.fsf.org wrote: http://wiki.sugarlabs.org/go/Collab_mockup I see that you are pointing to Ubuntu's brainstorm, which has a huge overlap with the wiki-ish blueprints and tasks/bugs as tracked in launchpad/malone. it was just a possible way to go Comparing Ubuntu's brainstorm with their own use of blueprints+bugtracker, the blueprints+bugtracker win big time. Brainstorm takes a lot of page / screen real state for very few tasks, and the quality of discussion/interaction isn't very high. Maybe a better path for users to get into the wikipages that Walter mentioned (Feature Request, etc) would work? well, as was mentioned in this thread, collab.sl.o is not intended to do something unique(but maybe unique view), everything could be done reusing existed infrastructure. The problem with existed methods could be costs of supporting, keeping in mind casual and decentralized sugar nature. Well other FOSS projects have these issues as well but do we have many community coordinators who will, on regular bases, track various sources like dozen of wiki pages (on several servers), dozen emails(on several servers) to coordinate all these efforts. Also collab.sl.o is not intended to be organisation driven portal but community driven. For example OLPC could have more effective ways to treat all these issues due to having administrative resources, collab.sl.o could give community replacement of OLPC's administrative resource. maybe I wasn't enough clear, tools like wiki are to common, e.g. why people use bugs tracker instead of wiki or mls. Another possible issue is not friendly to non-tech and casual sugar users, with collab.sl.o's requester mode, it could be more useful for people who lacks of some feature and wants to: expose this, track progress of implementation w/o UI which encumbered with many development related components. Possible analogy is wiki.laptop.org vs. ASLO. -- Aleksey -- Aleksey ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Mockup for collab.sugarlabs.org
On Thu, Jan 07, 2010 at 01:34:04PM +0100, Martin Langhoff wrote: On Thu, Jan 7, 2010 at 1:23 PM, Aleksey Lim alsr...@member.fsf.org wrote: maybe I wasn't enough clear, tools like wiki are to common, e.g. why people use bugs tracker instead of wiki or mls. Trackers, um, track state of the issues/bugs/tasks, and let you - form a narrow forum of discussion on a very specific topic - minimising noise at the expense of reducing the number of eyes - track completion towards an overall goal Mailing lists have again a different dynamic. But what you are looking for seems to me exactly what the feature request = blueprints = tracker workflow achieves. SL has it right now. Major concerns I had in mind were: * let non-tech users(not even deployments) to expose theirs requests in simple and convenient way: * tools like wiki are too common and we have to remind people all time to follow some rules * much better to have ASLO for requests(needs), when user opens site which contain only requests(w/o bunch of related development info) * people can browse/vote/create requests and track implementation progress(just fact of completion). All development info could be accessible from development resources(request page could contain links). * having such convenient tool will stimulate sugar users to share their needs and make sugar development process more flexible when developers do what is a real need for sugar users rather what they think is * such collab.sl.o could be the first place where interested in contribution people could go, even casual participant e.g. if you are a designer and have spare time for these weekends, just open collab.sl.o, search for artwork requests and implement some of them (browsing wiki or ml could be painful) * one of side effects of such site would be more coordinated development process, developers know what is going on and where the place they can contribute right now All mentioned above could be(already) done in existed env. But the major idea of collab.sl.o proposal is bringing life to existed scheme by stimulating users to share their needs(due to having convenient ASLO for needs site). About launchpad, maybe I'm wrong but launchpad seems to me targeted more for developers and experienced users who test development releases or at least post bugs. I'm personally for lightweight collab.sl.o(to meet only mentioned above issues) and reusing existed development related resources like wiki/launchpad/mls for development process. -- Aleksey ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] Calendar
Hi Rita, Although I didn't do it for Sugar Labs, I've done it for other projects (e.g. the DC Ubuntu LoCo calendar -- http://dc.ubuntu-us.org/GoogleCalendar-- which is embarrassingly empty at the moment). It's fairly straightforward: Create a Google Calendar, then go to Calendar Settings for the particular calendar, and under the Calendar Details tab you'll find: Embed This Calendar Embed this calendar in your website or blog by pasting this code into your web page. To embed multiple calendars, click on the Customize Link Just copy and paste the URL offered into your web site. You can also do fancy things with the RSS and ICAL feeds listed on the Settings page as well. -- Ubuntu Linux DC LoCo Washington, DC http://dc.ubuntu-us.org/ ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] Sugar Digest 2010-01-07
=== Sugar Digest === 1. Aleksey Lim has started a discussion [http://lists.sugarlabs.org/archive/iaep/2010-January/009726.html] about how to better coordinate—in a more welcoming and friendly manner—our various development activities with the needs of deployments. This complements the Luke Faraone's thread [http://lists.sugarlabs.org/archive/iaep/2009-December/009668.html] from a few weeks ago about a redesign of the website, based in part from feedback from the Babson team's study [[http://wiki.sugarlabs.org/go/File:Sugar_Deployment_in_US_Schools_Report.pdf]]. The gist of the various conversations is that we need to tackle a typical Free-Software project issue: how can we make the project more friendly and accessible to non-technical people; and, related, manage the explosion of pages, sites, points of view on the project without limiting expression on the part of individual contributors. Part of the answer certainly lies in providing a bit more structure to our website. Part of the answer likely lies in more outreach to where the non-techies hang out. (I had put together a survey last year for the teachers in Uruguay to solicit feedback on this topic, but alas, it was never conducted.) I am not sure we know what are the best channels for reaching teachers, parents, etc. In any case, it is an important issue for us. Please contribute to the discussion. === In the community === 2. Bruno Coudoin announced the release of GCompris Version 9.0. Aleksey is already working on making sure that it is properly packaged for Sugar and available on http://activities.sugarlabs.org. 3. As I mentioned a few weeks ago, Jim Simmons has been working on a beginner's guide to creating Sugar Activities. He has made great progress and is at the point where some constructive criticize would be helpful (Please see http://en.flossmanuals.net/ActivitiesGuideSugar/Introduction). === Help wanted === 4. David Farning has been working on an Ubuntu-Sugar remix. He is looking for help with testing. The release can be downloaded from http://people.sugarlabs.org/dfarning/. === Tech talk === 5. Aleksey has been busy working on Sugar Services [[[http://wiki.sugarlabs.org/go/Activity_Team/Services]]—a decentralized means of supporting Sugar Activity dependencies. He announced that the first version is ready to test or use in simple cases. Please refer to the wiki for more details about Sugar Services ([[[http://wiki.sugarlabs.org/go/Documentation_Team/Services/Activity_Developers_Guide#Known_issue]], [[[http://wiki.sugarlabs.org/go/Activity_Team/Services#Workflows]], [[[http://wiki.sugarlabs.org/go/Activity_Team/Services#What_is_Sugar_Services_not.3F]]). 6. Simon Schampijer has resurfaced the discussion about Resume vs Start new activity instance from the Home View (http://lists.sugarlabs.org/archive/sugar-devel/2010-January/021771.html). Please contribute your thoughts and observations from the field. === Sugar Labs === 12. Gary Martin has generated a SOM from the past week of discussion on the IAEP mailing list (Please see [[http://wiki.sugarlabs.org/go/File:2009-Dec-26-Jan-1-som.jpg|SOM]]). Happy New Year everyone. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
