[Sugar-devel] New ASLO features to implement

[Aleksey Lim]

Hi all,

Lack of some ASLO features was mentioned several times in this mailing
list. I'm going to start implementing some of them from this week.

Here it is my preliminary TODO (not prioritized list):

* Support(revert) of per architecture uploads, there are bunch of
  activities that are binaries and having requirement to have all
  supported blobs could be overkill for uploaders.

* Support per languages uploads. In some cases (GCompris, OOo4Kids)
  all languages in one bundle weights too much and per locale bundles makes
  sense. While downloading, ASLO will suggest only current locale
  bundle.

* By default, ASLO just an repository of activities (not regarding their
  stability status) and anonymous downloading is required (for now,
  experimental downloads requires be logged in).

* Current QA[1] scheme is too weak for deployment(various) needs and
  having previous option, more reliable scheme is required. Current plan is
  implementing QA profiles. Every activity could be stamped (from -n to
  +n) in several QA profiles. QA stamp is not part of activity itself
  and could be set by QA editors in any time. User can nominate activity
  to be stamped in several QA profiles to notify QA editors about new
  activity. QA editors will be notified about new version of already
  stamped activities via aslo at .

* Support microformat for OLPC updater. Also support collections as
  microformat groups. Take into account QA profiles.

It could be not full list of required features. If you are interested in
some ASLO improvements, post an comment.

[1] http://wiki.sugarlabs.org/go/Activity_Library/Editors/Policy

-- 
Aleksey