Features/Sugar Update Control ASLO: Difference between revisions

Line 2:

== Summary ==

Modify the existing Sugar Update Control to pull from ~~ASLO instead of the wiki~~.~~laptop~~.org

Modify the existing Sugar Update Control to pull from activities.sugarlabs.org

== Owner ==

Line 13:

== Current status ==

* Targeted release: .86

* Last updated: 16 July 2009

* Last updated: 30 July 2009

* Percentage of completion: 50% All basic functionality is present. Needs testing.

* Percentage of completion: 75% All basic functionality is present. Needs testing.

== Source ==

http://git.sugarlabs.org/projects/update

http://git.sugarlabs.org/projects/~~sugar-~~update~~-control/repos/aslo-clone~~

== Detailed Description ==

~~Current, the Sugar~~ Update ~~Control pulls~~ from ~~wiki~~.~~laptop~~.org. ~~Server side, this results in unnecessary work for activities developers as they must update specific wiki pages when releasing new activities~~. ~~The existing system~~ is ~~rather fragile as developers must store~~ the ~~update information by hand in machine-readable micro-format~~. ~~FWIW, this system was pretty good until ASLO came along~~.

Update enables users to update their installed activities from the Activities Library at activities.sugarlabs.org. Activities.sugarlabs.org is base on the well established addons.mozilla.org.

Using ASLO the client can request information about updated by sending a url of the form

Line 57:

Line 56:

== Benefit to Sugar ==

This benefits Sugar by moving the entire activities infrastructure to ~~aslo~~ rather than being spread across a wiki and aslo.

1. This benefits Sugar by moving the entire activities infrastructure to activities.sugarlabs.org rather than being spread across a wiki and aslo.

It reduces activity developer work load.

2. It reduces activity developer work load by using the established activites.sugarlabs.org upload process to update activities.

It reduces and isolates infrastructure load between wiki, ~~aslo~~, and download system. ASLO is backed by memcache, so standard update pings are ~~_very_~~ cheap. ASLO can be configured to store and serve downloads from download-farm to ease scaling issues.

3. It reduces and isolates infrastructure load between wiki, activities.sl.o, and download system.

a. ASLO provides all necessary update information in a single network transaction.

b. ASLO is backed by memcache, so standard update pings are very cheap.

~~Makes activities developers and infrastructure maintainers lives easier~~.

c. ASLO can be configured to store and serve downloads from download-farm to ease scaling issues.

== Scope ==

Technically the scope is ~~pretty~~ limited. Most of the changes are inside sugar-update-control or are in ASLO.

Technically the scope is limited. Most of the changes are inside sugar-update-control or are in ASLO.

There will not be external api changes.

~~Depends on the bitfrost python modules. Until a decision is made concerning where to include those modules in Sugar, actinfo.py, actutils.py and urlrange.py are shipped with sugar-update-control.~~

Over the last several months, ASLO has been improving and proving it's reliability. Many activities are being served via ASLO as their information is marked deprecated on wiki.laptop.org. Shifting update to point to also will require clear communication to end users and developers.

~~Socially, this is _huge_ change.~~ Over the last several months, ASLO has been improving and proving it's reliability. Many activities are being served via ASLO as their information is marked deprecated on wiki.laptop.org. Shifting update to point to also will require clear communication to end users and developers.

=== Implementation ===

@@ Line 2: / Line 2: @@
 == Summary ==
-Modify the existing Sugar Update Control to pull from ASLO instead of the wiki.laptop.org
+Modify the existing Sugar Update Control to pull from activities.sugarlabs.org
 == Owner ==
@@ Line 13: / Line 13: @@
 == Current status ==
 * Targeted release: .86
-* Last updated: 16 July 2009
+* Last updated: 30 July 2009
-* Percentage of completion: 50%  All basic functionality is present.  Needs testing.
+* Percentage of completion: 75%  All basic functionality is present.  Needs testing.
 == Source ==
+http://git.sugarlabs.org/projects/update
-http://git.sugarlabs.org/projects/sugar-update-control/repos/aslo-clone
 == Detailed Description ==
-Current, the Sugar Update Control pulls from wiki.laptop.org.  Server side, this results in unnecessary work for activities developers as they must update specific wiki pages when releasing new activities.  The existing system is rather fragile as developers must store the update information by hand in machine-readable micro-format. FWIW, this system was pretty good until ASLO came along.
+Update enables users to update their installed activities from the Activities Library at activities.sugarlabs.org.  Activities.sugarlabs.org is base on the well established addons.mozilla.org.
 Using ASLO the client can request information about updated by sending a url of the form
@@ Line 57: / Line 56: @@
 == Benefit to Sugar ==
-This benefits Sugar by moving the entire activities infrastructure to aslo rather than being spread across a wiki and aslo.
+. This benefits Sugar by moving the entire activities infrastructure to activities.sugarlabs.org rather than being spread across a wiki and aslo.
-It reduces activity developer work load.
+. It reduces activity developer work load by using the established activites.sugarlabs.org upload process to update activities.
-It reduces and isolates infrastructure load between wiki, aslo, and download system.  ASLO is backed by memcache, so standard update pings are _very_ cheap.  ASLO can be configured to store and serve downloads from download-farm to ease scaling issues.
+. It reduces and isolates infrastructure load between wiki, activities.sl.o, and download system.
+ a. ASLO provides all necessary update information in a single network transaction.
+ b. ASLO is backed by memcache, so standard update pings are very cheap.
-Makes activities developers and infrastructure maintainers lives easier.
+  c. ASLO can be configured to store and serve downloads from download-farm to ease scaling issues.
 == Scope ==
-Technically the scope is pretty limited.  Most of the changes are inside sugar-update-control or are in ASLO.
+Technically the scope is limited.  Most of the changes are inside sugar-update-control or are in ASLO.
 There will not be external api changes.
-Depends on the bitfrost python modules.  Until a decision is made concerning where to include those modules in Sugar, actinfo.py, actutils.py and urlrange.py are shipped with sugar-update-control.
+Over the last several months, ASLO has been improving and proving it's reliability.  Many activities are being served via ASLO as their information is marked deprecated on wiki.laptop.org.  Shifting update to point to also will require clear communication to end users and developers.
-Socially, this is  _huge_ change.  Over the last several months, ASLO has been improving and proving it's reliability.  Many activities are being served via ASLO as their information is marked deprecated on wiki.laptop.org.  Shifting update to point to also will require clear communication to end users and developers.
 === Implementation ===