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
