User:Carlo/sandbox - Revision history

Carlo: SOAS Deployement Settings Table

2009-11-23T15:49:38Z

SOAS Deployement Settings Table

← Older revision		Revision as of 11:49, 23 November 2009
Line 66:		Line 66:
	\|-		\|-
	\| User account \|\| parameters \|\| conf file ? \|\|schoolclass info to be added (?)		\| 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)
	\|-		\|-
	\|}		\|}

Carlo at 11:16, 23 November 2009

2009-11-23T11:16:41Z

← Older revision		Revision as of 07:16, 23 November 2009
Line 4:		Line 4:
	* A Matrix of Distributions features (what you get what you don't get)		* A Matrix of Distributions features (what you get what you don't get)
	* Activities & Sugar (Sweetness...?)		* Activities & Sugar (Sweetness...?)
			* Setting and personalization of SOAS

	....		....
	= SOAS Deployement Settings Definition =		= 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).		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.		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 :		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:
			* to ease the personalization efforts from field organizations
			* to avoid regression issues related to personalization done in the wrong places

			A basic list of setting to be descripted 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) ):

	<ol>		<ol>
	*Date, Time & Timezone		*Date, Time & Timezone
Line 24:		Line 33:
	*What else?		*What else?

	~~[[User:andrea.mangiatordi\|Andrea]] 16:41, 21 May 2009 (UTC)~~

	</ol>		</ol>
Line 61:		Line 70:


	~~=== _____________________________________________________________________________________________________________________ ===~~		= =
	~~=== _____________________________________________________________________________________________________________________ =~~==

Carlo at 11:04, 23 November 2009

2009-11-23T11:04:41Z

← Older revision		Revision as of 07:04, 23 November 2009
Line 6:		Line 6:

	....		....
	=== SOAS Deployement Settings Definition ===		= 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).		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.		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.
Line 28:		Line 28:
	</ol>		</ol>

	~~=== _____________________________________________________________________________________________________________________ =~~==		= =

	=== SOAS Deployement Settings Table ===		== SOAS Deployement Settings Table ==

			* Draft table :

	* A draft table could be the following:
	{\| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"		{\| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
	\|-style="background:#787878; color: white;"		\|-style="background:#787878; color: white;"

Carlo at 11:02, 23 November 2009

2009-11-23T11:02:13Z

@@ 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.
 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>
 *Date, Time & Timezone
@@ Line 16: / Line 16: @@
 *User Accounts
 *WiFi settings
-*Jabber server(s) - ability to input multiple servers for different user groups (schools, cities, countries, etc.).
+*Jabber server(s).
 *Add/Remove Programs
 *System Updates
 *Desktop GUI settings
 *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?
@@ Line 28: / Line 28: @@
 </ol>
-=== __________  ===
+=== _____________________________________________________________________________________________________________________  ===

Carlo at 10:39, 23 November 2009

2009-11-23T10:39:51Z

@@ Line 6: / Line 6: @@
 ....
-===  SOAS Deployement Settings ===
+===  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,
+In order to support deployements activities the standard SOAS image shuld allow a limited degree of personalization for basic settings,.

Carlo at 10:31, 23 November 2009

2009-11-23T10:31:34Z

← Older revision		Revision as of 06:31, 23 November 2009
Line 6:		Line 6:

	....		....
			=== SOAS Deployement Settings ===
			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,

Carlo: New page: === What I would like to write about... === * A Matrix of Distributions features (what you get what you don't get) * Activities & Sugar (Sweetness...?) ....

2008-07-03T09:44:08Z

New page: === What I would like to write about... === * A Matrix of Distributions features (what you get what you don't get) * Activities & Sugar (Sweetness...?) ....

New page

=== What I would like to write about... ===

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

....