Activity Team/TODO

< Activity Team
Revision as of 14:05, 12 January 2009 by Wade (talk | contribs)

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 Martni is currently leading the port of this PyGTK program to Sugar, it's current at an alpha stage I think. Mind mapping software has been specifically requested by teachers at deployments. Labyrinh needs help improving and extending the user interface, so PyGTK skills would be important. Or, collaboration would be a great addition!

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.

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.
  • Bug IT to get us admin accounts for SL services.
    • Downloads
    • Trac (component creation etc)
  • 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.
    • Where does the Activities list from the SL home page go?
    • How should development information be structured?
    • In the (temporary) absence of activities.sugarlabs.org, should we create per-activity Wiki pages? Should we anyway?

Development Tasks

  • Move projects owned by ATeam members over to git.sugarlabs.org and downloads.sugarlabs.org.
  • Help SoaS and distro packagers to get as many activities as possible working on plain Sugar (outside the XO software environment).
  • 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.