Re: [Sugar-devel] Education on the XO
On Sat, Jan 3, 2009 at 4:31 AM, Tony Anderson wrote: > Bryan has started a very interesting discussion about what is needed for > the XO to support education. I would like to add my two cents worth. > > We are learning (gaining new experience) every day that we are alive. > The traditional difference in education is that it is organized > learning. Teaching a topic means to provide an organized tour of an area > of knowledge covering what every student should know or be aware of. > > The XO's primary tool for education, as opposed to learning experiences, > is Moodle. The problem is that Moodle for the XO is a tool which is > ready and waiting to be used (all dressed up and no where to go). > > My vision is that there is a repository (website) which contains free > (CC or similar) courses covering the core curriculum for K-8. The > website needs to be supported by a community of developers (course > creators) and moderators (folks who volunteer to assist teachers and > students who are participating). This repository should also contain > 'elective' courses following the model of Oregon's Saturday Academy > (http://www.saturdayacademy.org/). Earth Treasury is working on that plan with a number of other partners. We welcome others to participate. http://wiki.sugarlabs.org/go/Creating_textbooks > The primary problem with Moodle at the moment is that there are is not a > body of grade school courses available to illustrate how to build them > or to provoke the community to 'make it better'. Exactly. > Tony -- Silent Thunder (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) is my name And Children are my nation. The Cosmos is my dwelling place, The Truth my destination. http://wiki.sugarlabs.org/go/User:Mokurai ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fwd: Google Summer of Code 2009 is a go!
On reflection, I think it might be a good thing to make a single really excellent mentoring framework for people through sugarlabs, and not to have two gsoc programs at all. OLPC will have a good bit of mentoring to do to look after travelling interns, which is likely to be a larger program than it was last year. People who write OLPC asking to mentor or intern for software can be directed to that program. And people who have gsoc experience through other groups can help with the setup / to make sure sugarlabs isn't treated like a novice participant. --SJ On Sat, Jan 10, 2009 at 10:51 AM, Simon Schampijer wrote: > Mel Chua wrote: >> That depends on what OLPC's GSoC focus is - it may *not* be Sugar at >> all, in which case the organizational intern allocations should be (and >> they should be, anyway!) independent of each other. >> >> Marcin, do you recall where you heard/saw that rule? Googling for things >> like "gsoc limit of 2 students" isn't getting me anywhere - I want to >> have a few moments to read through all the docs and historical paperwork >> before emailing Leslie (likely tomorrow, as there will be time to catch >> my breath then). >> >> Is anybody here, aside from SJ, a former GSoC coordinator who can chime >> in / fill in details / help? I am *completely *swamped for the next 24 >> hours wrapping up the "becoming a volunteer again" process. >> >> --Mel > > I did mentor Hemant Goyal on sugar speech synthesis. > http://wiki.laptop.org/index.php?title=User:Hemant_goyal We did quite ok > during the program. I would probably set stricter schedule in terms of > wrapping up the status and milestones. But apart from that I was quite > heppy what we achieved and I think Hemant was as well, I think. > > About the slots I can not say much, I only did fill out forms for the > assessment. > > Regards, >Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ActivityTeam proposal
On 10 Jan 2009, at 18:46, Wade Brainerd wrote: > And that's why I'm proposing the creation of a SugarLabs ActivityTeam. > The new team will be separate from the DevelopmentTeam, and will have > the responsibility of maintaining and extending the suite of > activities available for Sugar. > > We will: > 1. Maintain and develop the current suite of Sugar activities. > 2. Recruit and mentor activity developers from the community. > 3. Collect, document and organize new activity and activity feature > ideas from the EducationTeam, deployments and community. > 4. Work with the DevelopmentTeam and the InfrastructureTeam to ensure > activity developers are well supported. > 5. Gather feedback with the DeploymentTeam about how Sugar activities > are doing in the field. > > Until now, activity development has largely been an individual effort. > The purpose of this proposal is to collect the activity development > community into an effective team who can tackle the entire ecosystem > of Sugar activities together. One result should be fewer activities > "dropping off the radar" into lack of maintenance. > > Please respond with your feedback about the proposal. If you like the > idea and would like to be part of the ATeam, feel free to indicate > that. Yes, count me in! > Best, > Wade ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ActivityTeam proposal
Yep, once activities.sugarlabs.org is up and running (help wanted btw!) we should be able to keep this up to date. I hope to 'feature' orphaned activities from time to time to try to help get them picked up as well. Suggestions for which one to start with are welcome, I was thinking maybe 'Connect' since it was part of the initial Sugar vision. -Wade On Sat, Jan 10, 2009 at 4:34 PM, Aleksey Lim wrote: > On Sat, Jan 10, 2009 at 01:46:56PM -0500, Wade Brainerd wrote: >> One result should be fewer activities >> "dropping off the radar" into lack of maintenance. > > I suggest using explicit status of activity's maintenance > at least active and orphaned - to encourage people to pick up unsupported > activities > > -- > Aleksey > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ActivityTeam proposal
On Sat, Jan 10, 2009 at 01:46:56PM -0500, Wade Brainerd wrote: > One result should be fewer activities > "dropping off the radar" into lack of maintenance. I suggest using explicit status of activity's maintenance at least active and orphaned - to encourage people to pick up unsupported activities -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ActivityTeam proposal
Hi Wadeb. I've done a draft wiki page for the activity team http://sugarlabs.org/go/ActivityTeam Please edit it at your will. cheers. Rafael Ortiz On Sat, Jan 10, 2009 at 3:27 PM, Marco Pesenti Gritti wrote: > +1, this is awesome! > > Marco > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ActivityTeam proposal
+1, this is awesome! Marco ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ActivityTeam proposal
Where is a place I could enter myself into :) On Sat, Jan 10, 2009 at 01:46:56PM -0500, Wade Brainerd wrote: > Hi all, hope you are enjoying FUDcon. > > Given the recent events at OLPC, I'm planning to refocus my activity > development efforts on SugarLabs. I imagine other activity developers > are planning to do the same. > > SugarLabs is off to a great start getting packages into distributions, > but I can't help noticing that the activities on the home page are > essentially the same were shipped with OLPC build 650 back in 2007. > > One of the things that drew me to Sugar and OLPC was the promise of > high quality, collaborative, constructivist educational software. > While the initial activity set was good, it was also clear that there > were large holes to be filled. For a variety reasons, many of those > holes remain two years later. > > And that's why I'm proposing the creation of a SugarLabs ActivityTeam. > The new team will be separate from the DevelopmentTeam, and will have > the responsibility of maintaining and extending the suite of > activities available for Sugar. > > We will: > 1. Maintain and develop the current suite of Sugar activities. > 2. Recruit and mentor activity developers from the community. > 3. Collect, document and organize new activity and activity feature > ideas from the EducationTeam, deployments and community. > 4. Work with the DevelopmentTeam and the InfrastructureTeam to ensure > activity developers are well supported. > 5. Gather feedback with the DeploymentTeam about how Sugar activities > are doing in the field. > > Until now, activity development has largely been an individual effort. > The purpose of this proposal is to collect the activity development > community into an effective team who can tackle the entire ecosystem > of Sugar activities together. One result should be fewer activities > "dropping off the radar" into lack of maintenance. > > Please respond with your feedback about the proposal. If you like the > idea and would like to be part of the ATeam, feel free to indicate > that. > > Best, > Wade > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] idea for Sugar slogan and name
I came up w/ an idea that would help us market Sugar to the general public. We need a slogan expresses what Sugar allows kids to do, its purpose, and puts a positive image in the minds of most people. Here is my slogan suggestion: "Sugarland: Where Kids Learn and Play" Adding "Land" expresses that Sugarland, e.g. Sugar, is a whole environment where kids learn, play, express themselves, create, etc. Words like "platform", "engine", "environment" sound like tools for adults and don't indicate that this is a tool for children. I also like "Playground: Where Kids Learn and Play" Playground expresses a safe place for kids to play but doesn't necessarily convey "learning" to a lot of people. -- Bryan W. Berry Technology Director OLE Nepal, http://www.olenepal.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ActivityTeam proposal
+1 I'll join. -walter On Sat, Jan 10, 2009 at 1:46 PM, Wade Brainerd wrote: > Hi all, hope you are enjoying FUDcon. > > Given the recent events at OLPC, I'm planning to refocus my activity > development efforts on SugarLabs. I imagine other activity developers > are planning to do the same. > > SugarLabs is off to a great start getting packages into distributions, > but I can't help noticing that the activities on the home page are > essentially the same were shipped with OLPC build 650 back in 2007. > > One of the things that drew me to Sugar and OLPC was the promise of > high quality, collaborative, constructivist educational software. > While the initial activity set was good, it was also clear that there > were large holes to be filled. For a variety reasons, many of those > holes remain two years later. > > And that's why I'm proposing the creation of a SugarLabs ActivityTeam. > The new team will be separate from the DevelopmentTeam, and will have > the responsibility of maintaining and extending the suite of > activities available for Sugar. > > We will: > 1. Maintain and develop the current suite of Sugar activities. > 2. Recruit and mentor activity developers from the community. > 3. Collect, document and organize new activity and activity feature > ideas from the EducationTeam, deployments and community. > 4. Work with the DevelopmentTeam and the InfrastructureTeam to ensure > activity developers are well supported. > 5. Gather feedback with the DeploymentTeam about how Sugar activities > are doing in the field. > > Until now, activity development has largely been an individual effort. > The purpose of this proposal is to collect the activity development > community into an effective team who can tackle the entire ecosystem > of Sugar activities together. One result should be fewer activities > "dropping off the radar" into lack of maintenance. > > Please respond with your feedback about the proposal. If you like the > idea and would like to be part of the ATeam, feel free to indicate > that. > > Best, > Wade > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] ActivityTeam proposal
Hi all, hope you are enjoying FUDcon. Given the recent events at OLPC, I'm planning to refocus my activity development efforts on SugarLabs. I imagine other activity developers are planning to do the same. SugarLabs is off to a great start getting packages into distributions, but I can't help noticing that the activities on the home page are essentially the same were shipped with OLPC build 650 back in 2007. One of the things that drew me to Sugar and OLPC was the promise of high quality, collaborative, constructivist educational software. While the initial activity set was good, it was also clear that there were large holes to be filled. For a variety reasons, many of those holes remain two years later. And that's why I'm proposing the creation of a SugarLabs ActivityTeam. The new team will be separate from the DevelopmentTeam, and will have the responsibility of maintaining and extending the suite of activities available for Sugar. We will: 1. Maintain and develop the current suite of Sugar activities. 2. Recruit and mentor activity developers from the community. 3. Collect, document and organize new activity and activity feature ideas from the EducationTeam, deployments and community. 4. Work with the DevelopmentTeam and the InfrastructureTeam to ensure activity developers are well supported. 5. Gather feedback with the DeploymentTeam about how Sugar activities are doing in the field. Until now, activity development has largely been an individual effort. The purpose of this proposal is to collect the activity development community into an effective team who can tackle the entire ecosystem of Sugar activities together. One result should be fewer activities "dropping off the radar" into lack of maintenance. Please respond with your feedback about the proposal. If you like the idea and would like to be part of the ATeam, feel free to indicate that. Best, Wade ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ANNOUNCE] Reminder - Sucrose 0.84 Feature Freeze the 15.01.09
Hi all, the Feature, API, String freeze is getting close (15.01.09) [1]. Please land your pending features, check items in the TODO list and verify that all the new strings are exposed and do not contain any typing errors. Wish you some upcoming productive days, Your Release Team [1] http://sugarlabs.org/go/DevelopmentTeam/Release/Roadmap#Schedule [2] http://sugarlabs.org/go/DevelopmentTeam/TODO [3] http://en.wikipedia.org/wiki/Freeze_(software_engineering) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Cerebro v3.0: File sharing and buddy management made easy!
Hi, On Sat, Jan 10, 2009 at 8:54 AM, Bert Freudenberg wrote: > > How could an activity make use of this? All you have to do is follow the tutorial. In the sample gui there is also an example chat session. > Is it integrated with > Telepathy - could it be - will it be? Not integrated at the moment. Not sure about the future, but I'm afraid I have too much on my plate right now. ;) > It reads like this is a totally > different mesh protocol. Different than what? The XO's mesh network? Yes it is. Cerebro's mesh capabilities are meant to be used with regular wifi devices. > If it cannot be integrated, Cerebro is quite modular; its module that provides presence information could be substituted for information arriving from the XO's firmware, except that the firmware does not provide information on the layout of the network. > could it be run in parallel? Of course. p. > > > - Bert - > > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fwd: Google Summer of Code 2009 is a go!
Mel Chua wrote: > That depends on what OLPC's GSoC focus is - it may *not* be Sugar at > all, in which case the organizational intern allocations should be (and > they should be, anyway!) independent of each other. > > Marcin, do you recall where you heard/saw that rule? Googling for things > like "gsoc limit of 2 students" isn't getting me anywhere - I want to > have a few moments to read through all the docs and historical paperwork > before emailing Leslie (likely tomorrow, as there will be time to catch > my breath then). > > Is anybody here, aside from SJ, a former GSoC coordinator who can chime > in / fill in details / help? I am *completely *swamped for the next 24 > hours wrapping up the "becoming a volunteer again" process. > > --Mel I did mentor Hemant Goyal on sugar speech synthesis. http://wiki.laptop.org/index.php?title=User:Hemant_goyal We did quite ok during the program. I would probably set stricter schedule in terms of wrapping up the status and milestones. But apart from that I was quite heppy what we achieved and I think Hemant was as well, I think. About the slots I can not say much, I only did fill out forms for the assessment. Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Cerebro v3.0: File sharing and buddy management made easy!
On 10.01.2009, at 04:18, Polychronis Ypodimatopoulos wrote: > Hi, > > On Fri, Jan 9, 2009 at 7:25 AM, Sayamindu Dasgupta > wrote: >> Wow - this looks cool :) >> Is this a "blessed dependency" for Sugar 0.84 ? Also, are there any >> Sugar activities which is already using this ? > > Not that I know of. > Cheers, > > Pol How could an activity make use of this? Is it integrated with Telepathy - could it be - will it be? It reads like this is a totally different mesh protocol. If it cannot be integrated, could it be run in parallel? - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
