Difference between revisions of "Sugar on a Stick/TODO"

Revision as of 20:57, 3 August 2009

Project Home · Join · Contacts · Resources · FAQ · Roadmap · To Do · Meetings

Sugar on a Stick Improve Deployability

The good news is Sugar on a Stick is being successfully used in Schools around the world now! Based on these experiences this is a list of some of the known challenges that people may face Piloting Sugar on a Stick right now. Sept is start of school in the US so we expect to see an increase in teachers trying Sugar. We want to be ready with suggestions and work arounds as people face these challenges.

Make it easier for a teacher or school to customize a spin and then copy it for a hundred kids

Tickets on this topic:

Red Hat - https://bugzilla.redhat.com/show_bug.cgi?id=448030 - RFE: create a bootable Live USB stick from the running livecd SugarLabs Ticket 74 - http://dev.sugarlabs.org/ticket/74

Use Case A teacher should be able to create a USB stick, add activities, add some content, change the language, change the jabber server etc. Then create new sticks that reflect these changes but do not copy the name, color or collaboration key.

It would be great if the teacher could use an inexpensive USB hub to burn more then one stick at a time.

Stick Failure

Discussions of Stick Failure and alternative file structures is now at Stick Layout

Backup and recovery

Ham and Dave from Solution Grove are making progress on this. You can track progress on ticket 916 [[1]]

What is a reasonable expectation for the role of the XS in Sugar on a Stick deployments in the next 6 months?

Collaboration is unreliable and thus frustrating

Its working fairly well in the wired network at the GPA lab, but no other use case seem to work reliably. We need to expand the Poets Guide to Collaboration to give people hints on how to set up a scenario that will work for them.

Using a CD helper takes a lot of prep time before and after class

A floppy helper would reduce it. A VM solution might also reduce it.

Tickets

* Ticket 598   Boot Helper Virtual Machine [[2]]
* Ticket 907  change the format we use for the USB stick [[3]]
* Ticket 597 Floppy Boot Helper [[4]]

See also Sugar on a Stick/Goals.

Gardner Pilot Academy#Critical Path Technical Issues

This is an the general todo list for SoaS. If you've any ideas or requests, please add them here.

Task Name	Priority	Status/Notes
solicit USB key donations from companies	1	info needed
allow direct recreation of USB keys (cloning)	2	needs testing [5]
add additional activities, if requested	3	get them on a.sl.o
work on a keyboard layout control panel	3	work in progress [6]
be able to backup and restore from a School Server	3	to be worked out
support printers, scanners, cameras	3	to be worked out
activity for cloning USB Sticks and .iso files (cloning)	3	to be worked out [7]

Here's a list with completed tasks; feel free to move them from the table above.

Task Name	Status/Notes
get SoaS included in liveusb-creator	done
create a virtual appliance (builds)	done [8] [9]
release a helper CD for boot from USB	done [10]
add sample content	done - add more if needed
fix blockers for release	most important point, check rawhide, as it progresses towards beta
update remaining RPMs	good progress done so far
check localization support	done
get artwork and branding together	done
change default Browse location	done

@@ Line 28: / Line 28: @@
 ===What is a reasonable expectation for the role of the XS in Sugar on a Stick deployments in the next 6 months?===
 ===Collaboration is unreliable and thus frustrating===
-Its working fairly well in the wired network at the GPA lab, but no other use case seem to work reliably.
+Its working fairly well in the wired network at the GPA lab, but no other use case seem to work reliably.  We need to expand the Poets Guide to [[Collaboration]] to give people hints on how to set up a scenario that will work for them.
 ===Using a CD helper takes a lot of prep time before and after class===