8,288
edits
Changes
Features/SoaS customization (view source)
Revision as of 12:20, 31 January 2014
, 12:20, 31 January 2014spelling and sort in category page
<noinclude>{{TOCright}}
<noinclude>[[Category:Feature Page Incomplete]]
[[Category:Feature Page Incomplete]]
[[Category:Feature|SoaS customization]]
[[Category:Feature|Feature intro language keyboard options]]
</noinclude>
</noinclude>
== Summary ==
== Summary ==
SOAS Deployement Customization
SOAS Deployment Customization
== Owner ==
== Owner ==
== Detailed Description ==
== Detailed Description ==
In order to support deployements activities the standard SOAS image should allow a limited degree of customization for basic/advanced settings.
In order to support deployments activities the standard SOAS image should allow a limited degree of customization for basic/advanced settings.
This page would be the start of a documentation effort aimed to document those basic interfaces:
This page would be the start of a documentation effort aimed to document those basic interfaces:
* to ease the personalization efforts from field organizations
* to ease the personalization efforts from field organizations
* to avoid regression issues related to personalization done in the wrong places
* to avoid regression issues related to personalization done in the wrong places
* to ease peacefully coexistance between personalization needs and bugfixing/support activities
* to ease peacefully coexistence between personalization needs and bug fixing/support activities
== Scope ==
== Scope ==
== User Experience ==
== User Experience ==
In case of a deploy in a school we could not expect children or teacher to spend a large initial amount of time to set up basic paramenters for SOAS usage (es. LANGUAGE, Timezone, Keyboard, servers, etc).
In case of a deploy in a school we could not expect children or teacher to spend a large initial amount of time to set up basic parameters for SOAS usage (es. LANGUAGE, Timezone, Keyboard, servers, etc).
Whatever approach would be taken in order to land those initial settings in the actual sticks/images, the very first step is to try to define with increasing detail:
Whatever approach would be taken in order to land those initial settings in the actual sticks/images, the very first step is to try to define with increasing detail:
== Documentation ==
== Documentation ==
SOAS Deployement Settings Table (Draft)
SOAS Deployment Settings Table (Draft)
|-
|-
| Jabber Server(s) || addres of jabber server for the school/class || conf file? || ...... || ...
| Jabber Server(s) || address of jabber server for the school/class || conf file? || ...... || ...
|-
|-
Note: The "Complexity" column could be the base for differentiate the effort/scope of personalization effort:
Note: The "Complexity" column could be the base for differentiate the effort/scope of personalization effort:
* some of them could be defined as "standard" and potentially we could have half baked tools to smooth efforts (the idea is that's far easyer to write a well done & safe script to be used by deployer on the field other than increase the Sugar UI with rarely used features)
* some of them could be defined as "standard" and potentially we could have half baked tools to smooth efforts (the idea is that's far easier to write a well done & safe script to be used by deployer on the field other than increase the Sugar UI with rarely used features)
* some of them could be defined as "hard" and then documented only then left to field/deployers will...
* some of them could be defined as "hard" and then documented only then left to field/deployers will...
== References ==
== References ==
A basic list of setting to be descripted could be taken from http://wiki.sugarlabs.org/index.php?title=Request_New_Feature
A basic list of setting to be described could be taken from http://wiki.sugarlabs.org/index.php?title=Request_New_Feature
(by [[User:andrea.mangiatordi|Andrea]] 16:41, 21 May 2009 (UTC) ):
(by [[User:andrea.mangiatordi|Andrea]] 16:41, 21 May 2009 (UTC) ):