+1 I am in too. Arjun <div class="gmail_quote">On Sun, Jan 11, 2009 at 3:02 PM, Tomeu Vizoso <<a href="mailto:tomeu@sugarlabs.org">tomeu@sugarlabs.org</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I believe this will make a very big difference in the future of Sugar. Good luck and have fun, Tomeu <div><div></div><div class="Wj3C7c"> On Sat, Jan 10, 2009 at 19:46, Wade Brainerd <<a href="mailto:wadetb@gmail.com">wadetb@gmail.com</a>> 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 > <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </div></div></blockquote></div> -- Arjun Sarwal