[Sugar-devel] ActivityTeam proposal
bcjordan at gmail.com
Mon Jan 12 15:09:05 EST 2009
On Mon, Jan 12, 2009 at 2:26 PM, Wade Brainerd <wadetb at gmail.com> wrote:
> Hello again,
> If you would like to join the ActivityTeam, the Contact page at
> http://sugarlabs.org/go/ActivityTeam/Contacts is available for you to
> add your name.
> When adding your name to the list, please take a minute and decide how
> you will contribute to the effort. Then, go over to the To Do List at
> http://sugarlabs.org/go/ActivityTeam/TODO and put your name down next
> to something using four tildes (~~~~).
> A lot of tasks are as simple as moving a Git repository or making sure
> activities have up to date tarballs for distribution. There are also
> bigger tasks like helping to get activities.sugarlabs.org running or
> taking up one of the High Impact tasks from the other thread.
(Pardon my inexperience with Gitorious)
To become a contributor to an activity, is the suggested process (1)
make account on Gitorious, (2) email owner of project directly, (3)
wait to be added, (4) commit changes?
What do you think about adding an active ActivityTeam coordinator to
be an admin for each activity project, in case (3) takes a while? Or
is there a global admin role that would allow for something like this?
Over analyzing imaginary bottlenecks,
> Looking forward to seeing you there!
> PS - I'm hoping to make it down to XOcamp one evening this week,
> either Tuesday or Wednesday.
> On Sat, Jan 10, 2009 at 1:46 PM, Wade Brainerd <wadetb at 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
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
More information about the Sugar-devel