Difference between revisions of "Features/SoaS customization"

Revision as of 13:38, 24 November 2009

Summary

SOAS Deployement Settings Definition

Owner

Name: Carlo Falciola
Email: <cfalciola dot yahoo dot it>

Current status

Targeted release: (0.88)
Last updated: (2009 Nov 24)
Percentage of completion: 1%

Detailed Description

In order to support deployements activities the standard SOAS image should allow a limited degree of personalization for basic settings.

This page would be the start of a documentation effort aimed to document those basic interfaces:

Benefit to Sugar

to ease the personalization efforts from field organizations
to avoid regression issues related to personalization done in the wrong places
to ease peacefully coexistance between personalization needs and bugfixing/support activities

Scope

Actually will be mostly a documentation effort - no impact on code in this phase.

How To Test

Features/SoaS customization/Testing

User Experience

Users will have the opportunity to work in their native language from the initial experience of Sugar rather than having to initially wade through English-language menus.

Dependencies

None

Contingency Plan

If we don't complete this feature, it can be left out. Nothing else depends upon it.

Documentation

This is common practice now on several GNU/Linux distros, e.g., Ubuntu 9.10

Release Notes

Comments and Discussion

See discussion tab for this feature

@@ Line 17: / Line 17: @@
 == Detailed Description ==
- In order to support deployements activities the standard SOAS image should allow a limited degree of personalization for basic settings.
+In order to support deployements activities the standard SOAS image should allow a limited degree of personalization for basic settings.
+This page would be the start of a documentation effort aimed to document those basic interfaces:
 == Benefit to Sugar ==
-Our users speak many languages and with Sugar on a Stick, deploy on many different--unpredictable?--keyboards. This feature would allow them to set their language on initial boot rather than having to wait until they have completed the intro dialog. (Note that on an XO, the manufacturing data is used to set these fields. This feature would be used to override those settings.)
+* to ease the personalization efforts from field organizations
+* to avoid regression issues related to personalization done in the wrong places
+* to ease peacefully coexistance between personalization needs and bugfixing/support activities
 == Scope ==