Difference between revisions of "User:Carlo/sandbox"

From Sugar Labs
Jump to navigation Jump to search
Line 10: Line 10:
 
Whatever approach would be taken in order to land those initial dsettings in the sticks/images, the very first step is to try ti define with increasing precision what  all those settings are, where a deployer or developer could find them and how to operate changes without creating regression errors in the procedure.     
 
Whatever approach would be taken in order to land those initial dsettings in the sticks/images, the very first step is to try ti define with increasing precision what  all those settings are, where a deployer or developer could find them and how to operate changes without creating regression errors in the procedure.     
 
In order to support deployements activities the standard SOAS image shuld allow a limited degree of personalization for basic settings,.
 
In order to support deployements activities the standard SOAS image shuld allow a limited degree of personalization for basic settings,.
A basic list of setting to be descripted could be (from http://wiki.sugarlabs.org/index.php?title=Request_New_Feature )
+
A basic list of setting to be descripted could be taken from http://wiki.sugarlabs.org/index.php?title=Request_New_Feature :
 
<ol>  
 
<ol>  
 
*Date, Time & Timezone
 
*Date, Time & Timezone
Line 16: Line 16:
 
*User Accounts
 
*User Accounts
 
*WiFi settings
 
*WiFi settings
*Jabber server(s) - ability to input multiple servers for different user groups (schools, cities, countries, etc.).
+
*Jabber server(s).
 
*Add/Remove Programs
 
*Add/Remove Programs
 
*System Updates
 
*System Updates
 
*Desktop GUI settings
 
*Desktop GUI settings
 
*Name SD card and USB media drives, etc.
 
*Name SD card and USB media drives, etc.
*Running Linux Applications Under Sugar - A script has been written to Sugar Coat Linux apps to make them run under Sugar desktop (i.e. making them to run in the Sugar interface, without the collaboration and other Sugar integration programmed into them). Can this be made more user-friendly and incorporated into a Sugar Control Panel GUI, to make adding applications easier?
+
.....
 
*What else?
 
*What else?
  
Line 28: Line 28:
 
</ol>
 
</ol>
  
=== __________ ===
+
=== _____________________________________________________________________________________________________________________  ===
 +
 
 +
=== SOAS Deployement Settings Table ===
 +
 
 +
* A draft table could be the following:
 +
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
 +
|-style="background:#787878; color: white;"
 +
! Description!! What || Where !! How !! Complexity
 +
|-
 +
|Language ||LANGUAGE and LANG environment variables || conf file, login/boot scripts || ....  || easy (must be!)
 +
 +
|-
 +
| Timezone ||Environment that define timezone || login/boot scripts || .... ||  easy (must be!)
 +
 
 +
 
 +
|-
 +
| Jabber Server(s) || addres of jabber server for the school/class || conf file? || ......
 +
 
 +
|-
 +
| WiFi settings
 +
|| in case of proxy, passwords needed|| conf file? || .....
 +
 
 +
|-
 +
| Activity selection  or preferred list reworked (added to default set)
 +
|| Journal
 +
|| tbd
 +
|-
 +
| User account || parameters || conf file ? ||schoolclass  info to be added (?)
 +
|-
 +
|}
 +
 
 +
 
 +
=== _____________________________________________________________________________________________________________________  ===
 +
=== _____________________________________________________________________________________________________________________ ===

Revision as of 06:02, 23 November 2009

What I would like to write about...

  • A Matrix of Distributions features (what you get what you don't get)
  • Activities & Sugar (Sweetness...?)

....

SOAS Deployement Settings Definition

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). Whatever approach would be taken in order to land those initial dsettings in the sticks/images, the very first step is to try ti define with increasing precision what all those settings are, where a deployer or developer could find them and how to operate changes without creating regression errors in the procedure. In order to support deployements activities the standard SOAS image shuld allow a limited degree of personalization for basic settings,. A basic list of setting to be descripted could be taken from http://wiki.sugarlabs.org/index.php?title=Request_New_Feature :

    • 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?
    Andrea 16:41, 21 May 2009 (UTC)

_____________________________________________________________________________________________________________________

SOAS Deployement Settings Table

  • A draft table could be the following:
Description What Where How Complexity
Language LANGUAGE and LANG environment variables conf file, login/boot scripts .... easy (must be!)
Timezone Environment that define timezone login/boot scripts .... easy (must be!)


Jabber Server(s) addres of jabber server for the school/class conf file? ......
WiFi settings in case of proxy, passwords needed conf file? .....
Activity selection or preferred list reworked (added to default set) Journal tbd
User account parameters conf file ? schoolclass info to be added (?)


_____________________________________________________________________________________________________________________

_____________________________________________________________________________________________________________________