Difference between revisions of "Features/SoaS customization"
< Features
Jump to navigation
Jump to search
m (FGrose moved page Features/Feature SoaS customization to Features/SoaS customization: simplify name) |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | <noinclude> | + | <noinclude>[[Category:Feature Page Incomplete]] |
| − | [[Category:Feature Page Incomplete]] | + | [[Category:Feature|SoaS customization]] |
| − | [[Category:Feature| | ||
</noinclude> | </noinclude> | ||
== Summary == | == Summary == | ||
| − | SOAS | + | SOAS Deployment Customization |
== Owner == | == Owner == | ||
| Line 17: | Line 16: | ||
== Detailed Description == | == Detailed Description == | ||
| − | In order to support | + | 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: | ||
| Line 25: | Line 24: | ||
* 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 | + | * to ease peacefully coexistence between personalization needs and bug fixing/support activities |
== Scope == | == Scope == | ||
| Line 34: | Line 33: | ||
== 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 | + | 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: | ||
| Line 42: | Line 41: | ||
== Dependencies == | == Dependencies == | ||
| − | None on code | + | * None on code |
| − | + | ||
| + | * Once consensus being reached on the customization documentation, developers that changes Sugar in areas that impact this documentation set should fell obliged to update it consistently and notify downstream. | ||
== Contingency Plan == | == Contingency Plan == | ||
| Line 50: | Line 50: | ||
== Documentation == | == Documentation == | ||
| − | SOAS | + | SOAS Deployment Settings Table (Draft) |
| Line 64: | Line 64: | ||
|- | |- | ||
| − | | Jabber Server(s) || | + | | Jabber Server(s) || address of jabber server for the school/class || conf file? || ...... || ... |
|- | |- | ||
| Line 72: | Line 72: | ||
|- | |- | ||
| Added Activity (added to the default set) | | Added Activity (added to the default set) | ||
| − | || | + | || Activity Bundle |
| − | || | + | || Filesystem or Journal?|| ... || ... || see also mail: (http://lists.sugarlabs.org/archive/sugar-devel/2009-November/020967.html ) |
|- | |- | ||
| − | | Preferred Activities list reworked/reordered || | + | | Preferred Activities list reworked/reordered ||text file, proprietary format || /home/liveuser/.sugar/default/favorite_activities (in Soas) |
| − | || | + | || ... || ... || see also mail: (http://lists.sugarlabs.org/archive/sugar-devel/2009-November/020967.html ) |
|- | |- | ||
| User account || parameters || conf file ? ||schoolclass info to be added (?) || ... || ... | | User account || parameters || conf file ? ||schoolclass info to be added (?) || ... || ... | ||
| Line 82: | Line 82: | ||
| Additional Drivers || Linux drivers to support specific HW || Standard Linux Drivers locations || Link to an Howto Page || (Could be hard) || | | Additional Drivers || Linux drivers to support specific HW || Standard Linux Drivers locations || Link to an Howto Page || (Could be hard) || | ||
|- | |- | ||
| − | | Additional Multimedia || to enhance localization for specific packages (es. Gcompris Voices, openstreetmap | + | | Additional Multimedia || to enhance localization for specific packages (es. Gcompris Voices, openstreetmap dataset) || /Activities... || ... || ... || |
|- | |- | ||
| Additional Contents (eBooks, images, ecc.) || files || to land in Journal or in compressed r/o partition || ... || ... || | | Additional Contents (eBooks, images, ecc.) || files || to land in Journal or in compressed r/o partition || ... || ... || | ||
|- | |- | ||
| − | | Additional static HTML (local homepage, etc.) || files || to land in ... || ... || ... || | + | | Additional static HTML (local homepage, etc.) || files || to land in ... || ... || ... || see also mail: (http://lists.sugarlabs.org/archive/sugar-devel/2009-November/020967.html ) |
|- | |- | ||
|} | |} | ||
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 | + | * 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... | ||
| Line 103: | Line 103: | ||
== References == | == References == | ||
| − | A basic list of setting to be | + | 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) ): | ||
Latest revision as of 12:21, 31 January 2014
Summary
SOAS Deployment Customization
Owner
- Name: Carlo Falciola
- Email: <cfalciola dot yahoo dot it>
Current status
- Targeted release: (0.88)
- Last updated: (2009 Nov 24)
- Percentage of completion: 5%
Detailed Description
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:
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 coexistence between personalization needs and bug fixing/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
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:
- what all those settings are
- where a deployer or developer could find them
- how to operate changes to those setting without creating regression errors in the procedure
Dependencies
- None on code
- Once consensus being reached on the customization documentation, developers that changes Sugar in areas that impact this documentation set should fell obliged to update it consistently and notify downstream.
Contingency Plan
If we don't complete this feature, it can be left out. Nothing else depends upon it.
Documentation
SOAS Deployment Settings Table (Draft)
| Description | What | Where | How | Complexity | Notes/References |
|---|---|---|---|---|---|
| Language | LANGUAGE and LANG environment variables | conf file, login/boot scripts | .... | .... | |
| Timezone | Environment that define timezone | login/boot scripts | .... | ..... |
|
| Jabber Server(s) | address of jabber server for the school/class | conf file? | ...... | ... | |
| WiFi settings (auto connect) | in case of proxy, passwords needed | conf file? | ..... | ... | see also mail: (http://lists.sugarlabs.org/archive/sugar-devel/2009-November/020967.html ) |
| Added Activity (added to the default set) | Activity Bundle | Filesystem or Journal? | ... | ... | see also mail: (http://lists.sugarlabs.org/archive/sugar-devel/2009-November/020967.html ) |
| Preferred Activities list reworked/reordered | text file, proprietary format | /home/liveuser/.sugar/default/favorite_activities (in Soas) | ... | ... | see also mail: (http://lists.sugarlabs.org/archive/sugar-devel/2009-November/020967.html ) |
| User account | parameters | conf file ? | schoolclass info to be added (?) | ... | ... |
| Additional Drivers | Linux drivers to support specific HW | Standard Linux Drivers locations | Link to an Howto Page | (Could be hard) | |
| Additional Multimedia | to enhance localization for specific packages (es. Gcompris Voices, openstreetmap dataset) | /Activities... | ... | ... | |
| Additional Contents (eBooks, images, ecc.) | files | to land in Journal or in compressed r/o partition | ... | ... | |
| Additional static HTML (local homepage, etc.) | files | to land in ... | ... | ... | see also mail: (http://lists.sugarlabs.org/archive/sugar-devel/2009-November/020967.html ) |
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 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...
Release Notes
...
Comments and Discussion
References
A basic list of setting to be described could be taken from http://wiki.sugarlabs.org/index.php?title=Request_New_Feature (by Andrea 16:41, 21 May 2009 (UTC) ):
- Date, Time & Timezone
- Language
- User Accounts
- WiFi settings
- Jabber server(s).
- Add/Remove Programs
- System Updates
- Desktop GUI settings
- Name SD card and USB media drives, etc.
- What else?