Sugar Labs - User contributions [en]

Platform Team/Server Kit/sugar-client

2013-04-23T18:51:34Z

M anish:

== Summary ==

A program to run on Sugar clients side to interact with [[Sugar Server Kit]] based school server. It implements the [[Sugar_Server_Kit/Client_API|Client API]] for usage, e.g. in Sugar Shell, and the {{Code|sugar-client}} utility to get access to the same API from the console.

== Functionality ==

The high level functionality is described by DBus [[Sugar_Server_Kit/Client_API|API]] sugar-client provides. These DBus services will be accessible right after installing {{Code|sugar-client}} package, e.g., to reuse them in Sugar Shell code. To call the same functionality from the command line, use {{Code|sugar-client}} utility.

=== Registration on a school server ===

That's the first operation that should be processed to let the rest of sugar-client functionality working properly. The key configuration option here, is {{Code|api-url}} that points to [[Sugar_Server_Kit/sugar-server#Services|sugar-server's API]]. If {{Code|api-url}} was not explicitly specified, the default one, {{Code|http://schoolserver:8000}}, will be used. If {{Code|api-url}} was explicitly specified, it will be [[#Configuration|kept]] for later usage.

The result of registration will be:

* Setting the {{Code|/desktop/sugar/collaboration/jabber_server}} GConf key with Jabber server url to support Sugar collaboration;
* School server reply will be formed as a regular {{Code|sugar-client.conf}} configuration file and placed to user's profile directory. This configuration will be [[#Configuration|reused]] for all other sugar-client functionality.

If {{Code|auto-register}} configuration option is set, sugar-client will try to make auto-registration on a server on Sugar [[#Background_operations|startup]]. Auto-registration will happen if client is not registered at all or registration is outdated (school server asked clients to process re-registration).

To process registration, either call [[Sugar_Server_Kit/Client_API#org.sugarlabs.client.Server|DBus API]] or use {{Code|sugar-client}} utility:

sugar-client register [''<api-url>'']

=== Auto Journal restore ===

The affected usecase:

* a XO processed several [[#Background operations|auto]] backups (the regular practice in the field),
* and was reflashed,
* XO was '''not''' restored manually before the first auto backup,
* the first auto backup will cleanup backuped Journal on the server (Journal after reflashing is empty),
* any later restore using UI will restore empty Journal (though, it is possible to restore Journal for particular date using CLI tools).

Since disabling auto backups will be considered as a regression, sugar-client needs to provide a way to
auto restore Journal after reflashing.

The implementation will be:

* {{Code|auto-register}} option needs to be more than {{Code|0}},
* {{Code|backup-timeout}} needs to be more than {{Code|0}},
* {{Code|auto-restore}} needs to be {{Code|True}},
* Journal should be empty,
* right after registering newly reflashed XO, sugar-client will start restoring the Journal.

=== Usage statistics ===

Summary:

* Implementation is based on [[Sugar_Server_Kit/sugar-stats|sugar-stats]] library.
* Client behaviour is entirely controlled by [[Sugar_Server_Kit/sugar-stats#Stats_server|stats server]].

To activate stats client activity, [[#Background operations|background operations]] need to be activated. The procedures are:

* sugar-client requests server for stats parameters in {{Code|stats-timeout}} period, in particular:
** should stats gathering process start or stop,
** client side storage parameters;
* if server needs stats, client start gathering process;
* during the server interaction, client sends already collected stats.

To start stats activity, client side should have the following [[#Configuration|configuration]]:

* {{Code|stats-url}}, HTTP(S) url to the stats server,
* {{Code|stats-timeout}}, how frequent (in seconds) client should connect to stats server to upload new information and correct current behaviour.

The stats gathering process might be initiated manually by the command:

sugar-client -d monitor [OPTIONS]

It is important to use secure connection with server, specify server's certificate via {{Code|stats-ca-certs}} parameter.

==== Stats configuration ====

After enabling stats gathering (after the first successful server connection), all stats related configuration will be stored in [[#Configuration|sugar-client.conf]] configuration file in {{Code|[stats]}} section. Enable this configuration manually if you need to enable stats gathering before the first connection to the server.

[stats]
rras = ["RRA:AVERAGE:0.5:1:4320", "RRA:AVERAGE:0.5:5:2016"]
step = 60
enabled = true

== Background operations ==

Sugar-client might process background operations. To make it possible, add

sugar-client session

command line call to, e.g., {{Code|~/.sugar/debug}} file, to let it run on Sugar Shell startup. It is important to let sugar-client know about environment variables like {{Code|DISPLAY}} and {{Code|DBUS_SESSION_BUS_ADDRESS}}. This command will start, if it was not started before, DBus service on session bus.

Background operations are:

* Process auto-[[#Registration on a school server|registration]]. If {{Code|auto-register}} option is {{Code|1}}, sugar-client will process auto-registration for never registered clients. If {{Code|auto-register}} option is more than {{Code|1}}, sugar-client will check if auto-registration is needed on every start.
* Process regular Journal backup. If {{Code|backup-timeout}} option is more than {{Code|0}}, sugar-client will try to backup the Journal periodically in {{Code|backup-timeout}} seconds.
* Process automatic Journal [[#Auto Journal restore|restore]] if {{Code|auto-restore}} is {{Code|True}}.
* Process regular unattended packages update. If {{Code|update-timeout}} option is more than {{Code|0}}, sugar-client will try to call update process periodically in {{Code|update-timeout}} seconds;
* Process stats [[#Usage statistics|monitoring]]. If {{Code|stats-url}} is set.

In all cases, periodical operations will be triggered only once within the same timeout period, even after Sugar session restart.

Background operations will be processed from DBus service. While working, such DBus service will log into {{Code|~/.sugar/''current-profile''/logs/sugar-client.log}} file.

== Backwards compatibility ==

=== Sugar Shell code ===

The sugar-client initiative is intended to replace several client side tools to collect all server interaction functionality in the same place and provide it via DBus API. To support already existed tools, sugar-client provides the same name programs that forward the processing to {{Code|sugar-client}} utility:

* {{Code|dextrose-updater}} utility from Dextrose-2 to process native packages updates.
* {{Code|journal-backup}} Journal backup from Dextrose-2.
* {{Code|journal-restore}} Journal restore from Dextrose-2.
* {{Code|ds-backup.sh}} and {{Code|ds-backup.py}} Journal backup from OLPC XS distribution.

=== Treating UUIDs ===

While interacting with a [[Sugar_Server_Kit/sugar-server#User_identity_models|sugar-server]], sugar-client is different, in case of treating UUIDs while registration, with Sugar Shell code. The UUID value will be a hash of SSH public key (how it is being used for JIDs in Sugar Shell). After registration, UUID value will be kept in {{Code|~/.sugar/''profile''/sugar-client.conf}} file as a sugar-client's {{Code|uuid}} configuration option.

=== OLPC XS ===

In addition to [[Sugar Server Kit]] based solutions, sugar-client will interoperate with OLPC XS school servers.

''TODO''

== Distribution ==

The sugar-client distribution contains:

* {{Code|sugar-client-service}} utility the main program that implements entirely functionality as DBus services for Client API;
* {{Code|sugar-client}} utility to call DBus API from the console;
* {{Code|.service}} files to run {{Code|sugar-client-service}} for each exported DBus interface;
* backwards compatibility command wrappers.

== Configuration ==

The configuration occurs based on several sources (sorted by applied order):

* {{Code|/etc/sugar-client.conf}} system-wide configuration file,
* {{Code|~/.config/sugar-client/config}} user-wide configuration file,
* {{Code|~/.sugar/''current-profile''/sugar-client.conf}} configuration got after registration on a server,

Configuration files contain option names equal to command-line arguments. To get the current configuration, call:

sugar-client-service config

== Troubleshooting ==

'''Debugging'''

To enable debug logging, add the following lines to [[#Configuration|configuration file]]:

[main]
debug = 3

'''Direct launch'''

In special cases, it is possible to execute sugar-client operations directly, instead of calling DBus service. For that reason, {{Code|-d|--direct}} command-line argument needs to be passed:

sugar-client -d update

== Getting involved ==

* [http://bugs.sugarlabs.org/newticket?component=sugar-server-kit Report] on bugs.
* Read the [http://git.sugarlabs.org/server/client/blobs/master/HACKING HACKING] file to know how to contribute with code.

== Resources ==

* [http://git.sugarlabs.org/desktop/stats/commits/sugar-client-1.2 Sources].
* Current stable binary [http://download.sugarlabs.org/packages/Server:/1/ packages].
* Development binary [http://download.sugarlabs.org/packages/Server:/Factory/ packages].

Platform Team/Server Kit/sugar-client

2013-04-23T18:51:15Z

M anish:

Features/Lease Information Display

2012-08-01T19:19:01Z

M anish: /* Benefit to Sugar */

<noinclude>
[[Category:Feature|Lease Information Display]]
</noinclude>

== Summary ==
Display Lease Expiry information in the "My Settings" -> "About My Computer" view.

Currently, some useful information such as Build number, sugar release version, etc. are displayed in the About My Computer section in the My Settings menu. This menu can be extended to display more relevant information on these lines. Many OLPC deployments use the built in security system which involves leases which expire by certain dates.

Expired leases cause a problem for technical support staff at deployments. They requested that if the security system is used, such information should be made easily accessible. This especially, was an important requirement coming out of the OLPC deployment in Paraguay.

Another use case could be for the kids. During vacations, kids don't go to schools for many days and the leases can expire, resulting in the kids getting 'locked out'. If they can easily access this information, then they can make sure that this doesn't happen.

== Owner ==

* Name: [[User:M_anish| Anish Mangal]]
* Email: anish@activitycentral.com

== Current status ==
* Targeted release: 0.98
* Status of code: The code has been tested to work without problems on sugar-0.94 based dextrose-3 images.

== Benefit to Sugar ==

As noted above, this feature will make the lives of tech. support guys at deployments (and kids in some cases), who use the Lease/Security system easier. This feature was specifically requested by the OLPC deployment in Paraguay and is in use there since the last >1.5 years.

== Scope ==
The current code has to be ported to sugar/mainline. The patch is quite small and should be modifiable very easily.

==UI Design==
See [http://people.sugarlabs.org/~anish/resources.pdf this] pdf document (first part) which contains the mockup.

== How To Test ==
* Check for the existence of the lease.sig file.
* If not present, then goto (A)
* If present, then goto (B)

(A) * Open My Settings -> About My Computer
* There should be no field with the name "Lease"

(B) * Open My Settings -> About My Computer
* There should be a field with the name "Lease"
* It should display "XX day(s) to expiry" where XX is the lease expiry date as contained in the lease.sig file

== User Experience ==
If the lease information file (lease.sig) is present, users will see another entry in the "My Settings" -> "About my computer" section mentioning the number of days left before the lease expires.

Currently, if the file is not present, "Information not available" is displayed in that field. That should and will be changed to making the entire field invisible in that case.

== Dependencies ==
This feature is meant only for XO (Currently XO-1, XO-1.5, XO-1.75) laptops. However, since > 98% of sugar users are also XO users, this feature is generally relevant.

== Contingency Plan ==
Don't implement it. / N.A.

== Documentation ==
http://wiki.laptop.org/go/Firmware_Key_and_Signature_Formats#Antitheft.2FActivation_Lease

== Release Notes ==
N.A.

== Comments and Discussion ==
N.A.

Features/Lease Information Display

2012-08-01T19:18:30Z

M anish: /* Summary */

<noinclude>
[[Category:Feature|Lease Information Display]]
</noinclude>

== Summary ==
Display Lease Expiry information in the "My Settings" -> "About My Computer" view.

Currently, some useful information such as Build number, sugar release version, etc. are displayed in the About My Computer section in the My Settings menu. This menu can be extended to display more relevant information on these lines. Many OLPC deployments use the built in security system which involves leases which expire by certain dates.

Expired leases cause a problem for technical support staff at deployments. They requested that if the security system is used, such information should be made easily accessible. This especially, was an important requirement coming out of the OLPC deployment in Paraguay.

Another use case could be for the kids. During vacations, kids don't go to schools for many days and the leases can expire, resulting in the kids getting 'locked out'. If they can easily access this information, then they can make sure that this doesn't happen.

== Owner ==

* Name: [[User:M_anish| Anish Mangal]]
* Email: anish@activitycentral.com

== Current status ==
* Targeted release: 0.98
* Status of code: The code has been tested to work without problems on sugar-0.94 based dextrose-3 images.

== Benefit to Sugar ==

As noted above, this feature will make the lives of tech. support guys at deployments, who use the Lease/Security system easier. This feature was specifically requested by the OLPC deployment in Paraguay and is in use there since the last >1.5 years.

== Scope ==
The current code has to be ported to sugar/mainline. The patch is quite small and should be modifiable very easily.

==UI Design==
See [http://people.sugarlabs.org/~anish/resources.pdf this] pdf document (first part) which contains the mockup.

== How To Test ==
* Check for the existence of the lease.sig file.
* If not present, then goto (A)
* If present, then goto (B)

(A) * Open My Settings -> About My Computer
* There should be no field with the name "Lease"

(B) * Open My Settings -> About My Computer
* There should be a field with the name "Lease"
* It should display "XX day(s) to expiry" where XX is the lease expiry date as contained in the lease.sig file

== User Experience ==
If the lease information file (lease.sig) is present, users will see another entry in the "My Settings" -> "About my computer" section mentioning the number of days left before the lease expires.

Currently, if the file is not present, "Information not available" is displayed in that field. That should and will be changed to making the entire field invisible in that case.

== Dependencies ==
This feature is meant only for XO (Currently XO-1, XO-1.5, XO-1.75) laptops. However, since > 98% of sugar users are also XO users, this feature is generally relevant.

== Contingency Plan ==
Don't implement it. / N.A.

== Documentation ==
http://wiki.laptop.org/go/Firmware_Key_and_Signature_Formats#Antitheft.2FActivation_Lease

== Release Notes ==
N.A.

== Comments and Discussion ==
N.A.

Features/Lease Information Display

2012-07-18T18:02:29Z

M anish: Created page with "== Summary == Display Lease Expiry information in the "My Settings" -> "About My Computer" view. Currently, some useful information such as Build number, sugar release versi..."

== Summary ==
Display Lease Expiry information in the "My Settings" -> "About My Computer" view.

Currently, some useful information such as Build number, sugar release version, etc. are displayed in the About My Computer section in the My Settings menu. This menu can be extended to display more relevant information on these lines. Many OLPC deployments use the built in security system which involves leases which expire by certain dates.

Expired leases cause a problem for technical support staff at deployments. They requested that if the security system is used, such information should be made easily accessible. This especially, was an important requirement coming out of the OLPC deployment in Paraguay.

== Owner ==

* Name: [[User:M_anish| Anish Mangal]]
* Email: anish@activitycentral.com

== Current status ==
* Targeted release: 0.98
* Status of code: The code has been tested to work without problems on sugar-0.94 based dextrose-3 images.

== Benefit to Sugar ==

As noted above, this feature will make the lives of tech. support guys at deployments, who use the Lease/Security system easier. This feature was specifically requested by the OLPC deployment in Paraguay and is in use there since the last >1.5 years.

== Scope ==
The current code has to be ported to sugar/mainline. The patch is quite small and should be modifiable very easily.

==UI Design==
See [http://people.sugarlabs.org/~anish/resources.pdf this] pdf document (first part) which contains the mockup.

== How To Test ==
* Check for the existence of the lease.sig file.
* If not present, then goto (A)
* If present, then goto (B)

(A) * Open My Settings -> About My Computer
* There should be no field with the name "Lease"

(B) * Open My Settings -> About My Computer
* There should be a field with the name "Lease"
* It should display "XX day(s) to expiry" where XX is the lease expiry date as contained in the lease.sig file

== User Experience ==
If the lease information file (lease.sig) is present, users will see another entry in the "My Settings" -> "About my computer" section mentioning the number of days left before the lease expires.

Currently, if the file is not present, "Information not available" is displayed in that field. That should and will be changed to making the entire field invisible in that case.

== Dependencies ==
This feature is meant only for XO (Currently XO-1, XO-1.5, XO-1.75) laptops. However, since > 98% of sugar users are also XO users, this feature is generally relevant.

== Contingency Plan ==
Don't implement it. / N.A.

== Documentation ==
http://wiki.laptop.org/go/Firmware_Key_and_Signature_Formats#Antitheft.2FActivation_Lease

== Release Notes ==
N.A.

== Comments and Discussion ==
N.A.

Features/Multi selection screenshots

2012-07-18T10:50:24Z

M anish: /* Patches */

<noinclude>
[[Category:Feature|Multi selection screenshots]]
</noinclude>

== Summary ==

Implements the ability to select multiple journal entries in the journal entry view and perform group operations (like copy, delete) on them.

== Owner ==
* Name: [[User:Walter| Walter Bender]], [[User:Gonzalo| Gonzalo Odiard]], [[User:erikos| Simon Schampijer]], [[tch| Martin Abente]], [[User:Ajay| Ajay Garg]]
* Email: walter@sugarlabs.org, gonzalo@laptop.org, erikos@sugarlabs.org, tch@activitycentral.com, ajay@activitycentral.com

== Current status ==
* Targeted release: 0.98
* Development status: This feature is tested to be working quite well in sugar-0.94 based dextrose-3 images. The patchset just needs to be ported over to the latest sugar code.

== Benefit to Sugar ==
This feature allows the users to perform operations on multiple journal entries at once, making it very efficient if the user has to perform repetitive tasks like copying/deleting journal entries for many entries. The users can also filter journal entries by using the already existing search facilities and perform operations on those.

Two ways of selecting multiple journal entries have been provided. The user can either click the checkbox next to individual journal entries or use the select/deselect all buttons provided on the toolbar (which only shows up if the feature is being used). This UI takes some ideas from the standard gmail interface in how it allows users to select multiple entries and perform operations on them.

Another interesting and useful side-effect of this feature is that a user can insert a pen-drive with many activity bundles, select 'all' and copy them to journal. The resulting operation will install all bundles on the XO laptop!

== Scope ==
This feature has already been implemented in sugar-0.94 based dextrose-3 builds. The feature just needs porting to the latest sugar version.
===Patches===
* Patch in sugar-dx3 code repo: [http://git.sugarlabs.org/~m_anish/sugar/sugar-dextrose/commit/1d3574120ac7d7bbc4017aa0d0b2aab19553cd4a 1] [http://git.sugarlabs.org/~m_anish/sugar/sugar-dextrose/commit/dfb8c33f9591f7610e1b780bf7a95412c7cf8382 2]
* Patch in sugar-toolkit-dx3 code repo: [http://git.sugarlabs.org/~m_anish/sugar-toolkit/sugar-toolkit-dextrose/commit/e5c63fd56cf9a3982e9629229870aa4319af3b76 1]
* Patch in sugar-artwork-dx3 code repo: [http://git.sugarlabs.org/~m_anish/sugar-artwork/sugar-artwork-dextrose/commit/348bef5511cc8b6774199a7d46b2740036e26431 1] [http://git.sugarlabs.org/~m_anish/sugar-artwork/sugar-artwork-dextrose/commit/136d7abaf9b451aa18023b5c95bc79f3b622814c 2]

== History ==

The implementation is almost identical to the one done by Martin; details available at :
http://www.sugarlabs.org/~tch/journal2.mpeg

The only differences are ::

* More copy-to options :: Clipboard, Documents (in addition to mounted drives).
* When entries are copied to another location, both - the sources and the destinations - are de-selected automatically, without the user explicitly have to de-select them all manually.
* There has been a progress bar added for batch-operations.

== Basic utility of this feature ==

* This feature, merely does a loop-over for multiple entries. That is, the workflow and the end-result in the following two scenarios should be exactly the same ::
** Entries, E1, E2, E3 .... En, are operated upon one after the another, individually.
** Entries, E1, E2, E3 .... En, are selected together, and operated upon one after the another, as a single macro batch-operaton.

* Some particular use-cases ::
** Batch-operations <del>speeds up</del> makes XO-bundle installations more convenient, when multiple bundles are copied together from a USB drive to the journal. Thanks a ton to Sridhar Dhanapalan for the attention generated towards this (otherwise obscure) use-case.

== UI Design ==

=== Typical copy-to workflow ===

=[Step 01] Initial "Journal" view=
**[[File:b1.png]]

=[Step 02] Initial "Documents" view=
**[[File:b2.png]]

=[Step 03] Select an entry in the journal. The Edit-Toolbar, signifying batch-operations, appears.=
**[[File:b3.png]]

=[Step 04] Select more entries in the Journal.=
**[[File:b4.png]]

=[Step 05] Click "Copy" toolbar button, and select to copy to "Documents" from the pop-up=
**[[File:b5.png]]

=[Step 06] The confirmation alert appears. Click 'OK'=
**[[File:b6.png]]

=[Step 07] If there ia any error for a entry, the message is displayed as an alert. Click 'OK' to continue.=
**[[File:b7.png]]

=[Step 08] Progress status for entry=
**[[File:b8.png]]

=[Step 09] Progress status for next entry. Note that the progress-status changed without any user convention=
**[[File:b9.png]]

=[Step 10] Final "Journal" view. Note that all the "source" entries are de-selected.=
**[[File:b10.png]]

=[Step 11] Final "Documents" view. Note that all "destination" entries are de-selected.=
**[[File:b11.png]]

== Dependencies ==

None

== Contingency Plan ==

Don't use this feature

== Documentation ==

This feature was discussed in EDUJam 2011 and [http://wiki.sugarlabs.org/go/Features/Multi_selection this] feature page was a result of that.

Features/Multi selection screenshots

2012-07-18T10:49:18Z

M anish:

<noinclude>
[[Category:Feature|Multi selection screenshots]]
</noinclude>

== Summary ==

Implements the ability to select multiple journal entries in the journal entry view and perform group operations (like copy, delete) on them.

== Owner ==
* Name: [[User:Walter| Walter Bender]], [[User:Gonzalo| Gonzalo Odiard]], [[User:erikos| Simon Schampijer]], [[tch| Martin Abente]], [[User:Ajay| Ajay Garg]]
* Email: walter@sugarlabs.org, gonzalo@laptop.org, erikos@sugarlabs.org, tch@activitycentral.com, ajay@activitycentral.com

== Current status ==
* Targeted release: 0.98
* Development status: This feature is tested to be working quite well in sugar-0.94 based dextrose-3 images. The patchset just needs to be ported over to the latest sugar code.

== Benefit to Sugar ==
This feature allows the users to perform operations on multiple journal entries at once, making it very efficient if the user has to perform repetitive tasks like copying/deleting journal entries for many entries. The users can also filter journal entries by using the already existing search facilities and perform operations on those.

Two ways of selecting multiple journal entries have been provided. The user can either click the checkbox next to individual journal entries or use the select/deselect all buttons provided on the toolbar (which only shows up if the feature is being used). This UI takes some ideas from the standard gmail interface in how it allows users to select multiple entries and perform operations on them.

Another interesting and useful side-effect of this feature is that a user can insert a pen-drive with many activity bundles, select 'all' and copy them to journal. The resulting operation will install all bundles on the XO laptop!

== Scope ==
This feature has already been implemented in sugar-0.94 based dextrose-3 builds. The feature just needs porting to the latest sugar version.
===Patches===
* Patch in sugar-dx3 code repo: [http://git.sugarlabs.org/~m_anish/sugar/sugar-dextrose/commit/1d3574120ac7d7bbc4017aa0d0b2aab19553cd4a 1] [http://git.sugarlabs.org/~m_anish/sugar/sugar-dextrose/commit/dfb8c33f9591f7610e1b780bf7a95412c7cf8382 2]
* Patch in sugar-toolkit-code repo: [http://git.sugarlabs.org/~m_anish/sugar-toolkit/sugar-toolkit-dextrose/commit/e5c63fd56cf9a3982e9629229870aa4319af3b76 1]
* Patch in sugar-artwork-dx3 code repo: [http://git.sugarlabs.org/~m_anish/sugar-artwork/sugar-artwork-dextrose/commit/348bef5511cc8b6774199a7d46b2740036e26431 1] [http://git.sugarlabs.org/~m_anish/sugar-artwork/sugar-artwork-dextrose/commit/136d7abaf9b451aa18023b5c95bc79f3b622814c 2]

== History ==

The implementation is almost identical to the one done by Martin; details available at :
http://www.sugarlabs.org/~tch/journal2.mpeg

The only differences are ::

* More copy-to options :: Clipboard, Documents (in addition to mounted drives).
* When entries are copied to another location, both - the sources and the destinations - are de-selected automatically, without the user explicitly have to de-select them all manually.
* There has been a progress bar added for batch-operations.

== Basic utility of this feature ==

* This feature, merely does a loop-over for multiple entries. That is, the workflow and the end-result in the following two scenarios should be exactly the same ::
** Entries, E1, E2, E3 .... En, are operated upon one after the another, individually.
** Entries, E1, E2, E3 .... En, are selected together, and operated upon one after the another, as a single macro batch-operaton.

* Some particular use-cases ::
** Batch-operations <del>speeds up</del> makes XO-bundle installations more convenient, when multiple bundles are copied together from a USB drive to the journal. Thanks a ton to Sridhar Dhanapalan for the attention generated towards this (otherwise obscure) use-case.

== UI Design ==

=== Typical copy-to workflow ===

=[Step 01] Initial "Journal" view=
**[[File:b1.png]]

=[Step 02] Initial "Documents" view=
**[[File:b2.png]]

=[Step 03] Select an entry in the journal. The Edit-Toolbar, signifying batch-operations, appears.=
**[[File:b3.png]]

=[Step 04] Select more entries in the Journal.=
**[[File:b4.png]]

=[Step 05] Click "Copy" toolbar button, and select to copy to "Documents" from the pop-up=
**[[File:b5.png]]

=[Step 06] The confirmation alert appears. Click 'OK'=
**[[File:b6.png]]

=[Step 07] If there ia any error for a entry, the message is displayed as an alert. Click 'OK' to continue.=
**[[File:b7.png]]

=[Step 08] Progress status for entry=
**[[File:b8.png]]

=[Step 09] Progress status for next entry. Note that the progress-status changed without any user convention=
**[[File:b9.png]]

=[Step 10] Final "Journal" view. Note that all the "source" entries are de-selected.=
**[[File:b10.png]]

=[Step 11] Final "Documents" view. Note that all "destination" entries are de-selected.=
**[[File:b11.png]]

== Dependencies ==

None

== Contingency Plan ==

Don't use this feature

== Documentation ==

This feature was discussed in EDUJam 2011 and [http://wiki.sugarlabs.org/go/Features/Multi_selection this] feature page was a result of that.

Features/Simple Messages Notification

2012-06-12T15:27:14Z

2012-06-12T14:43:30Z

M anish: /* Scope */

<noinclude>{{TOCright}}
[[Category:Feature|3G database support]]
</noinclude>

== Summary ==
The 3G connectivity availability was only the first step. Next step is to provide a UX for easy configuration of 3G modems. Gnome allows users to enter details such as 'Country', 'Plan' and 'Provider' in a drop-down box fashion. This feature brings that functionality into Sugar.

== Owner ==
* Name: Andrés Ambrois, Anish Mangal
* Email: andresambrois@gmail.com, anish@activitycentral.com

== Current status ==
* Targeted release: (0.98)
* Percentage of completion: 70% (0.94 compatible code is working and included in Dextrose builds. The code needs to be ported to 0.98.)

== Detailed Description ==
Provides and easy to use mechanism of entering the configuration settings for 3G modems. The user can select 'Country', 'Plan' and 'Provider' from drop down boxes, and the required settings for the modem will automatically be configured. For some modems which require specific user names or passwords, the user can still manually input those settings.

Thus this is an add-on to existing functionality, where all settings must be manually typed in into the text-entry fields.

== Benefit to Sugar ==
Ease of use and configurability.

== Scope ==

* extensions/cpsection/modemconfiguration/config.py.in
* extensions/cpsection/modemconfiguration/model.py
* extensions/cpsection/modemconfiguration/view.py
* The XML database for Country, Plan, Provider already included in builds.

==UI Design==
The UI has been kept consistent with what is provided in Gnome. Drop down boxes for Country, Plan and Provider are provided, which when entered, configure settings in the text fields below. Attaching screenshots:

New user interface with database support.
[[File:3g_database_support_ui.png|700px]]

Old user interface without database support.
[[File:3g_configuration_old_ui.png|700px]]

== How To Test ==

* Insert the 3G modem.
* Open "My Settings -> Modem"
* Enter the modem configuration settings manually in the text entry fields
* Click the 'tick' button. It will prompt for a restart. Restart Sugar. The modem will be detected and connected
* Now open "My Settings -> Modem" again
* Clear the text entry fields which have values/text in them
* Select the Country, Plan and Provider from the drop down boxes.
* Verify that some values in the text entry fields were automatically set
* Enter information in missing fields (if any)
* Click the 'tick' button. It will prompt for a restart. Restart Sugar. The modem will be detected and connected
* Open the My Settings -> Modem again
* Check that the selected Country, Plan, and Provider values in the Drop down boxes are correct.

== User Experience ==

1. Plug GSM modem.

2. Open My Settings -> Modem

3. Select Country, Plan and Provider from the provided drop down menus

4. Click the 'tick' button on the top right corner of screen.

5. It will prompt for a sugar restart, Select Restart now.

6. After restart, the modem should automatically get connected

== Dependencies ==
Network Manager 0.8x (Most probably wont work with NM 0.9x. It needs to be ported)

== Contingency Plan ==
The manual text entry fields are provided to configure the modem, if the drop down boxes dont work.

== Documentation ==
Please see the testing section.

== Release Notes ==
N.A.

== Comments and Discussion ==
N.A.

Features/3G Support/Database Support

2012-06-12T14:36:31Z

M anish: /* Scope */

<noinclude>{{TOCright}}
[[Category:Feature|3G database support]]
</noinclude>

== Summary ==
The 3G connectivity availability was only the first step. Next step is to provide a UX for easy configuration of 3G modems. Gnome allows users to enter details such as 'Country', 'Plan' and 'Provider' in a drop-down box fashion. This feature brings that functionality into Sugar.

== Owner ==
* Name: Andrés Ambrois, Anish Mangal
* Email: andresambrois@gmail.com, anish@activitycentral.com

== Current status ==
* Targeted release: (0.98)
* Percentage of completion: 70% (0.94 compatible code is working and included in Dextrose builds. The code needs to be ported to 0.98.)

== Detailed Description ==
Provides and easy to use mechanism of entering the configuration settings for 3G modems. The user can select 'Country', 'Plan' and 'Provider' from drop down boxes, and the required settings for the modem will automatically be configured. For some modems which require specific user names or passwords, the user can still manually input those settings.

Thus this is an add-on to existing functionality, where all settings must be manually typed in into the text-entry fields.

== Benefit to Sugar ==
Ease of use and configurability.

== Scope ==

* extensions/cpsection/modemconfiguration/config.py.in
* extensions/cpsection/modemconfiguration/model.py
* extensions/cpsection/modemconfiguration/view.py

==UI Design==
The UI has been kept consistent with what is provided in Gnome. Drop down boxes for Country, Plan and Provider are provided, which when entered, configure settings in the text fields below. Attaching screenshots:

New user interface with database support.
[[File:3g_database_support_ui.png|700px]]

Old user interface without database support.
[[File:3g_configuration_old_ui.png|700px]]

== How To Test ==

* Insert the 3G modem.
* Open "My Settings -> Modem"
* Enter the modem configuration settings manually in the text entry fields
* Click the 'tick' button. It will prompt for a restart. Restart Sugar. The modem will be detected and connected
* Now open "My Settings -> Modem" again
* Clear the text entry fields which have values/text in them
* Select the Country, Plan and Provider from the drop down boxes.
* Verify that some values in the text entry fields were automatically set
* Enter information in missing fields (if any)
* Click the 'tick' button. It will prompt for a restart. Restart Sugar. The modem will be detected and connected
* Open the My Settings -> Modem again
* Check that the selected Country, Plan, and Provider values in the Drop down boxes are correct.

== User Experience ==

1. Plug GSM modem.

2. Open My Settings -> Modem

3. Select Country, Plan and Provider from the provided drop down menus

4. Click the 'tick' button on the top right corner of screen.

5. It will prompt for a sugar restart, Select Restart now.

6. After restart, the modem should automatically get connected

== Dependencies ==
Network Manager 0.8x (Most probably wont work with NM 0.9x. It needs to be ported)

== Contingency Plan ==
The manual text entry fields are provided to configure the modem, if the drop down boxes dont work.

== Documentation ==
Please see the testing section.

== Release Notes ==
N.A.

== Comments and Discussion ==
N.A.

Features/3G Support/Database Support

2012-06-12T14:34:49Z

M anish: Created page with "<noinclude>{{TOCright}} 3G database support </noinclude> == Summary == The 3G connectivity availability was only the first step. Next step is to provide ..."

<noinclude>{{TOCright}}
[[Category:Feature|3G database support]]
</noinclude>

== Summary ==
The 3G connectivity availability was only the first step. Next step is to provide a UX for easy configuration of 3G modems. Gnome allows users to enter details such as 'Country', 'Plan' and 'Provider' in a drop-down box fashion. This feature brings that functionality into Sugar.

== Owner ==
* Name: Andrés Ambrois, Anish Mangal
* Email: andresambrois@gmail.com, anish@activitycentral.com

== Current status ==
* Targeted release: (0.98)
* Percentage of completion: 70% (0.94 compatible code is working and included in Dextrose builds. The code needs to be ported to 0.98.)

== Detailed Description ==
Provides and easy to use mechanism of entering the configuration settings for 3G modems. The user can select 'Country', 'Plan' and 'Provider' from drop down boxes, and the required settings for the modem will automatically be configured. For some modems which require specific user names or passwords, the user can still manually input those settings.

Thus this is an add-on to existing functionality, where all settings must be manually typed in into the text-entry fields.

== Benefit to Sugar ==
Ease of use and configurability.

== Scope ==

extensions/cpsection/modemconfiguration/config.py.in
extensions/cpsection/modemconfiguration/model.py
extensions/cpsection/modemconfiguration/view.py

==UI Design==
The UI has been kept consistent with what is provided in Gnome. Drop down boxes for Country, Plan and Provider are provided, which when entered, configure settings in the text fields below. Attaching screenshots:

New user interface with database support.
[[File:3g_database_support_ui.png|700px]]

Old user interface without database support.
[[File:3g_configuration_old_ui.png|700px]]

== How To Test ==

* Insert the 3G modem.
* Open "My Settings -> Modem"
* Enter the modem configuration settings manually in the text entry fields
* Click the 'tick' button. It will prompt for a restart. Restart Sugar. The modem will be detected and connected
* Now open "My Settings -> Modem" again
* Clear the text entry fields which have values/text in them
* Select the Country, Plan and Provider from the drop down boxes.
* Verify that some values in the text entry fields were automatically set
* Enter information in missing fields (if any)
* Click the 'tick' button. It will prompt for a restart. Restart Sugar. The modem will be detected and connected
* Open the My Settings -> Modem again
* Check that the selected Country, Plan, and Provider values in the Drop down boxes are correct.

== User Experience ==

1. Plug GSM modem.

2. Open My Settings -> Modem

3. Select Country, Plan and Provider from the provided drop down menus

4. Click the 'tick' button on the top right corner of screen.

5. It will prompt for a sugar restart, Select Restart now.

6. After restart, the modem should automatically get connected

== Dependencies ==
Network Manager 0.8x (Most probably wont work with NM 0.9x. It needs to be ported)

== Contingency Plan ==
The manual text entry fields are provided to configure the modem, if the drop down boxes dont work.

== Documentation ==
Please see the testing section.

== Release Notes ==
N.A.

== Comments and Discussion ==
N.A.

2012-02-24T12:39:38Z

M anish: Adding implementation notes on SSL auth config, and server, client config.

==RRD (Round Robin Database) file data types==

There is a standard set of rrd databases containing stats for journal, system, shell. For each activity there is an independent rrd database which tracks a standard set of parameters, the details for which are listed below.

* database files conform [[Platform_Team/Usage_Statistics#Statistics|Statistics identifiers list]];
* database file name for non-activities is in format {{Code|<TOP-LEVEL-STAT-ID>.rrd}};
* database file name for activities is in format {{Code|activity.<BUNDLE-ID>.rrd}};
* the set of database fields conform second level stat identifiers for particular stat.

==Factors affecting network bandwidth==

The only factor that really affects the network bandwidth usage is the resolution at which the data is being stored. Currently, the default step-size is 60 seconds.

==Factors affecting database size on the client side==

The factor that affects the database size on the client is the RRAs (Round Robin Archives) being cached on the Client XO.

The default RRA configuration on the client side reads something like

RRA:AVERAGE:0.5:1:4320
RRA:AVERAGE:0.5:5:2016

This means that there is one RRA (Round robin archive) within the DB that stores one value every minute for 4320 samples. This makes the total length of this 1 minute resolution RRA to be 4320 minutes = 3 days

The other RRA stores an average of 5 samples, for a total of 2016 samples. Thus its total duration is 5x2016 min= 10080 min= 7 days.

Thus the default duration of high resolution samples is 3 days and lower resolution samples is 7 days. Tweaking these values will affect both the database size on the client size and the network usage.

For locations with very intermittent connectivity, having bigger-duration databases might be advisable. sample RRA's could be

RRA:AVERAGE:0.5:1:43200 (30 days)
RRA:AVERAGE:0.5:5:20160 (70 days)

The above sample values will not be having any impact on network usage, since we're not increasing their resolution, frequency or adding/removing more RRA's

==Notes on reading/interpreting the RRD databases==

===Dumping all information===
* To dump all the information contained in an rrd file, one could use 'rrdtool dump' command.
* To dump the same info in a more pretty print format (tabular), you may use [http://people.sugarlabs.org/anish/dsreport dsreport]. You'll need to install rrdtool-perl to make the script work.

==Notes on usage of the actual server/client system==
Update: The following version numbers have been tested to work. Previous versions were buggy. Subsequent versions may be good. These are the upstream [http://download.sugarlabs.org/packages/Server:/Factory/Fedora-14/ Fedora], [http://download.sugarlabs.org/packages/Server:/Factory/Ubuntu-10.04/ Ubuntu] and [http://download.sugarlabs.org/packages/Server:/Factory/Debian-6.0/ Debian] package repository paths. [http://git.sugarlabs.org/server This] is the upstream git repository. The Dextrose-3 operating system will ship the latest stable sugar-client side packages.

===Server side packages===
* active-document-0.1-3.1
* restful-document-0.1-4.1
* sugar-client-1.2-16.1
* sugar-stats-client-0.1-6.1
* sugar-stats-server-0.1-6.1

===Client side packages===
* sugar-client-1.2-16.1
* sugar-stats-client-0.1-6.1

Note: as you may have noticed, the package sugar-stats-client is needed to be installed on both the Client and the Server. The name is a bit misleading as it is more of a library that provides common functionality. [http://git.sugarlabs.org/server/client/commit/dcaed79104cb0c5f36558a8518ef9e5866d2c2a9 This name has/will be changed in future releases].

===The configuration files===
* There should be configuration files both on the client and the server. Here are the sample configurations:

====Client side config file: /etc/sugar-client.conf====
<pre>
[main]
# url to connect to school server's RESTfull API
api-url = http://schoolserver:8000
# process auto-registeration on a school server on startup; multiple argument,
# if mentioned more than once and previously registered server's IP is different
# from "schoolserver"'s one, process re-registrtion
auto-register = 0
# if, after registration, there are backups to restore on the server, process
# restore automatically
auto-restore = False
# if more than 0, do regular backups with specified delay in seconds
backup-timeout = 0
# rsync url to backup/restore Journal
backup-url =
# debug logging level; multiple argument
debug = 0
# jabber server for Sugar collaboraiton
jabber-url =
# specify machine's serial number instead of detecting it
machine-sn =
# specify machine's UUID instead of detecting it
machine-uuid =
# specify user's nickname instead of detecting it
nickname =
# school server's FQDN, will be auto-set after registration
schoolserver =
# CA certificates file to get access to --stats-url via HTTPS
stats-ca-certs = /home/anish/Documents/openssl/server.crt
# if more than 0 and --stats-url specified, ping stats server with specified
# delay in seconds to coordinate stats gathering work
stats-timeout = 60
# stats server's http(s) url to interact with; if omited, any stats related
# functionality is disabled
stats-url = https://192.168.1.55:8000
# current user's unique identity; needs to be set only from profile
# configuration file; will be auto-created on initial registration
uid =
# optional command-line arguments to pass to a packager while updating the
# system
update-args =
# if more than 0, do regular unattended updates with specified delay in seconds
update-timeout = 0
</pre>

'''Important paramerters to configure are'''
* <code>stats-ca-certs</code>: Path of the SSL certificate in case SSL auth is being used.
* <code>stats-url</code>: The url of the server. This needs to be prefixed with <code>http://</code> or <code>https://</code> to work without/with SSL.
* <code>stats-timeout</code>: The sync frequency of the collected statistics between the client and the server. Note, changing this wouldn't typically affect bandwidth consumption, which is actually determined by the RRAs.
* <code>machine-sn, machine-uuid, nickname</code>: Specify these values explicitly if you want them to be automatically determined. Might be useful in making stats anonymous by setting common machine-sn and/or nickname.

====Server side config file: /etc/sugar-stats.conf====
<pre>
[stats]
# enable stats collecting
stats = True
# path to SSL certificate to serve stats server via HTTPS
stats-certfile = /home/anish/Documents/openssl/server.crt
# space separated list of RRAs for RRD databases on client side
stats-client-rras = RRA:AVERAGE:0.5:1:4320 RRA:AVERAGE:0.5:5:2016
# path to SSL certificate keyfile to serve stats server via HTTPS
stats-keyfile = /home/anish/Documents/openssl/server.key
# path to the root directory to place stats
stats-root = /var/lib/sugar-stats/rrd
# space separated list of RRAs for RRD databases on a server side
stats-server-rras = RRA:AVERAGE:0.5:1:10080 RRA:AVERAGE:0.5:5:8928 RRA:AVERAGE:0.5:15:35040
# step interval in seconds for RRD databases
stats-step = 60

[active-document]
# path to the root directory to place documents' data and indexes
data-root = /var/lib/sugar-stats/users
# limit the resulting list for search requests
find-limit = 32
# flush index every specified changes
index-flush-threshold = 32
# flush index index after specified seconds since the last change
index-flush-timeout = 60
# for concurent access, run index writer in separate thread; this option
# specifies the writer's queue size; 0 means not threading the writer
index-write-queue = 256

[main]
# debug logging level; multiple argument
debug = 0
# hostname to listen incomming connections
host = 192.168.1.55
# path to the directory to place log files
logdir = /var/log/sugar-stats
# port number to listen incomming connections
port = 8000
# path to the directory to place pid files
rundir = /var/run/sugar-stats
# switch off user credentials check; disabling this option will require
# OpenSSH-5.6 or later.
trust-users = True
</pre>

'''Important paramerters to configure are'''
* <code>stats</code>: Must be true for stats collection to be enabled
* <code>stats-certfile</code>: Path of the SSL certificate on the server (if SSL auth is being used)
* <code>stats-keyfile</code>: Path of the SSL private key on the server (if SSL auth is being used)
* <code>stats-client-rras</code>: Configuration of Round Robin Archives on the client. See [[#Factors affecting database size on the client side]]
* <code>stats-server-rras</code>: Configuration of Round Robin Archives on the server. See [[#Factors affecting database size on the client side]]. This will '''NOT''' affect network bandwidth, but merely space consumed on the server.
* <code>stats-step</code>: Step size of '''ALL''' RRAs. This '''WILL''' affect bandwidth consumption. See [[#Factors affecting database size on the client side]]
* <code>trust-users</code>: Set this to True if using openSSH version lower than 5.6

===Notes on using SSL auth===

The steps broadly involved are:
* [http://www.akadia.com/services/ssh_test_certificate.html Generating private key, and self-signed certificates (for test env).] The certificate should be without a passphrase.
* Copying the certificate on the client, and configure <code>sugar-client</code> accordingly.
* Copying the certificate and private key on the server, and configure <code>sugar-stats-server</code> accordingly.

'''Notes on debugging the SSL auth system'''
* Check the <code>stats-url</code> in <code>sugar-client</code> configuration is <code>https://</code> and not <code>http://</code>.
* Check that the certificates are valid or have not expired.
* To check the SSL side of things, following commands maybe run on the client and the server.
** Server: <code>openssl s_server -cert server.crt -key server.key -accept 8000 </code>
** Client: <code>openssl s_client -connect 192.168.1.55:8000 -CAfile server.crt </code> (Replace the ipaddress with the correct server-machine url or IP address.
** If the process runs smoothly, you should see <code>Verify return code: 0 (ok)</code> at the end on the client side terminal. Fails will accompany an error code which maybe looked up [https://www.openssl.org/docs/apps/verify.html here]

Platform Team/Server Kit/Guide/Usage Statistics

2012-02-22T15:46:42Z

M anish:

Platform Team/Server Kit/Guide/Usage Statistics

2012-02-16T17:51:23Z

M anish:

2011-09-01T16:37:46Z

M anish: Sugar version decision and analysis

This discussion is a part and blocker for [[Dextrose/3/Feature Freeze]] discussions. One big question is the readiness of new collaboration in sugar-0.94. This raises two more questions if new collaboration isn't ready to be used in schools within 0.94 time frame.

* Should we revert collab code to 0.88 (which we know works), but it will be additional work, and '''only''' AC will have devs to work on that (i guess).
* Should we stick with sugar-0.88.1 (as with dx2) and bypass working on reverting the code. This has a few disadvantages:
** Obviously, we lose out on the new features between 0.88-0.94
** We lose sync with OLPC

The above have to be put up against 'how much work fixing collab is?'. Can it be fixed in time for 0.94. Fixed means, reliably tested as well. I guess this is a call both for OLPC and Dextrose.

Please use this page as a starting point and post your comments [[Talk:Dextrose/3/Sugar Version | here]] :-)

==Discussions/Analysis==

While dextrose-3 alpha-1 was being developed, it was assumed that we would basing it on sugar0.9x/fedora-14. However, the new 0.9x has quite a few collaboration issues, and without collaboration working stably, the whole point of dextrose-3 w.r.t it being used by deployments would be defeated. This made it a significant decision (one, which I believe caused the one week delay in reaching feature freeze). The choices against us were:

* Sugar 0.94/fedora14
* Sugar 0.88/fedora14
* Sugar 0.88/fedora11 (essentially the platform dextrose-2 is based on)

While coming to this decision, all these three options were seriously considered. 0.88/f11 was the last fallback option we had. We were somewhat certain that 0.88/f14 would have worked, but 0.94/f14 was the most ideal alternative. Staying with 0.94/f14 would have meant that:

* We stay in sync with OLPC 11.x, and upstream sugar 0.9x. This is a major advantage considering maintenance and packaging overheads, including backporting, upstreaming patches in the future.
* Fedora 11 was EOL-ed a while ago, and has numerous inherent problems.
* By the time 0.9x collab is eventually ready, it would be better than 0.88 collab.

Comment: One point that was raised during these discussions was that while developing collab 0.9x code, the procedure followed was not good coding practice. Heavily broken new collab code was pushed to trunk and then its fixing was started. What should perhaps been followed was a separate branch should have been used for new collab and only merged when it was stable enough ([http://meeting.sugarlabs.org/sugar-meeting/2011-08-22#i_2688362 reference] to a very long and fruitful discussion about deciding sugar version ;))

Thus, an analysis was carried out about current readiness (existing issues), rate of bugfixing, and comparison of workability with the 0.88 collaboration. At the end of this, I came to the following conclusions:

* The current 0.9x collab is actually not too bad, but there are still some high priority issues remaining.
* The collaboration in 0.88 was somewhat buggy, and those would likely not be fixed anytime soon.
* Collaboration bugs are being fixed at a good rate as of now.

This led me to believe that if AC were to work together with OLPC on collaboration, there is very little reason it will not be fixed by the time 0.94 is actually released. It is also a high priority for OLPC 11.3.0 as well. The way in which AC could contribute to fixing collab is that it need not be fixing the collab bugs directly (as they are complex and require knowledge of collab code) but help with other sugar related issues.

'''So, with the above in mind, dextrose-3 would be based on sugar 0.94/fedora-14.'''

File:Dx2 ac hor purple.png

2011-08-31T01:02:40Z

M anish:

Dextrose

2011-08-31T00:54:41Z

M anish:

__NOTOC__

[[File:Dextrose-2-intl-logo.png|600px]] [[File:Dextrose-mascotte-120x96.png]]
<noinclude>{{TeamHeader|Dextrose|home=Dextrose|xbgColor=ffe792|join_label=Get Involved}}[[Category:Project]]</noinclude>

[[Image:Dextrose_main.png|640px|frameless|right]]

== The deployments' XO Operating System ==

Dextrose is a Sugar distribution for the XO-1 and XO-1.5 jointly developed by [http://activitycentral.org Activity Central], [http://paraguayeduca.org/ Paraguay Educa], [http://www.ceibal.edu.uy/ Plan Ceibal] and [http://sugarlabs.org Sugar Labs] in collaboration with the OLPC and Sugar community.

Our focus is stability and usability in the classroom, but we've also merged some
new features contributed by deployments and freelance contributors.

== New features in Dextrose2 ==

* Backport of [[0.88/Notes|Sugar 0.88]] ([[User:Bernie|Bernie Innocenti]])
* [[Features/Journal_Sort|Journal sorting options]] ([[User:Aa|Andrés Ambrois]])
* [[:File:Dextrose_resource_monitoring.png|Intuitive resource monitoring]] ([[User:M_anish|Anish Mangal]])
* [[Features/Backup_and_Restore|Journal Backup/restore to removable devices]] ([[User:tch|Martin Abente]], [[User:Earias|Esteban Arias]])
* [[Features/Backup_and_Restore|Journal Backup/restore to schoolserver]] ([[User:tch|Martin Abente]])
* Protected activities support ([[User:tch | Martin Abente]])
* Improved GSM/3G handling ([[User:Dcastelo|Daniel Castelo]], [[User:tch|Martin Abente]])
* [[:File:Dextrose_tabbed_browsing.png|Tabbed browsing]] ([[User:M_anish|Anish Mangal]])
* [[:File:Dextrose_teclado_virtual.png|Virtual keyboard]] ([[User:Earias|Esteban Arias]])
* [[:File:Accessibility_control_panel_2.png|Accessibility features]] ([[User:Earias|Esteban Arias]])
* [[:File:Dextrose_journal_repair.png|Journal repair functionality]] ([[User:Earias|Esteban Arias]])
* [[Features/Touchpad_control_panel_section|Fast switching between touchpad and pen-tablet modes]] ([[User:Walter|Walter Bender]])
* OLPC Microformat support in activity updater (Akash Gangil, [[User:M_anish|Anish Mangal]])
* [[Features/Sugar_Adhoc_Networks|Ad-hoc Networks]] ([[User:Erikos|Simon Schampijer]])
* Ability to reissue registration to schoolserver ([[User:tch|Martin Abente]])
* [http://download.sugarlabs.org/dextrose/testing/dxo2/rpms-freeworld/ freeworld codecs] for most multimedia formats, including MP3 music and H264 videos ([[User:Bernie|Bernie Innocenti]])
* [http://codewiz.org/wiki/pictures/sugar/deployment/paraguay/caacupe/escuela_485_daniel_ortellado/dextrose-testing Extensive field testing] ([[User:Bernie|Bernie Innocenti]])
* Lease information display in Control Panel->About My Computer()
* Automatic crashlog reporting and manual feedback reporting, with server side daemon ([[User:Alsroot|Aleksey Lim]], [[User:tch|Martin Abente]], Mukesh Gupta)
* Notification system ([[User:tch|Martin Abente]])
* Automatic yum based updater ([[User:tch|Martin Abente]], [[User:Alsroot|Aleksey Lim]], [[User:M_anish|Anish Mangal]])
* Nearly complete Spanish Translations ([[User:tch|Martin Abente]], Sebastian Codas:scs, Carlos Garay:car|0s)
* One Click Share 3G ([[User:tch|Martin Abente]])

== Dextrose 2 - World Edition ==

[[File:Download-dextrose-py.png]]

'''This is a development build''' targeted for use by multiple deployments worldwide. We do appreciate feedback and bug reports.

{| class="wikitable"
! Hardware
! OS Images
! Size
! Date
|-
| [[File:Xo-1.png]] XO-1, without GNOME
| [http://download.sugarlabs.org/dextrose/testing/dxo2/xo1/intl/os508dx.img os508dx.img]
[http://download.sugarlabs.org/dextrose/testing/dxo2/xo1/intl/os508dx.crc os508dx.crc]
| 411MB
| Apr 1 2011
|-
| [[File:Xo-1.5.png]] XO-1.5, without GNOME
| [http://download.sugarlabs.org/dextrose/testing/dxo2/xo1.5/intl/os508dx.zd os508dx.zd]
| 339MB
| Apr 1 2011
|}

GNOME builds are currently unsupported. If you require GNOME for evaluation purposes in your deployment, please ask on the Dextrose mailing-list.

For more details on this release, see the [[Dextrose/2|Dextrose 2]] pages ([[Dextrose/2/Changelog|Change Log]], [[Dextrose/2/Todo|Todo List]]).

[[Dextrose/Resources|Older releases]]

== Knowing your way around the new features ==

* [http://people.sugarlabs.org/anish/3g_configuration.pdf 3G Modem configuration]
* [http://people.sugarlabs.org/anish/3g_sharing.pdf 3G Connection sharing]
* [http://people.sugarlabs.org/anish/feedback.pdf Manual feedback submission]
* [http://people.sugarlabs.org/anish/resources.pdf Understanding the resources icon and lease information]

== Installation ==

=== XO-1 ===

[[File:Xo-1.png|right]]
[[File:XO-XP.png|right]]

* First, ensure that your laptop is [http://wiki.laptop.org/go/Activation_and_developer_keys unlocked].
* Download both <tt>'''osXXXXX.img'''</tt> and <tt>'''osXXXXX.crc'''</tt> to the root directory of a USB stick or SD card.
* Drop to the "'''ok'''" prompt by pressing [[File:Esc.svg|24px]] (Esc) repeatedly during boot
* Type the command: {{Code|'''copy-nand u:\osNdx.img'''}} for a USB stick or {{Code|'''copy-nand sd:\osNdx.img'''}} for a SD card followed by [[File:Key_enter.jpg|50px]] (enter)
* Wait for the display to fill in with color and the "'''ok'''" prompt to return
* Type the command {{Code|'''reboot'''}} followed by [[File:Key_enter.jpg|50px]] (enter)
* The XO will reboot, finish writing, reboot itself, and take you to the naming and color choice process
* During the reboots, keep the charger connected to allow OFW to self-update

'''See also''' the [http://wiki.sugarlabs.org/go/Talk:Downloads#Upgrade_an_XO-1_to_Sugar_0.84_with_Fedora_11_and_Gnome detailed instructions].

=== XO-1.5 ===

[[File:Xo-1.5.png|right]]
[[File:XO-HS.png|right]]

* First, ensure that your laptop is [http://wiki.laptop.org/go/Activation_and_developer_keys unlocked].
* Download <tt>'''osXXXXX.zd'''</tt> to the root directory of a USB stick
* Drop to the "'''ok'''" prompt by pressing [[File:Esc.svg|24px]] (Esc) repeatedly during boot
* Type the command: {{Code|'''fs-update u:\osXXXXX.zd'''}} followed by [[File:Key_enter.jpg|50px]] (enter)
* Wait for the display to fill in with color and the "'''ok'''" prompt to return
* Type the command {{Code|'''reboot'''}} followed by [[File:Key_enter.jpg|50px]] (enter)
* The XO will reboot and take you to the naming and color choice process

'''See also''' the [http://wiki.laptop.org/go/F11_for_1.5 detailed instructions].

== Using Dextrose2 in your deployment ==

We're happy to help other deployments produce their
own OS images independently of us, thus exploiting the [http://www.gnu.org/philosophy/free-sw.html Freedom #1]
provided by Free Software.

=== Subpages ===
{{Special:PrefixIndex/{{PAGENAME}}/}}

Dextrose/3/Feature Freeze

2011-08-27T05:37:35Z

M anish: /* Alpha-2 */

'''TODO'''

* Triage [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone&keywords=~dx3 these] and [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~dx2 these]
* There are some unmerged patches on the @dx mailing list that tch sent some time ago. Those will close a few issues from above.
----
'''Blocker decisions needing debate'''

[[Dextrose/3/SugarVersion]]

----

This page is a listing of dextrose-3 related features and bugs identified on a priority basis. This page is '''NOT''' meant for regular tracking of their completion. The [http://dev.laptop.org.au olpc.au] and [http://bugs.sugarlabs.org sl.o] bug-trackers should be used for that.

=Development goals=

==High priority==
* Stability (looking towards current and future releases)
** Yum based updater [http://dev.laptop.org.au/issues/800 1] [http://dev.laptop.org.au/issues/851 2]
** Offline updates method [http://dev.laptop.org.au/issues/873 1]

* No regressions w.r.t earlier dx-2 or olpc.au releases
** '''TODO''' Identify bug-id's here

* '''Solid collaboration experience''' : This seems to be the most high-priority set of tasks, which are blockers in real terms. Need to fix the most critical ones
** Regressions in collaboration [http://dev.laptop.org.au/issues/737 1]
** [http://dev.laptop.org.au/issues/788 Send to not reliable]
** [http://dev.laptop.org.au/issues/729 Data lost if collaboration is terminated and re-established]
** [http://dev.laptop.org.au/issues/636 Aggressive power management hindering XO collaboration]
** OLPC tickets
*** [http://dev.laptop.org/ticket/10674 10674]
*** [http://dev.laptop.org/ticket/10749 10749]
*** [http://dev.laptop.org/ticket/10750 10750]
*** [http://dev.laptop.org/ticket/10676 10676]
*** [http://dev.laptop.org/ticket/10677 10677]
*** [http://dev.laptop.org/ticket/10801 10801]
*** [http://dev.laptop.org/ticket/10821 10821]
*** [http://dev.laptop.org/ticket/11074 11074]
*** [http://dev.laptop.org/ticket/11073 11073]
*** [http://dev.laptop.org/ticket/11075 11075]

* QA, (& maybe validation?)
* Stable and efficient dextrose development environment
** Discussed this with silbe. Maybe have a custom jhbuild env privately, and a public one once 0.94 is released, otw. rebasing might be a problem. Another way out which was suggested was to have multiple branches with rebase of dx patches on top.

==Medium Priority==
* Configure essential network settings completely within sugar
** [http://dev.laptop.org.au/issues/687 Configure network proxies in Sugar]
** [http://dev.laptop.org.au/issues/432 Sugar GUI to configure hidden SSIDs]
** [http://dev.laptop.org.au/issues/704 Set NTP server from Sugar]

* [http://dev.laptop.org.au/issues/789 Share files with a server]

* [http://dev.laptop.org.au/issues/595 Make running Linux apps more seamless in Sugar]

* Share settings between Sugar and GNOME [http://dev.laptop.org.au/issues/705 1]

* Share files between Sugar and GNOME [http://dev.laptop.org.au/issues/709 1]

==Low priority==
* Collection of usage statistics
* VM image [http://dev.laptop.org.au/issues/715 1] [http://dev.laptop.org.au/issues/691 2]

=Milestone blockers=
==Alpha-2==

All items [http://dev.laptop.org.au/issues?set_filter=1&f%5B%5D=status_id&op%5Bstatus_id%5D=o&v%5Bstatus_id%5D%5B%5D=1&f%5B%5D=tracker_id&op%5Btracker_id%5D=%3D&v%5Btracker_id%5D%5B%5D=1&v%5Btracker_id%5D%5B%5D=2&f%5B%5D=priority_id&op%5Bpriority_id%5D=%3D&v%5Bpriority_id%5D%5B%5D=5&v%5Bpriority_id%5D%5B%5D=6&v%5Bpriority_id%5D%5B%5D=7&f%5B%5D=assigned_to_id&op%5Bassigned_to_id%5D=%3D&v%5Bassigned_to_id%5D%5B%5D=me&v%5Bassigned_to_id%5D%5B%5D=97&v%5Bassigned_to_id%5D%5B%5D=95&v%5Bassigned_to_id%5D%5B%5D=43&v%5Bassigned_to_id%5D%5B%5D=7&v%5Bassigned_to_id%5D%5B%5D=91&v%5Bassigned_to_id%5D%5B%5D=3&f%5B%5D=fixed_version_id&op%5Bfixed_version_id%5D=%3D&v%5Bfixed_version_id%5D%5B%5D=23&f%5B%5D=&c%5B%5D=project&c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=priority&c%5B%5D=subject&c%5B%5D=assigned_to&c%5B%5D=updated_on&c%5B%5D=cf_3&c%5B%5D=due_date&group_by= here] which have a due date of 19th September should be closed.

==Alpha-3==

All items listed as Alpha-2 blockers closed.

All items [http://dev.laptop.org.au/issues?set_filter=1&f%5B%5D=status_id&op%5Bstatus_id%5D=o&v%5Bstatus_id%5D%5B%5D=1&f%5B%5D=tracker_id&op%5Btracker_id%5D=%3D&v%5Btracker_id%5D%5B%5D=1&v%5Btracker_id%5D%5B%5D=2&f%5B%5D=priority_id&op%5Bpriority_id%5D=%3D&v%5Bpriority_id%5D%5B%5D=4&f%5B%5D=assigned_to_id&op%5Bassigned_to_id%5D=%3D&v%5Bassigned_to_id%5D%5B%5D=me&v%5Bassigned_to_id%5D%5B%5D=97&v%5Bassigned_to_id%5D%5B%5D=95&v%5Bassigned_to_id%5D%5B%5D=43&v%5Bassigned_to_id%5D%5B%5D=7&v%5Bassigned_to_id%5D%5B%5D=91&v%5Bassigned_to_id%5D%5B%5D=3&f%5B%5D=fixed_version_id&op%5Bfixed_version_id%5D=%3D&v%5Bfixed_version_id%5D%5B%5D=23&f%5B%5D=&c%5B%5D=project&c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=priority&c%5B%5D=subject&c%5B%5D=assigned_to&c%5B%5D=updated_on&c%5B%5D=cf_3&c%5B%5D=due_date&group_by= here] closed

All items [http://dev.laptop.org.au/issues?set_filter=1&f%5B%5D=status_id&op%5Bstatus_id%5D=o&v%5Bstatus_id%5D%5B%5D=1&f%5B%5D=tracker_id&op%5Btracker_id%5D=%3D&v%5Btracker_id%5D%5B%5D=1&v%5Btracker_id%5D%5B%5D=2&f%5B%5D=priority_id&op%5Bpriority_id%5D=%3D&v%5Bpriority_id%5D%5B%5D=3&f%5B%5D=assigned_to_id&op%5Bassigned_to_id%5D=%3D&v%5Bassigned_to_id%5D%5B%5D=me&v%5Bassigned_to_id%5D%5B%5D=97&v%5Bassigned_to_id%5D%5B%5D=95&v%5Bassigned_to_id%5D%5B%5D=43&v%5Bassigned_to_id%5D%5B%5D=91&f%5B%5D=fixed_version_id&op%5Bfixed_version_id%5D=%3D&v%5Bfixed_version_id%5D%5B%5D=23&f%5B%5D=&c%5B%5D=project&c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=priority&c%5B%5D=subject&c%5B%5D=assigned_to&c%5B%5D=updated_on&c%5B%5D=cf_3&group_by= here] be discussed and closed.

==Beta-1==

==Beta-2==

==Release==

Dextrose/3/Feature Freeze

2011-08-27T05:37:07Z

M anish: /* Alpha-3 */

'''TODO'''

* Triage [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=priority&col=status&col=owner&col=type&col=milestone&keywords=~dx3 these] and [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&keywords=~dx2 these]
* There are some unmerged patches on the @dx mailing list that tch sent some time ago. Those will close a few issues from above.
----
'''Blocker decisions needing debate'''

[[Dextrose/3/SugarVersion]]

----

This page is a listing of dextrose-3 related features and bugs identified on a priority basis. This page is '''NOT''' meant for regular tracking of their completion. The [http://dev.laptop.org.au olpc.au] and [http://bugs.sugarlabs.org sl.o] bug-trackers should be used for that.

=Development goals=

==High priority==
* Stability (looking towards current and future releases)
** Yum based updater [http://dev.laptop.org.au/issues/800 1] [http://dev.laptop.org.au/issues/851 2]
** Offline updates method [http://dev.laptop.org.au/issues/873 1]

* No regressions w.r.t earlier dx-2 or olpc.au releases
** '''TODO''' Identify bug-id's here

* '''Solid collaboration experience''' : This seems to be the most high-priority set of tasks, which are blockers in real terms. Need to fix the most critical ones
** Regressions in collaboration [http://dev.laptop.org.au/issues/737 1]
** [http://dev.laptop.org.au/issues/788 Send to not reliable]
** [http://dev.laptop.org.au/issues/729 Data lost if collaboration is terminated and re-established]
** [http://dev.laptop.org.au/issues/636 Aggressive power management hindering XO collaboration]
** OLPC tickets
*** [http://dev.laptop.org/ticket/10674 10674]
*** [http://dev.laptop.org/ticket/10749 10749]
*** [http://dev.laptop.org/ticket/10750 10750]
*** [http://dev.laptop.org/ticket/10676 10676]
*** [http://dev.laptop.org/ticket/10677 10677]
*** [http://dev.laptop.org/ticket/10801 10801]
*** [http://dev.laptop.org/ticket/10821 10821]
*** [http://dev.laptop.org/ticket/11074 11074]
*** [http://dev.laptop.org/ticket/11073 11073]
*** [http://dev.laptop.org/ticket/11075 11075]

* QA, (& maybe validation?)
* Stable and efficient dextrose development environment
** Discussed this with silbe. Maybe have a custom jhbuild env privately, and a public one once 0.94 is released, otw. rebasing might be a problem. Another way out which was suggested was to have multiple branches with rebase of dx patches on top.

==Medium Priority==
* Configure essential network settings completely within sugar
** [http://dev.laptop.org.au/issues/687 Configure network proxies in Sugar]
** [http://dev.laptop.org.au/issues/432 Sugar GUI to configure hidden SSIDs]
** [http://dev.laptop.org.au/issues/704 Set NTP server from Sugar]

* [http://dev.laptop.org.au/issues/789 Share files with a server]

* [http://dev.laptop.org.au/issues/595 Make running Linux apps more seamless in Sugar]

* Share settings between Sugar and GNOME [http://dev.laptop.org.au/issues/705 1]

* Share files between Sugar and GNOME [http://dev.laptop.org.au/issues/709 1]

==Low priority==
* Collection of usage statistics
* VM image [http://dev.laptop.org.au/issues/715 1] [http://dev.laptop.org.au/issues/691 2]

=Milestone blockers=
==Alpha-2==

All items [http://dev.laptop.org.au/issues?set_filter=1&f%5B%5D=status_id&op%5Bstatus_id%5D=o&v%5Bstatus_id%5D%5B%5D=1&f%5B%5D=tracker_id&op%5Btracker_id%5D=%3D&v%5Btracker_id%5D%5B%5D=1&v%5Btracker_id%5D%5B%5D=2&f%5B%5D=priority_id&op%5Bpriority_id%5D=%3D&v%5Bpriority_id%5D%5B%5D=5&v%5Bpriority_id%5D%5B%5D=6&v%5Bpriority_id%5D%5B%5D=7&f%5B%5D=assigned_to_id&op%5Bassigned_to_id%5D=%3D&v%5Bassigned_to_id%5D%5B%5D=me&v%5Bassigned_to_id%5D%5B%5D=97&v%5Bassigned_to_id%5D%5B%5D=95&v%5Bassigned_to_id%5D%5B%5D=43&v%5Bassigned_to_id%5D%5B%5D=7&v%5Bassigned_to_id%5D%5B%5D=91&v%5Bassigned_to_id%5D%5B%5D=3&f%5B%5D=fixed_version_id&op%5Bfixed_version_id%5D=%3D&v%5Bfixed_version_id%5D%5B%5D=23&f%5B%5D=&c%5B%5D=project&c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=priority&c%5B%5D=subject&c%5B%5D=assigned_to&c%5B%5D=updated_on&c%5B%5D=cf_3&c%5B%5D=due_date&group_by= here] should be closed.

==Alpha-3==

All items listed as Alpha-2 blockers closed.

All items [http://dev.laptop.org.au/issues?set_filter=1&f%5B%5D=status_id&op%5Bstatus_id%5D=o&v%5Bstatus_id%5D%5B%5D=1&f%5B%5D=tracker_id&op%5Btracker_id%5D=%3D&v%5Btracker_id%5D%5B%5D=1&v%5Btracker_id%5D%5B%5D=2&f%5B%5D=priority_id&op%5Bpriority_id%5D=%3D&v%5Bpriority_id%5D%5B%5D=4&f%5B%5D=assigned_to_id&op%5Bassigned_to_id%5D=%3D&v%5Bassigned_to_id%5D%5B%5D=me&v%5Bassigned_to_id%5D%5B%5D=97&v%5Bassigned_to_id%5D%5B%5D=95&v%5Bassigned_to_id%5D%5B%5D=43&v%5Bassigned_to_id%5D%5B%5D=7&v%5Bassigned_to_id%5D%5B%5D=91&v%5Bassigned_to_id%5D%5B%5D=3&f%5B%5D=fixed_version_id&op%5Bfixed_version_id%5D=%3D&v%5Bfixed_version_id%5D%5B%5D=23&f%5B%5D=&c%5B%5D=project&c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=priority&c%5B%5D=subject&c%5B%5D=assigned_to&c%5B%5D=updated_on&c%5B%5D=cf_3&c%5B%5D=due_date&group_by= here] closed

All items [http://dev.laptop.org.au/issues?set_filter=1&f%5B%5D=status_id&op%5Bstatus_id%5D=o&v%5Bstatus_id%5D%5B%5D=1&f%5B%5D=tracker_id&op%5Btracker_id%5D=%3D&v%5Btracker_id%5D%5B%5D=1&v%5Btracker_id%5D%5B%5D=2&f%5B%5D=priority_id&op%5Bpriority_id%5D=%3D&v%5Bpriority_id%5D%5B%5D=3&f%5B%5D=assigned_to_id&op%5Bassigned_to_id%5D=%3D&v%5Bassigned_to_id%5D%5B%5D=me&v%5Bassigned_to_id%5D%5B%5D=97&v%5Bassigned_to_id%5D%5B%5D=95&v%5Bassigned_to_id%5D%5B%5D=43&v%5Bassigned_to_id%5D%5B%5D=91&f%5B%5D=fixed_version_id&op%5Bfixed_version_id%5D=%3D&v%5Bfixed_version_id%5D%5B%5D=23&f%5B%5D=&c%5B%5D=project&c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=priority&c%5B%5D=subject&c%5B%5D=assigned_to&c%5B%5D=updated_on&c%5B%5D=cf_3&group_by= here] be discussed and closed.

==Beta-1==

==Beta-2==

==Release==