Documentation Team
API documentation
- sugar-base and sugar-toolkit has API documentation in the code. What tool do we use to generate html? Where do we generate it and where we make it available? Do we need to build them to generate docs?
- Probably we should document the datastore dbus API. I'm not sure what's the best way to generate documentation for it. It's so small that a wiki page might be the simpler solution for now.
- Collaboration API. I have no idea, morgs we need your help here.
-
- Morgs, my impression after a 3 minutes look over the available documentation is that there is little written with activity authors in mind, and that it's dispersed in several pages and mixed with implementation docs. Is that impression correct? I would like to have a couple of things: 1 complete documentation of the API which interest activity authors (with good links to dbus documentation since it's used so heavily) 2 A complete tutorial as part of the "manual". One of the Tubes pages looks like a pretty good start in this respect. Does it make sense to you? Can we make it happen? -- Marcopg
- Low level API (non-python activities). We should just move bert document on this wiki.
Manual
- Setup a development environment. This is wiki oriented so we should probably not even mention jhbuild (we should definately not do so until we have a bunch of autobuild slaves running).
- "Write your activity" tutorial. It should include all the important bits: graphic controls, datastore, collaboration
- Probably good to have a pygame tutorial, it's probably the best thing we have at the moment to do free form graphics stuff.
- Etoys based activity tutorial?
Community
- Roadmap
- Release process
- Bug triage
- Publish you activity. Maybe we need bits of infrastructure to make this easiers, something like firefox addons. But even just a wiki page could be start if we maintain it well.