Count me in as well. This is a wonderful idea and could very well be what is necessary to make the wish list of Activities proposals real.
Nirav On Sun, Jan 11, 2009 at 5:09 AM, Arjun Sarwal <ar...@laptop.org> wrote: > +1 > I am in too. > > Arjun > > On Sun, Jan 11, 2009 at 3:02 PM, Tomeu Vizoso <to...@sugarlabs.org> wrote: >> >> I believe this will make a very big difference in the future of Sugar. >> >> Good luck and have fun, >> >> Tomeu >> >> On Sat, Jan 10, 2009 at 19:46, Wade Brainerd <wad...@gmail.com> 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 >> > >> _______________________________________________ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel > > > > -- > Arjun Sarwal > > > _______________________________________________ > 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