Documentation: Difference between revisions

From OLPC
Jump to navigation Jump to search
mNo edit summary
Line 15: Line 15:
== Needs ==
== Needs ==
* Comments in code -- clean up, write for children, translate
* Comments in code -- clean up, write for children, translate
* Notes about development -- how to create a 'hello world' activity or bundle. THis is intented to be in [[Activity_Template]]
* Notes about development -- how to create a 'hello world' activity or bundle. This is intented to be in [[Activity_Template]]
* Community introduction -- getting to know and collab with the social community of developers and supporting groups
* Community introduction -- getting to know and collab with the social community of developers and supporting groups
* Packaging/downloading guide -- how to package, where to publish, how to find and download
* Packaging/downloading guide -- how to package, where to publish, how to find and download

Revision as of 20:10, 13 October 2007

OLPC hardware and software is designed to be discoverable so that a user can figure things out by experimentation. We are preparing teachers by extensively lecturing and writing about how the devices might be leveraged. The OLPC laptops will come with e-books documenting how to use them, and technical details needed by application developers are available on the web including this wiki.

Examples: see the user interface guidelines and a draft developers handbook.

There are many audiences for the laptops and their software and content; some of them may need to create their own instructional material, or their own versions of existing material. This wiki is open for development of such material. If you have created your own documentation -- for instance, text, screenshots, video or animation for the hardware or specific software that is being turned into an activity -- note it here.

TODO

We need to improve speed/accuracy of

() noting the need for pascals doc
() making sure it gets created
(*) integrating it with other such docs in a organizing framework
() having an organizing framework 
() keeping the docs up to date / tagged with freshness indicators

Needs

  • Comments in code -- clean up, write for children, translate
  • Notes about development -- how to create a 'hello world' activity or bundle. This is intented to be in Activity_Template
  • Community introduction -- getting to know and collab with the social community of developers and supporting groups
  • Packaging/downloading guide -- how to package, where to publish, how to find and download
  • Testing guide -- how to write test plans, who tests, how to help test, how to read the results of automated / human tests
  • Build/release guide -- how builds are made how often, where they end up; stable v unstable; how an activity gets into a buld

Specific examples

Wikitexts

Images/Pictures

  • (from christina xu... to find on Flickr)

Tutorials

Videos