Activity Team/TODO

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

When you plan to take a task from the list, please sign and date it using four tildes.

* task name ˜˜˜˜

When a task is complete, strike it out.

<strike>task name</strike>

High Impact Tasks

These are tasks which will have a big impact on Sugar deployments. This is your chance to affect hundreds, if not thousands of children in the developing world! This section will be updated frequently to feature the most urgent work the Activity Team has to do.

Labyrinth

Labyrinth is a mind mapping activity. Gary C Martin is currently leading the port of this PyGTK program to Sugar. Mind mapping software has been specifically requested by teachers at deployments. Labyrinth needs help improving and extending the user interface, so PyGTK skills would be important. Or, collaboration would be a great addition!

I'm making good progress here, main issues resolve around whether I treat this as a fork, there seems a lot of changes needed deeper down in the Labyrinth code to make this really novice user friendly, lot's of stray code and odd behaviours floating around once you start digging. -Garycmartin 23:23, 12 January 2009 (UTC)

Typing Turtle

Typing Turtle is a touch typing activity with a turtle mascot. We are developing activity this with the Nepal and Afganistan deployments. Peru has also requested this activity as a high priority. TT is in pre-alpha but is close to its first release. Help is mostly needed testing and fixing the activity for use with foreign languages, and developing the lesson builder script. GUI programming experience is not critical, but Python skills and i18n knowledge, as well as the ability to work in a language other than English would be very useful.

Math

A request by the Peru deployment is simple math games. I have started working on some math puzzles with Peter Moxhay, based a suite of Java lessons he wrote in the past. These are very early in development but there are a lot of games to write. Also, examples are available, so it's really just porting and the work goes quickly. Ysun 19:50, 12 January 2009 (UTC)ysun

Maze collaboration

Maze is currently the most addictive multiplayer game on the XO, and it needs a further dusting of crack, including better statistics, handicaps, etc.

Speak collaboration

This has the potential to be an awesome communication method; not only a chat option for the blind but a way of teaching specific words, and a fun way to engage small clusters of people around an XO: sound carries well to people who aren't currently reading the screen.

SWF activity launcher

The Nepal deployment have created a suite of Flash based learning activities but are currently having to jump through many hoops to package them correctly. We would like to have a launcher which creates an activity window and launches Gnash in it, with a .SWF file. This launcher would then be used to easily make activity bundles out of SWF files.

Web activity launcher & framework

Other deployments are using HTML+CSS+Javascript to make learning activities, but they currently have to be installed using the Library Collection feature of Sugar which is not well developed. We would like to build a 'web-activity' launcher script which allows Web based activities to be first class activities with icons on the home screens. This would involve making a new framework out of the source code to the Browse activity and submitting it upstream to the DevelopmentTeam, in addition to writing the launcher script.

Community Tasks

  • Announce availability of ATeam contacts page to mailing lists. Wade 17:26, 12 January 2009 (UTC)
  • Query ATeam members about skills, interest, time commitment. Wade 17:26, 12 January 2009 (UTC)
  • Look for at least one additional coordinator.
  • Contact former + current activity developers. Wade 17:26, 12 January 2009 (UTC)
    • Ask about moving activities to git.sugarlabs.org (or mirroring).
    • Ask about joining the ActivityTeam or coming to meetings.

Infrastructure Tasks

  • Make activities.sugarlabs.org (or addons.sugarlabs.org) work. See ActivityTeam/Remora_port.
  • Move projects owned by ATeam members over to git.sugarlabs.org and downloads.sugarlabs.org
    See ActivityTeam/How_to_migrate_from_OLPC for activity migration instructions.
    See ActivityTeam/ActivityStatus for a list of projects that need to be moved.
  • Bug IT to get us admin accounts for SL services.
    • Downloads (It would be great if they could set up a way to automatically publish tarballs and xo bundles from Gitorious to downloads without a shell account).
    • Trac (component creation)
  • Ask IT about activity repository mirroring. A read-only Git repository on SL which automatically pulls from a remote repository.
  • Flesh out structure for ActivityTeam wiki.Wade 01:34, 14 January 2009 (UTC)
  • Create ActivityTeam wiki structure page indicating where content is supposed to go.
  • Bug IT to add helpful "git-clone" hints like on: http://dev.laptop.org/git?p=activities/help;a=summary and/or instructions for developing within sugar like: (snipped) I moved this snippet to the Get Involved page, and Gitorious does offer push / clone urls. Wade 01:34, 14 January 2009 (UTC)

Development Tasks

  • Help SoaS and other distro packagers to get as many activities as possible working on plain Sugar (outside the XO software environment).
    See ActivityTeam/ActivityStatus for a list of projects that need to ported and/or tested.
  • Clean up activities. Bring .POT files up to date, check MANIFEST is correct, publish latest version to downloads.sugarlabs.org.
    See ActivityTeam/ActivityStatus for a list of projects that need to cleaned up.
  • Build a list of "Rescue" activities: Ones which have not been worked on in a while but are close to being usable.
  • Build a list of "Help Wanted" activities: Great ideas or existing projects which need to be sugarized.
  • Generate spec for Web, SWF activities and deliver to DevelopmentTeam.

Activity Feature Requests

This section is for feature requests for specific activities. As requests, there can be no guarantee as to the order in which we will process them, but we will do our best.

If you are a new activity developer, there are many small tasks here which would be a great way to get introduced to the project.

Turtle Art

  • Move the show/hide blocks, erase, and stop buttons to the toolbar
  • Add run and step buttons to the same toolbar
  • Reconfigure audio initialization so that it only happens when TA starts up or gets sent to the background
  • Don't let bricks get lost off the screen
  • Add a special stack "hat" for "main" (tied to the run button above)
  • Merge with TA with sensors.