Alsroot

Hi

My name is Aleksey Lim, I am a volunteer for SugarLabs.

Build 0sugar packages on OBS
Sugarize OO4Kids
Remove login necessity to download experimental activities from ASLO, recheck all ASLO workflows to treat experimental activities as regular ones (update-aslo.php etc)
Renovate Library activity to meet its original purposes e.g. [1] and support peer-to-peer sharing.
Sugarize Aquaria Editor to let people create their own Aquaria games(activities).

Improve Polyol libraries.
Encircle all packaging related stuff around sugar in one well designed packaging system - 0sugar:
- move packaging related code from glucose to 0sugar e.g. if there are two activity installations, one to /usr and one to ~/Activities, sugar decides what version is preferable, or what should happen if user removes activity. This is regular packaging work which should be moved to packaging system.
- extensive usage of centralized (native packaging systems like rpm or deb) and decentralized (0install) models
- patch 0install to support not read only usage of installed packages (some activities could be under development)
Life in sugar! - support full time being online in sugar
- Sugar Daemons, all time beeing online servers that provide useful shared instances for broad collaboration e.g. Chat instances per purposes ("Ask your nub question", "How to hack sugar" etc.)
- Library instance via Sugar Daemon to provide server sharing model
- Сheck notification system in shell if it works well in "all time being in sugar" workflow
- Сreate Collab activity
- Collab instance via Sugar Daemon to have global collaboration portal for all sugar contributors/requesters.

standalone mode for activities thus more close merge sugar with other education software e.g. ASLO could be not just portal of sugar activities but portal of education software(non-sugar users could run particular activity w/o need to install sugar)