Sugar on a Stick/Resources

Project Planning

 * See ../TODO for some project tasks.
 * See ../Goals for some specific deployment/distribution obstacles.
 * See our Feature blueprints tracking system for feature development.

Use Cases
This is a list of ways we're working to support SoaS installation and their status. TODO: replace with a flow chart.

Sugar:
 * 1) On a Stick:
 * 2) Mobile booting using USB boot support in BIOS - implemented
 * 3) Mobile booting using ISO helper CDs - implemented
 * 4) Mobile virtualization or emulation - unimplemented
 * 5) Combination of booting and emulation - unimplemented
 * 6) * VMware (VMware Player and Appliance on one 8-GB bootable stick, or a 4-GB boot stick and a 4-GB stick with the Appliance) works but is complicated. (Waiting for Fedora 11 to allow VMware Player installation; this workaround uses Ubuntu 9.04 boot stick with VMPlayer.)
 * 7) On a fixed hard disk:
 * 8) Local booting with storage - implemented via various distros.
 * 9) Local booting with external storage - unimplemented, students would insert their SoaS stick and the fixed system would operate off their transportable data, and optionally, update their stick's software to the latest image.

Installation Methods

 * 1) Windows/Mac/Linux
 * 2) Live USB creator script - implemented
 * 3) Windows
 * 4) SoaS-emu - installer for a SoaS appliance on the local machine - work in progress
 * 5) MokaFive portable player installer - investigating
 * 6) Virtualization environments
 * 7) Boot a SoaS image on a USB device in VirtualBox.  See this discussion thread.
 * 8) Live CD which boots a Mac OS X version of VirtualBox and uses a SoaS USB device as the guest OS.  See this discussion thread.
 * 9) Live CD which boots to live user and autostarts VMware Player (installed in CD SquashFS). Then students can sequentially insert their USB Stick and work on same PC - "idea" [satellit 07/05/2009]
 * 10) Other variations
 * 11) Live CD which creates USB sticks - works in SoaS Strawberry
 * 12) Insert the target USB storage device into your computer,
 * 13) Boot from a CD-ROM burnt with the soas-strawberry.iso image,
 * 14) Launch Terminal,
 * 15) Switch to the root user,
 * 16) Unmount the USB device,
 * 17) Install the live image to the USB device by executing the following, single command with arguments:
 * Note: If you have more than 1 hard disc or USB device, you should verify the name of the USB storage device by reviewing the output of the  command before step 5 above.
 * 1) zyx-liveinstaller (in Terminal) in SoaS v2 Blueberry can be used to make USB installations from the running live CD. - "works for v2 Bluberry, not yet working in Nightly Composes (v3, F13)"
 * 2) dd install to USB device with F12 dual mode .iso "works, but offers no persistence"
 * 3) liveinst command from terminal, install to USB - "works for v2 Bluberry, not yet working in Nightly Composes (v3, F13)"
 * 4) Prebuilt USB .img/vmx/vdi files to download  ext3 real install USB .img file

Upgrade Paths

 * 1) With a Journal full of learning, how does one upgrade to a new version of Sugar?
 * 2) Will Journals restored from a School Server work?
 * 3) Is a persistent home overlay usable?
 * 4) Is Home.img exchangeable from one device to another?

More Information

 * Sugar on a Stick - The Fedora Project home for the project.
 * SoaS Gitorious home - Tools to build Sugar on a Stick images.
 * SoaS Desktop Manager Sugar_on_a_Stick/sdm
 * Other portable Sugar distributions that share the Sugar on a Stick goals.

Home View Design
See this page for ideas about the Home view design.

Initial Home View Activities
Discussion of which Activities should be visible on initial display of the Home view is appropriate here. See this sugar-devel thread for the background.

Marketing resources

 * SoaS Blueberry Banner
 * SoaS Blueberry Instructions
 * SoaS Blueberry Notes