Talk:Creating an activity

metadata

updating metadata discussion.

• make versioning clear to the user
  • parents : identify derived codebases, the branch point and the version at the branch

• make dependencies clear and explicit
  • define sugar/platform versions; can't keep api compat forever

    note that something /could/ work on future platform versions, not guaranteed.

    platform name and #. "sugar 0", since we don't have explicit versioning yet

    nnb: we don't have a platform name : OLPC OS? Sugar/Linux? Sugar?

tv : 'the sweet machine' coming with sugar.

terminology

tools/activities

journal : journal of events and actions requested by the user via sugar

yellow : see journal

system services, in-process

horizon : see http://teach.laptop.org/~mstone/horizon.html

hulahop :

datastore :

widgets :

xpcom : (including bookmarkservice, &c)

system services, out-of-process

spellcheck :

tts :

rainbow : see Taste the Rainbow (not yet in-p)

orison : prayer

shell

network services (out-of-machine)/powers

presence

jabber

mailserver

webserver (discovery, up/download)

bboards (distributed)

 ?? (lighthouse?) : filesharing, publishing

systems

sugar  : see also 'sugar/linux' and 'olpc os'

 ??  : openfirmware bootloader

plans: bitfrost; see also memebrand, sugar frame/view design

setup.py file status?

Is the setup.py file deprecated? in use? I can't get it to work for my activity right now... (we should have a canonical set of scripts that is in one location, pullable via git, for easier maintenance, rather than having this inline on the wiki. Mchua 00:55, 7 June 2008 (EDT)