Difference between revisions of "Activity Team"

From Sugar Labs
Jump to navigation Jump to search
m (fix camelcase links)
m (fix camelcase links)
Line 44: Line 44:
===sugar-widgets library===
===sugar-widgets library===
*A [[Activity Team/ProjectIdeas#sugar-widgets library|set]] of widgets/classes that could be valuable for writing new activity.
*A [[Activity Team/Project Ideas#sugar-widgets library|set]] of widgets/classes that could be valuable for writing new activity.
===Activity HIG (Human Interface Guidelines)===
===Activity HIG (Human Interface Guidelines)===
*[[Activity Team/ProjectIdeas#Activity HIG|Activity HIG]] discussion
*[[Activity Team/Project Ideas#Activity HIG|Activity HIG]] discussion
===Packaging activities discussion===  
===Packaging activities discussion===  

Revision as of 15:17, 3 April 2009

Team Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Meetings


The Activity Team develops and maintains many of the activities available for Sugar. We also encourage independent developers to write activities, and we support them in their efforts. Our goal is to ensure that Sugar provides a complete set of high quality educational, collaborative, constructivist activities.

Our responsibilities

  1. Develop and maintain the ecosystem 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 Education Team, deployments and community.
  4. Work with the Development Team and the Infrastructure Team to ensure activity developers are well supported.
  5. Gather feedback with the Deployment Team about how Sugar activities are doing in the field.


Problems logging in to Gitorious?

Gitorious users are sometimes having their IP addresses incorrectly blacklisted by OUOSL, the organization that hosts git.sugarlabs.org. If your SSH key is rejected with the error "Access denied or bad repository path", please open a ticket by emailing support@ouosl.org.

This has happened to a number of activity authors and we are working on getting it resolved.

Wade 22:04, 6 March 2009 (UTC)

For more info see tickets:

  • #418 Resolve Gitorious blacklisting issues with OUOSL
  • #523 Access denied or bad repository path while pushing to git.s.o

Activity Team users on activities.sugarlabs.org

Fake emails to identify users:

  • activity.team@sugarlabs.org activities that are supported by Activity Team
  • trash@dev.null activities to remove

Sugar Activities

There is an Activities page where we highlight Sugar activities in the wiki. (We need to discuss how best to manage the content of this page as well as how to manage the activity-specific sub-pages.)

Sugar Human Interface Guidelines

The Sugar Human Interface Guidelines content has also been migrated to Sugar Labs. This guide is a critical resource when designing activities. Wade 18:35, 19 February 2009 (UTC)

Sugar Almanac

The Sugar Almanac content has been migrated to Sugar Labs. It's a great, quick reference when building python Activities.

Modify Activities

A guide has been written describing how to make simple modifications to popular Sugar activities. Examples include adding sounds to TamTam, blocks to TurtleArt, buttons to Calculate, etc.


Hacking is under way on the new user-facing portal for Sugar activities, http://activities.sugarlabs.org/! The site uses the backend Mozilla built for Firefox and Thunderbird extensions at addons.mozilla.org, called Remora. To help out, check out Activity Team/Remora_port.

Wade 15:02, 27 January 2009 (UTC)

sugar-widgets library

  • A set of widgets/classes that could be valuable for writing new activity.

Activity HIG (Human Interface Guidelines)

Packaging activities discussion

We are currently discussing how to package activities in the future, in order to support all distributions. Please add your comments to the following pages.

  • Packaging
    • should we remove "Activities" section from that page; all issues where moved to Activity_Status page alsroot 10:33, 16 January 2009 (UTC)
  • Packaging ideas

Wade 17:19, 13 January 2009 (UTC)

Move an activity

We need help moving activities over to Sugar Labs from OLPC's servers. This is a great way to get started helping out the Activity Team. See Activity Team/How_to_migrate_from_OLPC for instructions, and Activity Team/Activity Status for the list of activities that need to be moved.

While moving activities, it would be great to check that the .pot files are up to date and the MANIFEST is correct. This will really help out the distro packagers.

Wade 17:19, 13 January 2009 (UTC)

General Overview of git and gitorious

Gitorious is the web front-end to git, the revision control system that Sugar Labs uses for project hosting. Once you have migrated your project, as an Activity developer, you may encounter some of these questions.

John Wiegley has written an overview of git: Git from the bottom up.

Cross-platform compatibility

As Sugar is integrated into more distros and the hardware base expands, it is important to keep Activity developers informed of any issues they need be aware of. For example, when Sugar was only expected to run on the XO-1 laptop, it was safe to assume that the display was always 1200x900.

The Compatibility Tips page is a place to accumulate tips.

Project Ideas

The Activity Team always needs project ideas and suggestions. Post your ideas to Activity Team/Project Ideas.

If you see something here you would like to help with, please contact us.

Wade 17:19, 13 January 2009 (UTC)


Please check /Meetings for meeting schedules/logs.